# Quantum Circuit Records - Provenance Edge Audit

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

Binds declared quantum circuit transformation edges to exact parent/child operation digests and validates parent backend supplied-record analysis for provenance verification.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/quantum-circuit-records/provenance-edge-audit?utm_source=zero.xyz
- Price: $0.04531/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-provenance-edge-audit-37737b1e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ooSyP_HTwsEthI-UnU4I1

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

Example prompt: Audit the provenance of these quantum circuit transformation edges — I have up to 10 edges and 10 nodes and the data is synthetic, nonpersonalMetadata is true — and tell me which edges are correctly bound to their parent/child operation digests and which ones are flagged as missing or mismatched.

## When to prefer this

Use this endpoint when you need to audit the provenance of declared quantum circuit transformation edges against exact parent/child operation digests sourced from a backend supplied-record — particularly for synthetic or public data workflows where nonpersonal metadata is required. Prefer this over independent circuit certification tools when you already have declared edge and node records and need binding verification rather than fresh certification.

## Known failure modes

- edges or nodes arrays empty or exceeding 32-item limit returns validation error
- dataClass not set to 'public' or 'synthetic' causes schema rejection
- nonpersonalMetadata not explicitly set to true causes request rejection
- malformed edge or node objects result in binding failures
- backend supplied-record unavailable for a declared parent causes unresolvable provenance flags

## How this service works

Bind declared circuit transformation edges to exact parent/child operation digests and parent backend Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a provenance audit report binding each declared circuit transformation edge to its exact parent and child operation digests, flagging any missing, mismatched, or unverifiable edges based on the parent backend supplied-record analysis.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "edges": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "nodes": {
   "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-provenance-edge-audit-37737b1e/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)