# Recovery Manifests — Condition Coverage Map

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

Compares a list of required recovery-check IDs against supplied check states to identify missing, conflicting, or unknown conditions that cannot be satisfied.

## Facts

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

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-condition-coverage-map-a0b02186 -d '<json body>'
```

Example prompt: Can you compare my list of required recovery-check IDs against the states I've supplied and tell me which conditions are missing, conflicting, or unknown? The data is public and nonpersonal — I need to know the coverage gaps in my recovery manifest.

## When to prefer this

Use this endpoint when you need an offline, non-authoritative coverage check of recovery-check IDs — specifically to identify missing, conflicting, or unknown conditions before proceeding with any recovery flow. It is not a recovery authorization or settlement check, so prefer it for pre-flight validation and audit purposes rather than for executing or authorizing recovery actions. Suitable only for public or synthetic, nonpersonal metadata.

## Known failure modes

- Missing required 'requiredChecks' array (must have at least 1 item) returns a validation error
- Providing more than 32 items in 'checks' or 'requiredChecks' exceeds max item limits
- Omitting or setting 'nonpersonalMetadata' to anything other than true causes rejection
- Invalid 'dataClass' value outside of 'public' or 'synthetic' enum returns an error
- Payment failure or insufficient USDC balance prevents execution
- Supplying empty 'checks' array with many required checks results in all required checks reported as missing

## How this service works

Compare required recovery-check IDs with supplied states. Missing, conflicting and unknown states never become satisfied; this is not a recovery authorization or settlement check. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

A coverage map indicating which required check IDs are satisfied, missing, conflicting, or in an unknown state based on the supplied check states — clarifying that missing, conflicting, and unknown states are never treated as satisfied. Results are retained for 24 hours; minimal receipt metadata is kept for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "checks": {
   "type": "array",
   "maxItems": 32,
   "minItems": 0
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "requiredChecks": {
   "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-condition-coverage-map-a0b02186/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)