# Recovery Manifests Required-Field Coverage Validator

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

Reports missing required-field declarations (payment, input, result, and original expiry) in recovery-manifest metadata without accessing secrets, signatures, or payloads.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/recovery-manifests/required-field-coverage?utm_source=zero.xyz
- Price: $0.010101/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-required-field-coverage-validator-d229f449
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_363UWdGeI4bxrdXsnIhXG

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-required-field-coverage-validator-d229f449 -d '<json body>'
```

Example prompt: Can you check these recovery manifests for missing required fields — specifically any gaps in payment, input, result, or original expiry declarations? The data is synthetic and nonpersonal, and I have about 10 manifests to check.

## When to prefer this

Use this endpoint when you need to audit recovery-manifest metadata for required-field completeness without needing access to secrets, signatures, payloads, or live journal data. Ideal for pre-submission QA, compliance auditing, or batch manifest generation workflows where only offline, nonpersonal metadata is involved. Best suited for public or synthetic data classes with up to 32 manifests per call.

## Known failure modes

- Manifests array empty or exceeds 32-item limit — validation rejected
- nonpersonalMetadata not set to true — request refused
- dataClass not set to 'public' or 'synthetic' — invalid enum error
- Malformed manifest objects — parsing error returned
- Attempting to include personal data — rejected by data-class constraint

## How this service works

Report missing payment, input, result and original expiry declarations in recovery-manifest metadata. No recovery secrets, signatures, payloads, journal access or deadline extension. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

A report identifying which of the submitted recovery manifests are missing required declarations across four categories: payment, input, result, and original expiry fields. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days. No secrets, signatures, payloads, or journal data are returned.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "manifests": {
   "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-required-field-coverage-validator-d229f449/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)