# API Contracts — Reference Integrity Map

> API Contracts — Reference Integrity Map is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035089/call, status unknown (last checked 2026-10-19).

Inspects HTTP contract inheritance links across a set of declared API contracts to detect missing nodes, cycles, and cross-owner reference issues — offline, without resolving external schemas.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/api-contracts/reference-integrity-map?utm_source=zero.xyz
- Price: $0.035089/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-contracts-reference-integrity-map-e1e880b8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_B9GmDyMq7zrr7mTn1CfeB

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-reference-integrity-map-e1e880b8 -d '<json body>'
```

Example prompt: Can you check these API contracts for reference integrity issues — specifically look for missing nodes, cycles in the inheritance chain, and any cross-owner links? The data is synthetic and non-personal.

## When to prefer this

Choose this endpoint when you need a fast, offline structural check of HTTP contract inheritance links — especially for detecting cycles, missing nodes, or cross-owner references — without triggering full JSON Schema or MCP validation. Ideal for governance pipelines, pre-merge audits, or contract library maintenance where external reference resolution is not needed or desired.

## Known failure modes

- Submitting fewer than 1 or more than 32 contracts returns a validation error
- Missing or incorrect nonpersonal metadata flag (must be true) causes rejection
- Invalid data class value (must be 'public' or 'synthetic') causes schema validation failure
- Contracts with deeply nested or ambiguous inheritance chains may produce incomplete cycle reports
- External references are not resolved, so cross-schema dependencies outside submitted contracts will appear as missing nodes

## How this service works

Inspect declared HTTP contract inheritance links for missing nodes, cycles and cross-owner links. No external references are resolved; this is not complete JSON Schema or MCP validation. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a reference integrity map identifying: missing nodes (referenced contract nodes that are not declared), cycles in the inheritance graph, and cross-owner links between contracts. Results are retained for 24 hours; minimal receipt metadata is kept for 90 days. No external schemas are resolved; validation is offline against the submitted declarations only.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-contracts-reference-integrity-map-e1e880b8/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)