# Reading Plans - Revision Delta Map

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

Enumerates changes in owner, subject, revision, content, and scope pin fields between two supplied revisions of a reading plan record, identified by stable record ID.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/library/reading-plans/revision-delta-map?utm_source=zero.xyz
- Price: $0.02134/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/reading-plans-revision-delta-map-f81f4c27
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yonAihbkUgmV42ja5_Iz1

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 reading-plans-revision-delta-map-f81f4c27 -d '<json body>'
```

Example prompt: Compare two snapshots of our reading plan records — the before set has up to 32 entries and the after set has up to 32 entries, both from public data — and tell me which owner, subject, revision, content, and scope pin fields changed between them, mapped by stable record ID.

## When to prefer this

Use this endpoint when you need a field-level diff between two specific revision snapshots of reading plan records, identified by stable record IDs, and you already hold both revision sets as caller-supplied data. Prefer this over general-purpose diff tools when you need structured output specifically for library/plan/work/edition/revision-pinned reading plan metadata fields.

## Known failure modes

- Exceeds 32-item array limit for before or after — returns validation error
- Invalid dataClass value (not 'public' or 'synthetic') — returns schema error
- nonpersonalMetadata not set to true — returns constraint violation
- Empty or malformed record arrays — may return empty delta or error
- Records with unstable IDs across revisions — delta mapping may be incomplete or mismatched

## How this service works

Enumerate owner, subject, revision, content and scope pin changes by stable record ID in two supplied revisions for library/plan/work/edition/revision-pinned reading Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

A structured delta map keyed by stable record ID, listing field-level changes (owner, subject, revision, content, scope pin) between the before and after revision arrays supplied by the caller. This is a supplied-record analysis, not independent certification.

## Request schema (JSON Schema)

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

## More

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