# Settlement Receipts — Revision Delta Map

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

Compares two pinned settlement receipt revisions to identify changes in transaction, result, amount, and observation-state fields within an exact payment/network frame.

## Facts

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

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 settlement-receipts-revision-delta-map-da23fba5 -d '<json body>'
```

Example prompt: Compare these two pinned settlement receipt revisions — beforeRevision 'rev-2024-04-01-a' and afterRevision 'rev-2024-04-15-b' — using public data class, and show me what changed in transaction outcome, amount, or observation state between them.

## When to prefer this

Choose this endpoint when you need a precise, field-level diff between exactly two pinned settlement receipt revisions within a defined payment/network frame, particularly for audit, compliance, or anomaly-detection workflows where you need to confirm what changed (transaction result, amount, observation state) without triggering any ledger or chain side effects. Prefer it over general-purpose diff tools when working specifically with settlement receipt projections in offline, nonpersonal metadata contexts.

## Known failure modes

- Missing or invalid beforeRevision/afterRevision identifiers — returns validation error
- nonpersonalMetadata not set to true — request rejected as required constant
- dataClass not one of 'public' or 'synthetic' — enum validation failure
- Revision snapshots not found or expired beyond 24-hour retention window — returns not-found error
- Malformed before/after objects — schema validation error

## How this service works

Compare pinned receipt projection revisions for transaction, result, amount and observation-state changes in an exact payment/network frame. No ledger mutation, chain reconciliation or proof of execution. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

A structured delta map highlighting field-level differences between two pinned settlement receipt revisions, covering changes to transaction identifiers, result status, amounts, and observation state within the specified payment/network frame. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days. No ledger mutation or chain reconciliation is performed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "type": "object"
  },
  "before": {
   "type": "object"
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "afterRevision": {
   "type": "string"
  },
  "beforeRevision": {
   "type": "string"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/settlement-receipts-revision-delta-map-da23fba5/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)