# Public Contract Amendment Lineage

> Public Contract Amendment Lineage is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.056001/call, status unknown (last checked 2026-10-20).

Maps nonpersonal public revision IDs, declared field changes, and effective dates across contract amendment history without legal interpretation.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/public-finance/amendment-lineage?utm_source=zero.xyz
- Price: $0.056001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/public-contract-amendment-lineage-4505b14a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vbOMMIBM2iWYtwZNCOGPM

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 public-contract-amendment-lineage-4505b14a -d '<json body>'
```

Example prompt: Can you trace the amendment lineage for public contract ID 'GOV-2024-00312' using public data class and up to 10 revision IDs, and show me all declared field changes and their effective dates?

## When to prefer this

Use this endpoint when you need a structured, non-legal audit trail of public contract amendments, including revision IDs, field-level change declarations, and effective dates. It is best suited for transparency reporting, compliance auditing, and programmatic analysis of public finance contracts where personal data is not involved. Choose it over generic document comparison tools when you need structured lineage output tied to stable revision IDs rather than free-text diff results.

## Known failure modes

- Invalid or unknown contractId returns an error or empty lineage
- Revision array exceeding 32 items is rejected with a validation error
- publicNonpersonalRecords not set to true causes request rejection
- Invalid dataClass enum value (not 'public' or 'synthetic') causes schema validation failure
- Expired results older than 24 hours may not be recoverable
- Network or service unavailability returns a 5xx error

## How this service works

Map nonpersonal public revision IDs, declared field changes and effective dates; no legal effect or contract interpretation. New modular adapter: retained result recovery for 24 hours, minimal receipt metadata for 90 days. Existing live route unchanged.

## Output

Returns a structured mapping of revision IDs to declared field changes and effective dates, covering the full amendment lineage of the specified public contract. Results are retained for 24 hours for recovery; minimal receipt metadata is kept for 90 days. No legal interpretation or contract effect is implied.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "revisions": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "contractId": {
   "type": "string",
   "maxLength": 80
  },
  "publicNonpersonalRecords": {
   "enum": [
    true
   ],
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/public-contract-amendment-lineage-4505b14a/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)