Actions Reference
These are the governed action names recorded in action decisions, usage events, and billing metadata. The same names are used across supported API, MCP, Console, and future CLI paths.
| Action | Purpose | Billable |
|---|---|---|
pages.content.serialize |
Normalize page content into bounded chunks. | Yes |
visibility.prompts.suggest |
Generate AI Visibility prompt ideas. | Yes |
visibility.runs.create |
Queue AI Visibility probes. | Yes |
content_intelligence.trends.discover |
Discover relevant content and market trends. | Yes |
content_intelligence.content.score |
Score page coverage and recommendations. | Yes |
content_intelligence.runs.create |
Queue a persisted Content Intelligence run. | Yes |
Read endpoints are authorized by tests:read or runs:read, but they do not
emit synthetic action names such as tests.list or usage.read and do not
consume credits.
Design Rule
Section titled “Design Rule”The action name describes the work, not the transport.
For example, content_intelligence.runs.create means the same thing whether the caller is MCP, API, Console, or CLI.