Agent and Skill lineage

Lineage adds relationship intelligence to a subject-level score. It can return the associated Creator, Creator T&C context and upstream artifact relationships available to inVerus.

The canonical operation is agent_skill_lineage, costs 20 credits and requires the lineage:read operation scope.

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

Lineage is not an endorsement chain. Consumers should still verify each relationship, evidence timestamp and source authority.

What a lineage result can contain

Lineage connects an Agent or Skill to available upstream artifacts, source repositories and Creator context. A relationship can be direct, inferred from source evidence or unavailable. Clients must preserve that distinction instead of flattening every node into a verified ownership statement.

When to request lineage

• A repository is a fork, template or generated derivative.
• The artifact delegates work to another Agent or imports Skills dynamically.
• The Creator relationship is material to approval.
• A high-impact installation needs evidence beyond the subject-level score.
• A prior score changed and the consumer needs to understand upstream context.

Request from a server

const idempotencyKey = `lineage:${pageId}:${evaluationId}`

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: idempotencyKey,
  }),
})

if (response.status === 402) throw new Error('No eligible usage balance')
if (!response.ok) throw new Error(`Lineage request failed: ${response.status}`)
const result = await response.json()

The Access Key needs lineage:read. channel: "mcp" is rejected with mcp_not_available — MCP is planned and not documented as available until a public transport is deployed and verified.

Rendering relationships

Use an ordered or graph representation that names the subject, relationship type, source and freshness. Link nodes to canonical Pages when available. Keep missing Creator context visible as missing; do not infer a Creator from a repository owner string without authoritative resolution.

Billing and retries

Lineage costs 20 credits after free calls. The operation reserves usage before the inVerus request and settles it only on success. An upstream failure reverses the reservation. Reuse the same idempotency key for a retry of the same evaluation so an ambiguous client timeout cannot create another charge.