# Catalyst Measurements - Missingness Co-occurrence

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

Counts paired missing owner, revision, and content pins in catalyst measurement records without treating missing values as matches for public material-lot/method-pinned data.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/catalyst-measurements/missingness-cooccurrence?utm_source=zero.xyz
- Price: $0.020318/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/catalyst-measurements-missingness-co-occurrence-a7f5c11c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uxeZ_TzeRhGKP-ElwVuCX

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 catalyst-measurements-missingness-co-occurrence-a7f5c11c -d '<json body>'
```

Example prompt: Check my batch of up to 32 public catalyst measurement records for co-occurring missing pins — I need to know which rows are simultaneously missing owner, revision, or content pin fields without those absences being silently counted as matches.

## When to prefer this

Use this endpoint when you need to explicitly count co-occurring missing pin pairs (owner, revision, content) in catalyst measurement records and require that missing values are never silently treated as matches. Prefer this over generic null-checking tools when your data involves material-lot or method-pinned scientific measurements where provenance integrity matters.

## Known failure modes

- rows array exceeds 32 items — returns validation error
- rows array is empty (minItems:1 violated) — returns schema error
- dataClass not set to 'public' or 'synthetic' — returns enum validation error
- nonpersonalMetadata not set to true (const:true violated) — returns constraint error
- malformed row objects lacking expected pin fields — may return incomplete or zero counts
- network timeout for large row batches — returns HTTP 408 or gateway error

## How this service works

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

## Output

Returns counts of paired missing pin occurrences (owner, revision, content) across the supplied catalyst measurement rows, showing which pin combinations are simultaneously absent and how often, without treating missing values as matching values.

## 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/catalyst-measurements-missingness-co-occurrence-a7f5c11c/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)