Agent or Skill lineage

Operation: agent_skill_lineage
Price: 20 credits / $0.20 display equivalent
Scope: lineage:read

See Lineage result for the associated Creator/T&C shape and REST result fields for ledger, status and balance units.

Lineage uses the same strict score contract as the other operations and adds the associated Creator from Clawdbase's canonical registry records. It is the premium operation because it returns both artifact evidence and verified Creator context.

{
  "operation": "agent_skill_lineage",
  "subject": "owner/repository",
  "channel": "api",
  "idempotency_key": "lineage-owner-repository-01"
}

When to use it

Request lineage when a subject-level score is not enough: forks, generated artifacts, Agent delegation, dynamically loaded Skills, unclear Creator origin or high-impact execution are common triggers.

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": "agent_skill_lineage",
    "subject": "owner/repository",
    "channel": "api",
    "idempotency_key": "review-201:lineage:owner-repository"
  }'

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: 'agent_skill_lineage',
    subject: 'owner/repository',
    channel: 'api',
    idempotency_key: `review-201:lineage:owner-repository`,
  }),
  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": "agent_skill_lineage",
        "subject": "owner/repository",
        "channel": "api",
        "idempotency_key": "review-201:lineage:owner-repository",
    },
    timeout=50,
)

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

Lineage is the only operation that also returns the associated Creator and Creator T&C Score alongside the requested Agent or Skill relationships. A timeout or non-success response from inVerus returns 502 and reverses the 20-credit reservation.

Scope and billing

The key needs lineage:read; scores:read alone is not sufficient. The operation costs 20 credits after free-call accounting because it returns validated artifact evidence plus the canonical Creator relationship and Creator T&C context. channel: "mcp" is rejected with mcp_not_available; MCP is planned and not yet a live channel.

Interpret relationships

Treat returned relationships according to their evidence and freshness. A lineage edge is not automatically a verified endorsement or permission grant. Link canonical nodes when possible and preserve unknown or unresolved relationships explicitly.

Store an auditable decision

Record the subject Page, raw result or supported projection, ledger ID, evidence timestamp and policy version. If your workflow traverses individual related Pages, give each assessment its own request and idempotency key rather than reusing the lineage key.

Failure behavior

A timeout or non-success response from inVerus returns 502 and reverses the 20-credit reservation. Retrying the same logical lineage lookup uses the same idempotency key. Do not fall back to invented relationships or a shallow name match.