# Quantum Circuit Records - Source Coverage Map

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

Binds record references to an owner/subject/revision/content/source frame and maps source coverage across quantum circuit backend/register/operation-pin records without independent certification.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/quantum-circuit-records/source-coverage-map?utm_source=zero.xyz
- Price: $0.035129/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantum-circuit-records-source-coverage-map-f12d6adb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EPYZzh7_BQbxPlN0svCBz

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-source-coverage-map-f12d6adb -d '<json body>'
```

Example prompt: Can you run a source coverage map on these 12 quantum circuit records using public data class — I need to see how well the sources bind to the owner, subject, revision, and content pins across each row?

## When to prefer this

Choose this endpoint when you need to systematically map and audit declared source coverage across a bounded set of quantum circuit or register records, specifically when you want to bind owner/subject/revision/content frame references to source declarations. Prefer this over generic record validation when your records are scoped to circuit backend, register, or operation-pin contexts and you need structured coverage output per source frame.

## Known failure modes

- rows or sources arrays outside 1–32 item bounds returns validation error
- dataClass value other than 'public' or 'synthetic' is rejected
- nonpersonalMetadata not set to true (const) causes schema rejection
- malformed or unrecognized record row formats may yield incomplete coverage declarations
- no independently verified certification of source bytes — declared analysis only

## How this service works

Bind record references to an exact owner/subject/revision/content/source frame; hash-shaped strings are declarations, not independently verified source bytes for bounded backend/circuit/register/operation-pin Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured source coverage map declaring how each supplied record row binds to its owner/subject/revision/content/source frame, identifying coverage gaps and frame-to-source associations. Results are declared analysis outputs, not independently verified certifications of the underlying source bytes.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "sources": {
   "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-circuit-records-source-coverage-map-f12d6adb/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)