# Policy Excerpts — Revision Delta Map

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

Identifies and maps changes between two pinned policy revisions, surfacing differences in clause identifiers, jurisdiction, scope, and effective-time metadata.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/policy-excerpts/revision-delta-map?utm_source=zero.xyz
- Price: $0.021293/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/policy-excerpts-revision-delta-map-f1e15b62
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_x2-zOLpR74V7iUJS3uCTd

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 policy-excerpts-revision-delta-map-f1e15b62 -d '<json body>'
```

Example prompt: Compare these two pinned policy revisions — the 'before' and 'after' snapshots — and tell me exactly which clause identifiers, jurisdictions, scope definitions, or effective dates changed between them. Both datasets are public and non-personal.

## When to prefer this

Choose this endpoint when you need a precise, metadata-level diff between two specific pinned policy revision snapshots — particularly when you care about clause-level identifiers, jurisdiction, scope, and effective-time fields rather than full text analysis. It is purpose-built for offline, non-personal, typed metadata comparison and is not suitable for interpreting legal obligations or processing personal data. Prefer it over general-purpose document diff tools when working with structured policy revision objects in a compliance or governance pipeline.

## Known failure modes

- Missing or malformed 'before' or 'after' revision objects returns a validation error
- Providing personal data when nonpersonalMetadata must be true will be rejected
- Invalid or unsupported dataClass value outside 'public' or 'synthetic' enum causes a 400 error
- Providing non-pinned or unparseable revision objects may result in incomplete delta output
- Results expire after 24 hours and are no longer retrievable

## How this service works

Identify exact source/clause identifiers, jurisdiction, scope and effective-time changes between two pinned policy revisions. A changed revision digest is not interpreted as a changed legal obligation. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

A structured delta map highlighting exact differences between two pinned policy revisions, including changed clause identifiers, jurisdiction modifications, scope alterations, and effective-time changes. Does not interpret legal obligations — strictly metadata-level comparison. Results are retained for 24 hours; minimal receipt metadata is kept 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/policy-excerpts-revision-delta-map-f1e15b62/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)