# Quantum Calibrations - Required Field Coverage Check

> Quantum Calibrations - Required Field Coverage Check is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.010119/call, status unknown (last checked 2026-10-20).

Checks that required backend, run, register, and measurement pin fields are present (not null) in caller-supplied public or synthetic quantum calibration records.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/quantum-calibrations/required-field-coverage?utm_source=zero.xyz
- Price: $0.010119/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-required-field-coverage-check-92cfd4a4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lsZiXvW77ipI1jsWHoYR6

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-required-field-coverage-check-92cfd4a4 -d '<json body>'
```

Example prompt: Check these 10 quantum calibration rows (public, nonpersonal) to confirm the required backend, run, register, and measurement-pin fields are all present — flag any that are null.

## When to prefer this

Choose this endpoint when you need a lightweight, deterministic check of required field presence (null vs. non-null) across quantum calibration records that are public or synthetic and nonpersonal. It is purpose-built for pin-field completeness auditing on calibration data, not for hardware access, recalibration, or scientific certification. Prefer it over general-purpose data validators when working specifically with quantum backend/run/register/measurement pin schemas.

## Known failure modes

- Input exceeds 32 KiB limit — request rejected
- rows array is empty or contains more than 32 items — validation error
- requiredFields array is empty or exceeds 8 entries — rejected
- dataClass not set to 'public' or 'synthetic' — enum validation error
- nonpersonalMetadata not explicitly set to true — request rejected
- Malformed JSON body — parse error returned

## How this service works

Check presence of required backend/run/register/measurement pins; null is missing, not an invalid credential or artifact 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

A field-coverage report indicating which required backend, run, register, and measurement pin fields are present or null across the supplied calibration rows. Null values are flagged as missing. Results are retained for 24 hours; minimal receipt metadata is kept for 90 days. No hardware measurement, recalibration, or scientific certification is performed.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/quantum-calibrations-required-field-coverage-check-92cfd4a4/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)