# Contract Amendments Provenance Edge Audit

> Contract Amendments Provenance Edge Audit is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.045292/call, status unknown (last checked 2026-10-20).

Validates declared amendment-to-source edges against revision pins and tenant/contract boundaries, reporting stale or absent endpoint links in contract amendment provenance graphs.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/contract-amendments/provenance-edge-audit?utm_source=zero.xyz
- Price: $0.045292/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/contract-amendments-provenance-edge-audit-d8e52bbe
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-Z9W1H4Mr06QLHSBq1w-U

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-provenance-edge-audit-d8e52bbe -d '<json body>'
```

Example prompt: Audit the provenance edges for contract C-4892 under tenant T-221 — check whether the declared amendment-to-source links in these 3 amendments match their revision pins and flag any stale or missing endpoints; data class is synthetic.

## When to prefer this

Choose this endpoint when you need to programmatically audit the structural integrity of amendment-to-source provenance edges in contract metadata — specifically to detect stale revision pins or absent source endpoints within strict tenant/contract boundaries. It is purpose-built for offline, typed, nonpersonal metadata validation (public or synthetic data classes only) and is not a substitute for signature verification, legal passage support, or document authenticity checks.

## Known failure modes

- Missing required fields (amendments or edges arrays empty) returns validation error
- tenantId or contractId not supplied causes boundary scoping failure
- dataClass not set to 'public' or 'synthetic' causes enum rejection
- Exceeding 32 items in amendments, edges, or sources arrays returns limit exceeded error
- nonpersonalMetadata not explicitly set to true causes request rejection
- Stale revision pins may produce false positives if caller supplies outdated source lists

## How this service works

Validate declared amendment-to-source edges against supplied revision pins and tenant/contract boundaries. Reports stale or absent endpoints, not passage support, signatures or authenticity. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a structured audit report identifying which declared amendment-to-source provenance edges are stale (revision pin mismatch) or absent (missing endpoints), scoped to the supplied tenant and contract boundaries. Does not validate document content, signatures, or authenticity — metadata linkage only. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "edges": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "sources": {
   "type": "array",
   "maxItems": 32,
   "minItems": 0
  },
  "tenantId": {
   "type": "string"
  },
  "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-provenance-edge-audit-d8e52bbe/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)