# Contract Amendments Source Coverage Map

> Contract Amendments Source Coverage Map is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035021/call, status unknown (last checked 2026-10-15).

Identifies amendment references missing from a supplied source/revision manifest, reporting coverage gaps without proving passage support or exhaustive agreement.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/contract-amendments/source-coverage-map?utm_source=zero.xyz
- Price: $0.035021/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/contract-amendments-source-coverage-map-fe021448
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3npBoWAKSJkOg3C--USdz

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 contract-amendments-source-coverage-map-fe021448 -d '<json body>'
```

Example prompt: Check my contract 'MSA-2024-001' and see which of these 5 amendment references — [Amendment A, Amendment B, Amendment C, Amendment D, Amendment E] — are missing from my source manifest; use public data class and flag metadata as non-personal.

## When to prefer this

Use this endpoint when you need to systematically identify which amendment references are absent from a known source or revision manifest for a specific contract, without needing semantic passage analysis or exhaustive agreement validation. Ideal for compliance audits, due diligence workflows, and document manifest reconciliation tasks where offline typed metadata checking is sufficient and results within 24 hours are acceptable.

## Known failure modes

- Empty amendments array (minimum 1 required) returns validation error
- Exceeding 32 items in sources or amendments arrays causes rejection
- Missing nonpersonalMetadata:true field may block processing
- Invalid dataClass value outside 'public'/'synthetic' enum returns error
- Expired results after 24-hour retention window returns not-found error
- Malformed contractId string may cause lookup failure

## How this service works

Find amendment references absent from the supplied source/revision manifest, preserving declared contract scope. Does not prove passage support or an exhaustive agreement set. Offline typed metadata only. Retained-result recovery: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a structured map identifying which amendment references from the input list are absent from the supplied source/revision manifest, along with coverage gap details. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days. Does not prove passage support or confirm an exhaustive agreement set.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "sources": {
   "type": "array",
   "maxItems": 32,
   "minItems": 0
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "amendments": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "contractId": {
   "type": "string"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/contract-amendments-source-coverage-map-fe021448/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)