# Revision Lineage Check

> Revision Lineage Check is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.010003/call, status unknown (last checked 2026-10-15).

Compares a revision transition against its declared predecessor to detect lineage inconsistencies and return an integrity receipt

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/provenance/revision-lineage?utm_source=zero.xyz
- Price: $0.010003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/revision-lineage-check-9946a5a0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_G3WZV9J9OS6JCdIffac3A

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability revision-lineage-check-9946a5a0 -d '<json body>'
```

Example prompt: Before I reuse the evidence from the previous draft, can you check the revision handoff between the old version and the new superseding version — both are public data — and flag any lineage inconsistencies?

## When to prefer this

Use this endpoint when you need to verify that a revision correctly and consistently references its declared predecessor before reusing evidence or inheriting prior review outcomes. It is specifically suited for lineage integrity checks in document versioning, audit pipelines, and compliance workflows where chain-of-custody matters. Do not use it if you need to confirm semantic equivalence between revisions, validate review approval inheritance, or establish full document authenticity.

## Known failure modes

- Missing or malformed 'next' revision object causes validation error
- Null 'previous' object treated as initial revision — may produce false-negative inconsistency reports
- Invalid 'dataClass' enum value (must be 'public' or 'synthetic') causes schema rejection
- Inconsistency detection limited to structural lineage — semantic or content equivalence not assessed
- Results expire after 24 hours; re-call required if receipt retrieval window is missed

## How this service works

Check a revision handoff before reusing evidence. Compare one initial or superseding transition with its declared predecessor; return lineage inconsistencies and an integrity receipt. Does not establish authenticity, semantic equivalence or inherited review approval. New modular adapter: retained result recovery for 24 hours, minimal receipt metadata for 90 days. Existing live route unchanged.

## Output

Returns a list of lineage inconsistencies found between the next and previous revision objects, along with an integrity receipt. Results are retained for 24 hours; minimal receipt metadata is stored for 90 days. Does not confirm authenticity, semantic equivalence, or inherited review approval.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "next": {
   "type": "object"
  },
  "previous": {
   "anyOf": [
    {
     "type": "object"
    },
    {
     "type": "null"
    }
   ]
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/revision-lineage-check-9946a5a0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.mahastrategies.com](https://www.zero.xyz/host/www.mahastrategies.com/llms.txt)