Creator score

Operation: creator_score
Price: 8 credits / $0.08 display equivalent
Scope: scores:read

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

Supply a GitHub handle or Creator name resolvable by inVerus. Use the result as origin context for an Agent or Skill, while preserving it as a distinct Creator score.

{
  "operation": "creator_score",
  "subject": "@github-handle",
  "channel": "api",
  "idempotency_key": "creator-github-handle-01"
}

When to use it

Use creator_score when the identity behind an Agent or Skill is material to a decision, or when reviewing a Creator independently. It is origin evidence and should be combined with the artifact's own assessment rather than substituted for it.

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": "creator_score",
    "subject": "@github-handle",
    "channel": "api",
    "idempotency_key": "review-194:creator_score:github-handle"
  }'

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: 'creator_score',
    subject: '@github-handle',
    channel: 'api',
    idempotency_key: `review-194:creator_score:github-handle`,
  }),
  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": "creator_score",
        "subject": "@github-handle",
        "channel": "api",
        "idempotency_key": "review-194:creator_score:github-handle",
    },
    timeout=50,
)

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

The operation costs 8 credits after eligible Free calls. Upstream failure reverses usage and returns the failed ledger ID for correlation; retry with the same idempotency key.

Identity checks

Confirm that the resolved Creator is the expected GitHub identity. Public login and display name can change; registered Creator Pages use an immutable GitHub user ID internally. A similar handle on X or Telegram is a different Page type and score.

Relationship use

When displaying Creator evidence beside an Agent, label both pairs and timestamps. If the relationship is unavailable, do not infer it solely from a repository owner string. Use the lineage operation when the relationship itself must be resolved.

Billing and errors

The operation costs 8 credits after eligible Free calls. It requires scores:read. Validation and authorization failures occur before reservation. Upstream failure reverses usage and returns the failed ledger ID for correlation.

Related Page

Registered Creator Pages use /c/{handle}. Console Page refresh and the metered operation should resolve the same underlying Creator subject while retaining their distinct workflow and billing behavior.