Credit Lifecycle

Sleepwalker uses credits for billable actions.

Lifecycle

State	Meaning
estimated	Sleepwalker calculated the expected credit cost.
reserved	Credits were held before queued work started.
settled	Credits were consumed for completed billable work.
released	Reserved credits were returned because work did not run or did not complete billable work.
failed	The billable action failed and no settled charge was recorded for that work.

AI Visibility

AI Visibility is metered per probe.

1 prompt x 1 platform = 1 probe = 1 credit

If a request contains more probes than the account can fund, Sleepwalker can queue the funded probes and mark the rest as skipped.

The completed probes remain available. Skipped probes are reported as not run because of insufficient credits.

Probe credits are settled when Sleepwalker returns a usable response or citations. If a probe fails without a usable result, the reserved credit is released.

Content Intelligence

Content Intelligence runs are metered by analysis depth:

Depth	Credits
score	3
full	6

Single actions have their own fixed credit costs:

Action	Credits
Page serialization	1
Prompt suggestion batch	1
Trend discovery	1
Content score with trends	2
Content score without trends	3

Synchronous single actions reserve credits before work starts. If the action returns a billable result, the reservation is settled in the same request. If the page is blocked, content is empty, or the action cannot complete billable work, the reservation is released.

Failures

Invalid requests that are rejected before work begins do not consume credits.

Actions that cannot start do not consume credits.

When credits are reserved and work cannot be completed, unused credits are released rather than settled.