Telegram account score

Operation: telegram_account_score
Price: 5 credits / $0.05 display equivalent
Scope: scores:read

See REST result fields for Trust, Confidence, status, freshness, ledger, charge source and balance units.

Supply a Telegram username or channel name resolvable by inVerus. Confirm that the Page type and provider verification match the intended account, channel or bot.

{
  "operation": "telegram_account_score",
  "subject": "@channel_name",
  "channel": "api",
  "idempotency_key": "telegram-channel-name-01"
}

When to use it

Use telegram_account_score for communication-identity context before trusting an account, channel or bot as the official surface for a Creator or artifact. Confirm the subject kind because account authentication does not imply channel administration or bot control.

Code examples

curl --request POST 'https://www.clawdbase.ai/api/clawdbase/operations/run' \
  --header "Authorization: Bearer $CLAWDBASE_API_KEY" \
  --header 'Content-Type: application/json' \
  --data '{
    "operation": "telegram_account_score",
    "subject": "@channel_name",
    "channel": "api",
    "idempotency_key": "review-242:telegram_account_score:channel-name"
  }'

const response = await fetch('https://www.clawdbase.ai/api/clawdbase/operations/run', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.CLAWDBASE_API_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    operation: 'telegram_account_score',
    subject: '@channel_name',
    channel: 'api',
    idempotency_key: `review-242:telegram_account_score:channel-name`,
  }),
  signal: AbortSignal.timeout(50_000),
})

const body = await response.json()
if (!response.ok) throw new Error(body.error)

import os
import requests

response = requests.post(
    "https://www.clawdbase.ai/api/clawdbase/operations/run",
    headers={
        "Authorization": f"Bearer {os.environ['CLAWDBASE_API_KEY']}",
        "Content-Type": "application/json",
    },
    json={
        "operation": "telegram_account_score",
        "subject": "@channel_name",
        "channel": "api",
        "idempotency_key": "review-242:telegram_account_score:channel-name",
    },
    timeout=50,
)

body = response.json()
if not response.ok:
    raise RuntimeError(body.get("error", "operation failed"))

The key needs scores:read. The operation costs 5 credits after Free calls. A 502 indicates no settled charge; retain any prior authoritative Page values as stale and retry the same evaluation with the same idempotency key.

Subject resolution

The resolver may accept a username or channel name, while registered Page ownership remains anchored by the provider-issued identifier and verification kind. Never treat a typed subject as control proof or create a canonical Page from this developer request.

Presentation

Render Telegram Trust and Confidence on the /tg-account/{handle} Page and clearly label whether the subject is an account, channel or bot. Related Agent, Skill or Creator scores remain separate records.

Scope, price and failure

The key needs scores:read. The operation costs 5 credits after Free calls. A 502 indicates no settled charge; retain any prior authoritative Page values as stale and retry the same evaluation with the same idempotency key.

Registration relationship

Use Telegram OpenID/provider-native control flows for Page ownership. See Telegram registration for redirect, nonce, PKCE and session-preservation requirements.