Operation playground
Test the production operation path from Developer Access.
The playground is an authenticated Console client for POST /api/clawdbase/operations/run.
Inputs
- Access Key: an active key owned by the signed-in user.
- Operation: one of the six canonical IDs.
- Subject: the Page name, handle, repository or identifier expected by the operation.
- Channel:
api— the only enabled channel. MCP is shown as planned but is disabled in the playground until a public MCP transport is deployed and verified. - Idempotency key: generated uniquely for the intended operation.
Processing states
The Run action disables while pending and shows a clear processing state. A successful response replaces it with a receipt. Failures remain visible and distinguish invalid input, scope denial, exhausted balance and inVerus failure.
Billing behavior
The UI displays operation credits before execution. Free plan calls consume one Free call per successful operation; paid-credit accounting uses the canonical operation credit amount. A failed inVerus call is settled as failed and consumes no credits.
Run a test
Select an active key
The key must belong to the signed-in user and include the selected operation scope. The playground only offers channel: "api" — MCP is planned and channel: "mcp" is rejected with mcp_not_available before any scope check.
Choose the operation
Review the displayed price, required scope and subject example before selecting one of the six operations.
Enter the subject
Use the exact handle, owner/repository or canonical ID expected by the selected operation. The subject is not ownership proof.
Run and inspect
Submit one request, keep the layout stable during processing, and render status, ledger ID, charge source, balance and raw result in the receipt.
Example request body
{
"api_key_id": "selected-key-uuid",
"operation": "skill_score",
"subject": "owner/repository",
"channel": "api",
"idempotency_key": "playground-skill-owner-repository-01"
}The signed-in Console sends api_key_id for scope and receipt attribution. External Access Key callers normally omit this field because the bearer secret identifies the key.
Receipt behavior
An idempotent replay may return result: null, idempotent: true, the existing ledger ID and current balance. Treat it as a previously settled request, not an empty score. The ledger confirms settlement but cannot recover a lost result; use a new idempotency key only when a fresh, normally charged score is required. For a 502, no credits were charged.
Safe testing
Use development credentials and non-sensitive subjects during setup. Playground calls are real metered operations; changing the channel label does not make them simulations. Do not enable MCP execution until the actual MCP transport is available.