# Reading Plans – Export Semantic Parity Check

> Reading Plans – Export Semantic Parity Check is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.03934/call, status unknown (last checked 2026-10-16).

Compares two sets of parsed, typed reading-plan record projections for semantic parity, preserving all pins and scope while ignoring field order.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/library/reading-plans/export-semantic-parity?utm_source=zero.xyz
- Price: $0.03934/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/reading-plans-export-semantic-parity-check-24af0ac8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1A57UnFG52oT4o7nMQLL4

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-export-semantic-parity-check-24af0ac8 -d '<json body>'
```

Example prompt: Compare these two reading plan export snapshots — up to 32 records each, using public data class — and tell me if they're semantically equivalent, preserving all pins and scope even if the field order is different.

## When to prefer this

Choose this endpoint when you need order-insensitive semantic comparison of typed reading-plan record projections — specifically when pins (library, plan, work, edition, revision) and scope must be preserved but field ordering may vary between exports. Prefer this over raw-byte or hash-based equality checks when structural equivalence matters more than byte-level identity. Best suited for post-migration validation, pipeline QA, or pre-publish audits of reading plan datasets rather than cryptographic provenance or ownership certification.

## Known failure modes

- Array exceeds maxItems of 32 — request rejected with validation error
- nonpersonalMetadata not set to true — schema const violation causing rejection
- Invalid dataClass value (not 'public' or 'synthetic') — enum validation failure
- Empty or malformed record objects in before/after arrays — parsing error
- Network timeout if record arrays are large and complex
- Service unavailable returning HTTP 402 or 5xx

## How this service works

Compare parsed typed record projections, preserving all pins and scope while ignoring order; not raw-byte equality or proof of the underlying artifact 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 comparison result indicating whether the before and after record projection arrays are semantically equivalent, including whether all typed pins (library, plan, work, edition, revision) and scope declarations are preserved, and highlighting any meaningful discrepancies — without regard to field ordering or raw byte equality.

## 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-export-semantic-parity-check-24af0ac8/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)