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

Overview

See activation state, identity, Page coverage, developer capacity and recent usage at a glance.

Overview is the Console's high-signal landing tab. It orients a new or returning user around one activation lifecycle instead of a generic marketing summary.

Activation lifecycle

  1. 1Connect or recommend GitHub
  2. 2Prepare Creator identity / Page
  3. 3Create an Access Key
  4. 4Run the first operation
  5. 5Core activation complete
  6. 6Optional X or Telegram connection

GitHub is the recommended path because it establishes a Creator identity and authorized repository attribution in one step. It is not mandatory: a user signed in with Google or another method can create an Access Key and run the first operation immediately, then connect GitHub later when Creator or repository authority is needed.

Core data

  • Signed-in identity, connected provider state and whether GitHub is connected or only recommended.
  • Active authenticated Page count and recent score status.
  • Access Key count and current developer allowance.
  • Current plan, included or prepaid credits and recent operations.
  • Beta distribution actions such as sharing and referrals when available.

Empty states

Each section has a focused next action: create the first Access Key and run an operation, connect GitHub to prepare a Creator identity, register the first Page, or connect a provider. Empty states use real account data and never substitute demo totals.

Consistency

Overview Page cards and the Pages tab read the same canonical records. Trust and Confidence donuts must match the public /a, /s, /c, /x or /tg-account Page values.

SectionPopulated stateEmpty state
Developer activationAccess Key count, recent operation and ledger statusCreate the first Access Key and run an operation
IdentityConnected GitHub/X/Telegram and Creator/Page preparation stateRecommend connecting GitHub
PagesActive count, recent Pages and score stateRegister the first Page (optional, not gating)
UsageRemaining free calls or credit balanceExplain the included allowance
BillingCurrent plan and renewal/cancellation stateCompare plans without blocking setup
Distribution (Beta)Recent shares or referralsShare a verified Page

Score health

Overview summaries count actual canonical states: complete, pending, stale, failed and unavailable. They do not average missing scores into zero. Recent Page rows use the same trust, confidence, scoreStatus and scoreUpdatedAt values returned to the Pages tab.

Loading and errors

Overview keeps unaffected sections usable when one source cannot load. Billing never shows an unknown balance as zero, and score failures never replace the last confirmed evidence. Authentication failure returns to the approved sign-in flow rather than showing a false empty account.