# Quantum Circuit Records - Required Field Coverage

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

Checks for the presence of required field pins (backend, circuit, register, operation) in quantum circuit metadata records, flagging null values as missing rather than invalid.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/quantum-circuit-records/required-field-coverage?utm_source=zero.xyz
- Price: $0.010117/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantum-circuit-records-required-field-coverage-58a12f6a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_an1-FSmzmoCH1dV8ekvoV

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-circuit-records-required-field-coverage-58a12f6a -d '<json body>'
```

Example prompt: Can you check these 10 quantum circuit metadata rows — marked as public and nonpersonal — for required field coverage against the fields 'backend', 'circuit', 'register', and 'operation', and tell me which ones have nulls?

## When to prefer this

Use this endpoint when you need a lightweight, stateless check for required field presence across quantum circuit metadata records without any quantum simulation, execution, or scientific validation. Prefer this over general schema validators when dealing specifically with quantum backend/circuit/register/operation pin structures and when your data is public or synthetic nonpersonal metadata within 32 rows and 8 required fields.

## Known failure modes

- Payload exceeds 32 KiB input limit — request rejected
- More than 32 rows submitted — exceeds maxItems limit
- requiredFields array is empty or exceeds 8 items — schema validation error
- nonpersonalMetadata not set to true — request rejected
- dataClass not one of 'public' or 'synthetic' — enum validation error
- Result unavailable after 24-hour retention window — data expired

## How this service works

Check presence of required backend/circuit/register/operation pins; null is missing, not an invalid credential or artifact for bounded backend/circuit/register/operation-pin records. Caller-supplied public/synthetic nonpersonal metadata only. No quantum simulation, device/API access, execution, calibration measurement, scientific validation or claim of circuit equivalence. Input limit: 32 KiB. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a coverage report for each submitted row indicating whether each required field pin is present (non-null) or missing (null), without performing any quantum simulation, execution, or scientific validation.

## 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-circuit-records-required-field-coverage-58a12f6a/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)