# Quantum Benchmark Comparability Checker

> Quantum Benchmark Comparability Checker is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.010039/call, status unknown (last checked 2026-10-15).

Compares two structured quantum benchmark declarations (protocol, workload, metric, noise, overhead) and flags mismatches that would make them incomparable.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/quantum/benchmark-comparability?utm_source=zero.xyz
- Price: $0.010039/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantum-benchmark-comparability-checker-4c9af92d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gOU89pSLesOau_ZfgJ6uM

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-benchmark-comparability-checker-4c9af92d -d '<json body>'
```

Example prompt: Check whether my baseline and candidate quantum benchmarks are comparable — the baseline uses a circuit-layer protocol with depolarizing noise and gate-count metrics, the candidate uses the same workload but reports fidelity instead, both are synthetic data — flag any mismatches that would make them incomparable.

## When to prefer this

Choose this endpoint when you need to programmatically verify that two quantum benchmark declarations are structurally comparable before combining, citing, or analyzing their results. It is purpose-built for quantum benchmarking contexts (protocol, workload, noise, overhead) rather than generic schema diffing or data validation tools. Use it as a preflight step before quantum performance analysis pipelines or when comparing benchmark claims across teams or vendors.

## Known failure modes

- Malformed baseline or candidate objects cause a 400 validation error
- Invalid or missing dataClass enum value (must be 'public' or 'synthetic') causes rejection
- Labels flagged as mismatched may not reflect true incompatibility since labels are not independently validated
- Empty or incomplete benchmark declarations may produce incomplete mismatch detection
- Service returns no comparability guarantee beyond structural declaration matching

## How this service works

Compare structured benchmark protocol, workload, metric, noise and overhead declarations. Flags mismatches; labels are not independently validated. New modular adapter: retained result recovery for 24 hours, minimal receipt metadata for 90 days. Existing live route unchanged.

## Output

Returns a structured comparability report identifying mismatches between the baseline and candidate benchmark declarations across protocol, workload, metric, noise, and overhead dimensions. Labels flagged mismatches but does not independently validate the underlying label claims. Results are retained for 24 hours; minimal receipt metadata is kept for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "baseline": {
   "type": "object"
  },
  "candidate": {
   "type": "object"
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/quantum-benchmark-comparability-checker-4c9af92d/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)