# Reading Plans - Record Sequence Diff

> Reading Plans - Record Sequence Diff is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035314/call, status unknown (last checked 2026-10-20).

Separates insertions/deletions from reordering in a before/after reading-plan record list, isolating which surviving records changed position vs. which were added or removed.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/library/reading-plans/record-sequence-diff?utm_source=zero.xyz
- Price: $0.035314/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/reading-plans-record-sequence-diff-e5033ab5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_WEuPxIrwib9KJLclOGpKD

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-record-sequence-diff-e5033ab5 -d '<json body>'
```

Example prompt: Can you compare these two versions of my reading plan record list — before had 12 entries and after has 10 — and tell me which records were actually inserted or deleted versus which surviving records just got reordered? Use public data class.

## When to prefer this

Choose this endpoint when you need to cleanly disentangle record insertions and deletions from positional reordering of survivors in a reading plan list, especially when naive diff tools conflate the two. Best suited for library, publishing, or plan-management workflows where understanding why a record's position changed matters — was it moved, or did surrounding records shift around it?

## Known failure modes

- Array exceeds 32-item limit — request rejected
- Invalid dataClass value (must be 'public' or 'synthetic') — validation error
- nonpersonalMetadata not set to true — request rejected
- Malformed or missing before/after arrays — schema validation failure
- Payment of 0.035314 USDC not supplied — 402 Payment Required

## How this service works

Separate record changes from shared-record reordering; inserting or deleting a record does not itself reorder surviving records for library/plan/work/edition/revision-pinned reading Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured diff identifying which records were inserted, which were deleted, and which surviving records experienced a positional reorder — without conflating the three change types. The analysis is based solely on the supplied before/after arrays and does not constitute 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-record-sequence-diff-e5033ab5/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)