# Recovery Manifests Export Semantic Parity

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

Compares two sets of parsed recovery export manifests for metadata parity, checking that creation/expiry, payment, chain, and result pins match regardless of order.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/recovery-manifests/export-semantic-parity?utm_source=zero.xyz
- Price: $0.039302/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/recovery-manifests-export-semantic-parity-d4782736
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1kbf25X3MFnRs4AnZ9Dm9

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 recovery-manifests-export-semantic-parity-d4782736 -d '<json body>'
```

Example prompt: Compare these two sets of recovery export manifests — up to 32 entries before and 32 after — and check whether all creation, expiry, payment, chain, and result pins match semantically, treating the data as public synthetic nonpersonal metadata.

## When to prefer this

Choose this endpoint when you need to verify that two snapshots of recovery export manifests preserve the same typed metadata pins (creation, expiry, payment, chain, result) and order does not matter. It is specifically designed for offline, nonpersonal, typed metadata parity — not for restoring outputs, extending deadlines, or comparing arbitrary data structures. Prefer it over general-purpose diff tools when you need structured pin-level semantic equivalence checking on recovery manifests.

## Known failure modes

- Array exceeds 32-item limit returns validation error
- nonpersonalMetadata not set to true causes rejection
- dataClass value outside 'public' or 'synthetic' enum returns schema error
- Malformed manifest entries in before or after arrays cause parsing failure
- Empty or mismatched array lengths may produce inconclusive parity result

## How this service works

Compare parsed recovery exports preserving original creation/expiry, payment, chain and result pins while ignoring order. This is metadata parity, not restored output or deadline extension. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a metadata parity assessment indicating whether the before and after manifest arrays are semantically equivalent with respect to creation/expiry, payment, chain, and result pins; highlights any discrepancies found. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days.

## 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/recovery-manifests-export-semantic-parity-d4782736/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)