# API Contracts Provenance Edge Audit

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

Binds caller-supplied implementation-manifest edges to HTTP contract owners, revisions, input/output pins, and pinned implementation artifacts for offline provenance auditing.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/api-contracts/provenance-edge-audit?utm_source=zero.xyz
- Price: $0.045303/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-contracts-provenance-edge-audit-3b1466f8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_X26ipNvnI7wn55cWSAfGo

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 api-contracts-provenance-edge-audit-3b1466f8 -d '<json body>'
```

Example prompt: Audit the provenance edge between my API contract and its implementation — I have up to 5 edges and 3 contracts to bind, all public data with nonpersonal metadata only, and I need the artifact pins and revision associations confirmed.

## When to prefer this

Choose this endpoint when you need to audit the declared provenance chain between HTTP API contracts and their implementation artifacts — specifically to bind manifest edges to contract owners, revisions, and input/output pins. Use it for offline compliance checks, software supply chain audits, or traceability records where nonpersonal typed metadata is sufficient and deployed runtime conformity verification is not required.

## Known failure modes

- Mismatched edge count or contract count causes validation rejection
- Missing nonpersonal metadata flag (must be explicitly true) causes request rejection
- Exceeding 32 items per array results in schema validation error
- Invalid dataClass value (must be 'public' or 'synthetic') causes rejection
- Edges referencing undeclared contracts or implementations return unbound result entries
- Service returns no guarantee of deployed code conformity even on success

## How this service works

Bind caller-supplied implementation-manifest edges to HTTP contract owner, revision, input/output pins and a pinned implementation artifact. Matching declarations do not prove deployed code conformity. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns bound provenance edge records associating implementation manifest edges with HTTP contract owners, revisions, input/output pins, and pinned implementation artifacts. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days. Does not verify deployed code conformity — only declared manifest associations.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "edges": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "contracts": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "implementations": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-contracts-provenance-edge-audit-3b1466f8/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)