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

Register a Telegram Page

Verify a Telegram account, channel or bot with Telegram-native authority.

Telegram registration starts from an authenticated Clawdbase user and stores a signed add-page intent before opening Telegram authentication.

POST/api/clawdbase/add-page/telegram/start

The start route sends the user through /auth/telegram/start with an add-page return target. On completion, the callback must validate the signed intent, read the canonical Telegram identifier from authenticated data and preserve the existing Clawdbase session.

Authorization errors

If Telegram reports redirect_uri required or incorrect redirect_uri, return to Clawdbase and start the flow again. If the error repeats, contact support with the time of the attempt and the page where registration began. Do not edit or reuse the provider authorization URL.

Channels and bots

Account login alone does not prove control of every channel or bot. Apply the relevant Telegram-native administrator or bot-control proof before creating those Page types.

Start and callback routes

POST/api/clawdbase/add-page/telegram/start
GET/auth/telegram/callback

The add-page start route creates the Clawdbase ownership intent, then sends the browser through /auth/telegram/start. Telegram returns only to the canonical /auth/telegram/callback OpenID callback.

https://clawdbase.ai/auth/telegram/callback

Verification boundary

Clawdbase validates the Telegram authorization response and reads the canonical Telegram subject before creating a Page. A username, URL or typed handle is never accepted as ownership proof.

Preserve the Clawdbase session

Adding a Telegram Page or connection returns to the initiating Clawdbase surface and keeps the current account signed in. It verifies another identity; it does not switch the primary account session.

Verification receipts

The receipt identifies the Telegram Page kind, canonical Page, current username if available, verification time and score status. It never exposes the OpenID token or phone number. If Telegram does not return a public username, use an appropriate display name while retaining the immutable ID internally.

Expected outcomes

Successful authorization either matches the existing canonical Telegram Page or creates one and starts automatic scoring. Cancellation creates nothing. Expired authorization asks you to start again. An account already owned by another Clawdbase user is refused without signing out the current user.