# Recovery Manifests Provenance Edge Audit

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

Binds supplied result metadata to exact manifests, original payments, chains, and result pins for provenance verification of recovery manifest records.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/recovery-manifests/provenance-edge-audit?utm_source=zero.xyz
- Price: $0.045302/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-provenance-edge-audit-cd93a746
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_R0RJrknOis-59JodafOnB

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-provenance-edge-audit-cd93a746 -d '<json body>'
```

Example prompt: Can you audit the provenance of these recovery manifest results — I have up to 32 result entries and their corresponding manifests, all public data class, assessed as of today, and all nonpersonal metadata — and confirm they're correctly bound to the original payment and chain pins?

## When to prefer this

Use this endpoint when you need to cryptographically or structurally bind recovery manifest result metadata to their originating manifests, payments, and chain pins for audit or compliance purposes. Prefer this over general validation endpoints when the specific domain is recovery manifests with provenance edge tracing requirements, especially when result retention windows (24h) and receipt metadata retention (90 days) are relevant constraints.

## Known failure modes

- Mismatch between result entries and manifest entries (array length or content mismatch)
- assessedAt timestamp outside the open deadline window, making the record ineligible
- nonpersonalMetadata not set to true (required constant), causing validation rejection
- Results or manifests array exceeding 32 items or containing fewer than 1 item
- Data class value not in allowed enum (public/synthetic), causing schema rejection
- Provenance chain or pin not found for supplied manifest references

## How this service works

Bind supplied result metadata to exact manifest, original payment, chain and result pins. An open deadline only establishes window eligibility; no live output availability or delivery is claimed. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

A provenance binding receipt confirming whether the supplied result metadata is correctly linked to the exact manifests, original payment records, chain references, and result pins. Result data is retained for 24 hours; minimal receipt metadata is retained for 90 days.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/recovery-manifests-provenance-edge-audit-cd93a746/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)