# API Contracts — Revision Delta Map

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

Compares two revisions of HTTP contract metadata to surface deltas in target, input/output pins, and scope labels, without performing full compatibility analysis.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/api-contracts/revision-delta-map?utm_source=zero.xyz
- Price: $0.021303/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-revision-delta-map-9e3fa62f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ijNrCKPToyaAZ3m2joJLZ

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-revision-delta-map-9e3fa62f -d '<json body>'
```

Example prompt: Compare these two API contract revisions and show me what changed in the HTTP target, input/output pins, and scope labels — the data is public and nonpersonal metadata only.

## When to prefer this

Choose this endpoint when you need a focused, fast metadata-level diff between two specific revisions of an HTTP API contract and only care about changes to targets, pins, and scope labels. Prefer it over full compatibility checkers when you do not need causal analysis, breaking-change scores, or runtime validation — just a clean structural delta of typed, nonpersonal contract metadata.

## Known failure modes

- Missing or malformed 'before' or 'after' objects returns a validation error
- nonpersonalMetadata set to false or omitted causes rejection since the const requires true
- dataClass not matching 'public' or 'synthetic' enum values returns an invalid input error
- Supplying personal data in contract objects may be rejected by policy enforcement
- Overly large contract objects may cause timeout or payload-size errors

## How this service works

Compare revision-pinned HTTP contract target, input/output pins and scope labels. These are contract metadata deltas, not full compatibility analysis or a causal explanation. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a structured delta map highlighting differences between two HTTP contract revisions, including changes to route/method targets, input and output pin declarations, and scope labels. Results are retained for 24 hours; minimal receipt metadata is kept for 90 days. No causal explanation or full compatibility analysis is included.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "type": "object"
  },
  "before": {
   "type": "object"
  },
  "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-revision-delta-map-9e3fa62f/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)