# Recovery Manifests Missingness Co-occurrence Counter

> Recovery Manifests Missingness Co-occurrence Counter is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.020302/call, status unknown (last checked 2026-10-15).

Counts the joint absence (co-occurrence of missingness) of result pins and original payload/receipt deadlines across recovery manifests using only offline, typed non-personal metadata.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/recovery-manifests/missingness-cooccurrence?utm_source=zero.xyz
- Price: $0.020302/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-missingness-co-occurrence-counter-1e518f73
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MRdyJmkrH9rJGeTDk_fYC

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-missingness-co-occurrence-counter-1e518f73 -d '<json body>'
```

Example prompt: Can you count how many of these 20 public recovery manifests have both the result pin and the original payload deadline missing at the same time? Use only non-personal metadata and treat the data class as public.

## When to prefer this

Use this endpoint when you need to quantify how often result pins and payload/receipt deadlines are simultaneously absent in recovery manifests, specifically for offline, typed non-personal metadata only. Prefer this over general missingness tools when working with recovery manifest structures and when you need co-occurrence counts (joint absence) rather than individual field missingness rates. It is appropriate when you explicitly do not require imputation or delivery-outcome inference.

## Known failure modes

- Manifests array exceeds 32 items — request rejected
- nonpersonalMetadata not set to true — validation error
- dataClass not one of 'public' or 'synthetic' — enum validation failure
- Empty manifests array (minItems:1 not met) — request rejected
- Malformed manifest objects — schema validation error
- Service unavailable or payment not processed — HTTP 402 or 5xx error

## How this service works

Count joint absence of result pins and original payload/receipt deadlines. Missing result metadata remains unknown, not proof that delivery failed or succeeded. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns counts representing the joint absence (co-occurrence of missingness) of result pins and original payload/receipt deadline fields across the supplied manifests. The result does not indicate delivery success or failure — only that both metadata fields were absent. Result data is retained for 24 hours; minimal receipt metadata is retained for 90 days.

## 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-missingness-co-occurrence-counter-1e518f73/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)