Scopes Reference
Scopes describe what a token or API key can do.
API keys generated in the Sleepwalker app include the action surface by default. Turn off Allow actions when a client should only read reports. MCP bearer token creation defaults to the two read scopes. When MCP write tools are enabled for a deployment, the app exposes an Allow actions option and selects it by default, adding the exact action scopes below. MCP OAuth advertises and requests those action scopes only when MCP write tools are enabled. Older bearer tokens or custom-scoped keys may still carry a narrower set.
Read Scopes
Section titled “Read Scopes”| Scope | Allows |
|---|---|
tests:read |
List and inspect owned tests. |
runs:read |
Read owned run summaries, statuses, and results. |
Write Scopes
Section titled “Write Scopes”| Scope | Allows |
|---|---|
pages:content:serialize |
Serialize page content. |
visibility:prompts:suggest |
Generate visibility prompt ideas. |
visibility:runs:create |
Queue and cancel AI Visibility runs. |
content_intelligence:trends:discover |
Discover content trends. |
content_intelligence:content:score |
Score content. |
content_intelligence:runs:create |
Queue Content Intelligence runs. |
Scope Selection
Section titled “Scope Selection”Use this page to understand authorization errors, audit existing keys, or build custom scoped integrations.
Legacy MCP Alias
Section titled “Legacy MCP Alias”runs:write is an MCP-only compatibility alias retained for older bearer
tokens. It grants the MCP write scopes above. New API keys do not accept it,
and new integrations should request exact action scopes instead.