# Recovery Manifests - Revision Delta Map

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

Compares two revision-pinned recovery manifest snapshots and reports changes to payment, network, result, or expiry metadata pins.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/recovery-manifests/revision-delta-map?utm_source=zero.xyz
- Price: $0.021302/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/recovery-manifests-revision-delta-map-93fbc195
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_z7vrLj9_puObn22Ym6j0J

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 recovery-manifests-revision-delta-map-93fbc195 -d '<json body>'
```

Example prompt: Compare these two recovery manifest snapshots — the 'before' and 'after' versions — and tell me what changed in the payment, network, result, or expiry pins; the data is public and non-personal.

## When to prefer this

Choose this endpoint when you need to audit or compare exactly two revision-pinned recovery manifest snapshots for changes in payment, network, result, or expiry metadata pins. It is specifically designed for offline, typed, non-personal metadata diffing (public or synthetic data classes only) and is not suitable for personal data, live authorization checks, or ongoing monitoring streams.

## Known failure modes

- Missing or malformed 'before' or 'after' objects returns a validation error
- Omitting nonpersonalMetadata: true causes rejection
- Supplying a dataClass value other than 'public' or 'synthetic' returns an enum validation error
- Empty objects with no pin fields produce a no-change delta with no useful output
- Network timeout on POST may result in no response; retry is safe given idempotency

## How this service works

Compare revision-pinned recovery metadata and report changes to original payment, network, result or expiry pins. A later expiry is a metadata change, not authorization to renew retention. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

A structured delta report identifying which pins (payment, network, result, expiry) changed between the 'before' and 'after' manifest revisions, along with the nature of each change. Result data is retained for 24 hours; minimal receipt metadata is retained for 90 days.

## 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/recovery-manifests-revision-delta-map-93fbc195/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)