# Quantum Calibrations - Missingness Co-occurrence

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

Counts co-occurring missing values across owner, revision, and content pin fields in caller-supplied quantum calibration records without treating absent values as matches

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/quantum-calibrations/missingness-cooccurrence?utm_source=zero.xyz
- Price: $0.020311/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantum-calibrations-missingness-co-occurrence-04d471aa
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_C-HPKmiU1HQf1hydkwuld

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 quantum-calibrations-missingness-co-occurrence-04d471aa -d '<json body>'
```

Example prompt: Check these 10 synthetic quantum calibration rows for co-occurring missing fields — I want to know how many records are simultaneously missing their owner, revision, or content pin values, making sure a missing value isn't counted as a match for another missing value.

## When to prefer this

Use this endpoint when you need to audit bounded sets of caller-supplied quantum calibration records for co-occurring missing fields and require strict null-safety (missing values must not be silently treated as matching each other). Prefer this over generic null-counting tools when the domain is quantum calibration metadata and you need per-field-pair missingness statistics with a clear receipt and retention policy.

## Known failure modes

- Input exceeds 32 KiB limit — request rejected
- Rows array empty or exceeds 32 items — validation error
- dataClass not set to 'public' or 'synthetic' — enum validation failure
- nonpersonalMetadata not set to true — const validation failure
- Malformed JSON payload — parse error
- Service unavailable — transient 5xx error

## How this service works

Count paired missing owner, revision and content pins without silently treating a missing value as a matching value for bounded backend/run/register/measurement-pin records. Caller-supplied public/synthetic nonpersonal calibration declarations only. No hardware measurement, device/API access, recalibration, mitigation, performance guarantee or scientific certification. Input limit: 32 KiB. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns counts of records where specified fields (owner, revision, content pin) are simultaneously missing, disaggregated by co-occurring field pairs, without conflating two missing values as a match. Results are retained for 24 hours; receipt metadata is retained for 90 days.

## 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/quantum-calibrations-missingness-co-occurrence-04d471aa/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)