Pages

The Pages tab lists ownership records joined to canonical Page registrations. Accounts can own multiple legitimate X, Telegram and GitHub-backed Pages; plan tiers do not impose a Page-count limit.

Add another Page

The add area presents X, Telegram and GitHub as provider choices inside the page, not a small generic modal. Selecting a provider starts a fresh authority flow and preserves the active Clawdbase session.

Page card

Each card shows canonical identity, provider verification, two score donuts, last-scored time and direct actions. Use View Page for the public record, Refresh Score for an inVerus refresh, and Share proof for a time-bound share.

GET/api/clawdbase/claimed-pages

POST/api/clawdbase/pages/refresh-score

Score refresh

Refresh targets the card's Page type and canonical registration record. On success, update the Pages card, public Page cache and Console Overview summary from the returned score. Never write a Creator score into an Agent or Skill record.

Data contract

GET /api/clawdbase/claimed-pages returns owned canonical Pages, claimable assets derived from connections and a provider connection summary. Canonical registrations take priority over legacy claims, and the response deduplicates by provider identity before rendering.

The card identity includes a canonical Page ID, Page type, label, public href, verification state, score pair, score status, timestamp and supported actions. Treat claimRecordId as an ownership/registration reference, not as a public provider identifier.

Add another Page

Open the in-page add area

Show X, Telegram and GitHub as full provider choices. Do not open a generic handle dialog.

Start fresh provider authorization

Call the provider's add-page start route and navigate to the returned authorization URL. Keep the active Clawdbase session as the owner context.

Select an authorized GitHub asset

GitHub returns to an asset selector for Creator, Agent or Skill. X and Telegram resolve the authenticated account directly.

Reconcile the receipt

On success, insert or update the Page by canonical ID, invalidate claimed-pages and show whether the Page was created or matched.

Refresh a Page

await fetch('/api/clawdbase/pages/refresh-score', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${session.access_token}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    id: page.id,
    type: page.type,
    claimRecordId: page.claimRecordId,
    handle: page.handle,
  }),
})

Send the Page fields returned by /api/clawdbase/claimed-pages; do not invent a handle target when a canonical registration ID is available. Disable only the affected refresh button, preserve the existing score while pending, and replace it only after the server returns authoritative values.

Duplicate prevention

Two cards with the same provider and immutable provider ID are a data defect, even when their scores differ. Fix canonical matching and ownership deduplication; do not merge cards by current handle in the browser. Reauthorizing the same identity should update verification metadata and return the existing Page.

Card actions

View Page opens the canonical public route.
Refresh Score requests an inVerus refresh for this Page type.
Share proof creates a snapshot/share intent from the same Page record.
Add another Page restarts provider selection and never silently reuses the signed-in provider.

On this page