Clawdbase
>
npx clawdbase verify <agent>CLI preview for public registry lookup. REST is the developer contract.
Documentation

Troubleshooting

Diagnose Console, provider, score, API and billing failures without losing account state.

Start with the receipt

Record the page or route, UTC timestamp, provider or operation, HTTP status, safe error code and ledger ID when present. Do not send Access Keys, OAuth codes, provider tokens or payment details to support.

Console returns to the landing page

Return to the sign-in or connection action you started and retry once. If the Console still returns to the landing page, contact support with the provider, time and originating Console tab. Do not include the provider authorization URL.

A provider connection replaced my login

Connection and Add Page authorization should preserve the signed-in Clawdbase account. If the avatar/account changes, sign out intentionally, sign back into the intended Clawdbase account, and contact support before reconnecting providers.

Duplicate Page cards

Reload Pages once. If two cards still represent the same provider asset, do not delete either based only on the visible handle or score. Contact support with both public Page links so the immutable provider records can be reconciled safely.

Score does not update

Use Retry on the affected Page. A prior confirmed score remains visible with its timestamp; a Page without one shows Score unavailable. No confirmed score yet. If that state persists, provide the Page link, time and error code to support.

Access Key gets 403

Check the key is active, unexpired and has the required scope. Score operations need scores:read; lineage needs lineage:read. A revoked or expired bearer key returns 401. An authenticated request with the wrong explicit api_key_id or scope returns 403. channel: "mcp" returns 501 mcp_not_available; use channel: "api".

API gets 402

Open Usage & Billing. Free accounts need a remaining monthly call. Paid accounts need enough gifted, included or purchased credits for the selected operation, or eligible overage. A dash means billing details could not be confirmed; it does not mean zero.

Checkout succeeds but the plan stays old

Stay on Usage & Billing while Clawdbase confirms the purchase. Reload once if the processing notice remains. Do not purchase again. If the plan and balance still disagree, contact support with the Checkout Session ID through the secure support channel.

Billing portal does not open

Retry Manage subscription → Open Stripe billing portal. A failure does not change the subscription. If it persists, contact support from the account email and include the UTC time; do not send card details.

Provider-specific help