# Recovery Manifests — Record Sequence Diff

> Recovery Manifests — Record Sequence Diff is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035086/call, status unknown (last checked 2026-10-15).

Compares two ordered lists of revision-pinned recovery manifest digests to identify reorderings and insertions of shared manifests, without any store mutation.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/recovery-manifests/record-sequence-diff?utm_source=zero.xyz
- Price: $0.035086/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/recovery-manifests-record-sequence-diff-1d4071b9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_n7JSfw_JinfOsVATN78gm

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

Example prompt: Can you diff these two ordered recovery manifest lists — the 'before' array is ['rev-001','rev-003','rev-002'] and the 'after' array is ['rev-001','rev-002','rev-003','rev-004'] — using public data class, and tell me which manifests were reordered versus which were newly inserted?

## When to prefer this

Choose this endpoint when you need to distinguish between manifest reorderings and pure insertions in recovery manifest sequences without any side effects or store mutations. It is purpose-built for revision-pinned recovery manifest comparison, making it more precise than generic diff utilities for this schema. Best suited for audit, CI validation, or incident investigation workflows where offline, nonpersonal metadata comparison of up to 32 manifests is sufficient.

## Known failure modes

- Array exceeds maxItems limit of 32 — returns validation error
- nonpersonalMetadata not set to true — request rejected
- Invalid dataClass value outside enum ['public','synthetic'] — schema validation failure
- Empty or malformed array items — diff may return empty or partial results
- Network timeout for large arrays near the 32-item limit

## How this service works

Compare revision-pinned recovery projections and the relative order of shared manifests. Insertions are separate from reordering; no purchase or store mutation. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a structured diff indicating which manifests appear in both the before and after arrays with changed relative positions (reorderings) versus which appear only in the after array (insertions), without modifying any stored state. Results are retained for 24 hours; minimal receipt metadata is kept 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-record-sequence-diff-1d4071b9/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)