# Quantum Calibrations Provenance Edge Audit

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

Binds measurement-to-configuration edges to exact backend, register-count, revision, and measurement-content supplied-record analysis for quantum calibration data.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/quantum-calibrations/provenance-edge-audit?utm_source=zero.xyz
- Price: $0.045311/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-provenance-edge-audit-86cf11fd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8vr7VF2vMwhPnDehllSq6

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-provenance-edge-audit-86cf11fd -d '<json body>'
```

Example prompt: Audit the provenance edges binding my quantum calibration measurements to their configurations — I have 5 measurements, 5 configurations, and 3 edges, all classified as synthetic data, with no personal metadata.

## When to prefer this

Use this endpoint when you need to audit and bind quantum calibration measurement-to-configuration provenance edges, specifically linking records to exact backend, register-count, and revision identifiers. Prefer this over generic record-linkage endpoints when the domain is quantum computing calibration data and you need edge-level provenance analysis on supplied records (not independent third-party certification).

## Known failure modes

- edges array empty or exceeds 32 items — rejected
- measurements or configurations arrays out of 1–32 bounds — rejected
- dataClass not one of 'public' or 'synthetic' — validation error
- nonpersonalMetadata not explicitly set to true — request rejected
- mismatched edge references that cannot be resolved against supplied measurements/configurations — partial or failed binding report
- malformed edge objects — schema validation error

## How this service works

Bind measurement-to-configuration edges to exact backend/register-count/revision and measurement-content Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns an analysis binding the supplied measurement-to-configuration edges to exact backend, register-count, revision, and measurement-content records. Produces a supplied-record provenance report (not independent certification) confirming or flagging edge bindings based on the provided data.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/quantum-calibrations-provenance-edge-audit-86cf11fd/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)