# Edition Records Schema Directionality Check

> Edition Records Schema Directionality Check is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035319/call, status unknown (last checked 2026-10-20).

Compares closed export-field schema directionality between two versions of edition record sets (before/after) for supplied-record analysis.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/library/edition-records/schema-directionality?utm_source=zero.xyz
- Price: $0.035319/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/edition-records-schema-directionality-check-ef64d37e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_M3FlvYujJ91HgUzLWymxA

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 edition-records-schema-directionality-check-ef64d37e -d '<json body>'
```

Example prompt: Compare the schema directionality of my edition records — here's the before snapshot (up to 32 records) and the after snapshot, both classified as public data with nonpersonal metadata only, and tell me which export fields were added, removed, or changed.

## When to prefer this

Use this endpoint when you need to compare schema field directionality between two snapshots of edition records specifically — particularly when working with closed export fields and need a supplied-record (not independently certified) analysis. Prefer this over generic schema diff tools when the context involves edition record structures with data-class classification (public or synthetic) and nonpersonal metadata constraints.

## Known failure modes

- before array is empty or missing (minItems:1 not met)
- after array exceeds 32 items (maxItems exceeded)
- dataClass not one of 'public' or 'synthetic'
- nonpersonalMetadata is not exactly true (const:true violation)
- malformed or non-array input for before/after fields
- payment not attached or insufficient USDC amount

## How this service works

Compare closed export-field Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a comparison of closed export-field schema directionality between the before and after edition record arrays, identifying which fields were added, removed, changed, or reordered, along with a summary of structural differences.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/edition-records-schema-directionality-check-ef64d37e/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)