Developer Access

Developer Access contains scoped Access Keys, the operation playground and channel-specific quickstarts.

Access Keys

Free includes one key, Builder up to three, Pro up to twenty and Enterprise up to one hundred. A new claw_live_... secret is returned once. Only its hash and display prefix remain in storage.

Select one of the six canonical operations, enter a subject, and run it with a unique idempotency key. The channel toggle shows REST API as the only enabled channel; MCP is visible and labeled planned but disabled until a public MCP transport is deployed and verified. The result, charge source and updated balance come from the same backend used by external requests.

10 cr

Agent Trust & Confidence Score

Returns Trust and Confidence outputs for a registered Agent.

agent_score

8 cr

Skill Trust & Confidence Score

Returns Trust and Confidence outputs for a registered Skill.

skill_score

20 cr

Agent or Skill Lineage

Returns lineage, associated creator identity and Creator T&C Score.

agent_skill_lineage

8 cr

Creator Trust & Confidence Score

Returns Trust and Confidence outputs for a creator identity.

creator_score

5 cr

X Account Trust & Confidence Score

Returns Trust and Confidence outputs for an X account.

x_account_score

5 cr

Telegram Account Trust & Confidence Score

Returns Trust and Confidence outputs for a Telegram account, channel or bot.

telegram_account_score

See REST API, MCP status and idempotency.

Create an Access Key

Name the workload

Use a name that identifies the service and environment, such as trust-gate-production.

Choose scopes

Select scores:read for score operations and lineage:read for lineage. mcp:invoke is a reserved legacy scope — new Access Keys never receive it, since MCP is planned and channel: "mcp" is rejected before any scope check. Grant the least privilege needed.

Store the secret

The claw_live_... value is shown once. Put it in a server-side deployment secret immediately; Clawdbase stores only its hash.

Test and rotate

Run a low-impact operation, then verify the ledger entry. Create a replacement before revoking a key used by production.

GET/api/clawdbase/api-keys

POST/api/clawdbase/api-keys

PATCH/api/clawdbase/api-keys

DELETE/api/clawdbase/api-keys

Playground request

The playground sends the same fields as the REST route: operation, subject, channel, optional api_key_id and required idempotency_key. When authenticating with an Access Key, an explicit api_key_id must either be omitted or match the bearer key.

{
  "operation": "agent_score",
  "subject": "owner/repository",
  "channel": "api",
  "idempotency_key": "playground-agent-owner-repository-01"
}

Result panel

Show HTTP state, operation, ledger ID, charge source, updated balance and the inVerus payload without inventing normalized fields that the backend does not return. On idempotent replay, the current implementation can return result: null with idempotent: true; explain that the original charge was not repeated and that a lost result requires a new, normally charged request if a fresh score is needed.

MCP status

The operation runner rejects channel: "mcp" before reservation or scoring with a stable mcp_not_available response and creates no ledger entry. Clawdbase does not yet provide a public MCP discovery or transport endpoint, so MCP controls remain disabled and marked Planned.