# Reaction Records - Missingness Co-occurrence

> Reaction Records - Missingness Co-occurrence is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.020316/call, status unknown (last checked 2026-10-20).

Counts paired missing values across owner, revision, and content pins in reaction records without treating missing as matching, for dataset/reaction/method/revision combinations.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/reaction-records/missingness-cooccurrence?utm_source=zero.xyz
- Price: $0.020316/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/reaction-records-missingness-co-occurrence-6f4d90f2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FDwF3msSTc-A-QU7zQucB

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 reaction-records-missingness-co-occurrence-6f4d90f2 -d '<json body>'
```

Example prompt: Check my batch of up to 32 public reaction records for co-occurring missing pins — I want to know how often owner, revision, and content pins are simultaneously absent without treating a missing value as a match.

## When to prefer this

Use this endpoint when you need to count simultaneous (paired) absences of multiple pin fields in reaction records without the risk of a missing value being silently treated as a match. Prefer it over general-purpose data validation tools when working specifically with reaction record schemas involving dataset, method, revision, and owner pins, and when you need missingness co-occurrence counts rather than simple field presence checks.

## Known failure modes

- Rows array exceeds maxItems of 32 — request rejected
- Rows array is empty (minItems 1 violated) — validation error
- nonpersonalMetadata not set to true — required const field missing
- dataClass not one of 'public' or 'synthetic' — enum validation failure
- Malformed row structure — missing required pin fields cause processing errors
- Payment not fulfilled via x402 protocol — 402 response returned

## How this service works

Count paired missing owner, revision and content pins without silently treating a missing value as a matching value for dataset/reaction/method/revision Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns counts of paired missingness co-occurrences across owner, revision, and content pins in the supplied reaction records, without treating a missing value as equivalent to a matching value. Results are specific to the supplied rows and do not constitute independent certification.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/reaction-records-missingness-co-occurrence-6f4d90f2/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)