Skip to content

MCP billing

Sleepwalker uses the same credit system for MCP, API, and Console actions.

Read tools do not consume credits. Billable action tools return billing metadata.

MCP actionCredits
serialize_sleepwalker_page_content1
suggest_sleepwalker_visibility_prompts1
discover_sleepwalker_content_trends1
score_sleepwalker_content with supplied trends2
score_sleepwalker_content without supplied trends3
create_sleepwalker_visibility_run1 per queued probe
create_sleepwalker_content_run with analysis_depth: score3
create_sleepwalker_content_run with analysis_depth: full6

Public pricing:

1 credit = €0.02
minimum top-up = €5.00

Billable tools include a billing block or equivalent credit fields.

Example:

{
"billing": {
"billable": true,
"credit_action": "pages.content.serialize",
"estimated_credits": "1.00",
"credits_enforced": true,
"status": "settled",
"reserved_credits": "1.00",
"settled_credits": "1.00",
"released_credits": "0.00"
}
}
StateMeaning
estimatedSleepwalker reports expected credit usage.
reservedCredits were held before work started.
settledCredits were charged after successful work.
releasedReserved credits were returned because work did not complete as billable.

See Credit Lifecycle for the shared lifecycle.

Credits are not settled for work that is rejected before execution.

For AI Visibility, probes settle only when Sleepwalker returns a usable response or citations. Probes that fail without a usable result release their reserved credits.

If work starts and then cannot complete, the response and Activity entry indicate whether credits were settled or released.

If a visibility run asks for more probes than the account can fund, Sleepwalker can queue the funded probes and mark the rest as skipped.

The funded probes remain accessible. Skipped probes are visible as not run because of insufficient credits.

Use Add Credits in the Sleepwalker app to top up the account balance.