# Recovery Manifests Source Coverage Map

> Recovery Manifests Source Coverage Map is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035081/call, status unknown (last checked 2026-10-15).

Binds recovery declarations to caller-supplied original purchase pins, validating chain and payload/receipt deadline linkages using offline, nonpersonal metadata only.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/recovery-manifests/source-coverage-map?utm_source=zero.xyz
- Price: $0.035081/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-source-coverage-map-83cbc4f9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tVocZ5b1EAcFa6Qyscebv

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-source-coverage-map-83cbc4f9 -d '<json body>'
```

Example prompt: Can you check whether these recovery manifests are properly bound to their original purchase pins? I have up to 10 manifests and matching purchases, all synthetic data, and I need to confirm the chain and deadline linkages are valid.

## When to prefer this

Use this endpoint when you need to verify that recovery declarations are correctly bound to their originating purchase pins in an offline, privacy-preserving manner — no secrets or payment verification is performed. Prefer this over full settlement or payment-verification endpoints when you only need metadata-level coverage mapping and deadline consistency checks without retaining sensitive output.

## Known failure modes

- Invalid or mismatched manifest-to-purchase count (arrays must have 1–32 items each)
- dataClass not set to 'public' or 'synthetic' causes rejection
- nonpersonalMetadata not set to true causes request rejection
- Malformed manifest or purchase pin structures result in validation errors
- Exceeding 32 items in either array returns a schema violation error

## How this service works

Bind recovery declarations to caller-supplied original purchase pins, including chain and original payload/receipt deadlines. No signatures, secrets, payment verification or retained output is loaded. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a binding/coverage map indicating which recovery manifests are successfully linked to their caller-supplied purchase pins, including chain alignment and payload/receipt deadline consistency checks. Results are retained for 24 hours; minimal receipt metadata is kept for 90 days. No signatures, secrets, or payment data are loaded or returned.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/recovery-manifests-source-coverage-map-83cbc4f9/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)