# RQM Supported Circuit Equivalence

> RQM Supported Circuit Equivalence is a paid API for AI agents from jobs.rqmtechnologies.com, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-13).

Compares two RQM Circuit IR circuits to determine if they are equivalent within a bounded, supported verifier scope

## Facts

- Endpoint: POST https://jobs.rqmtechnologies.com/x402/buyer-jobs/supported-circuit-equivalence-v1
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/rqm-supported-circuit-equivalence-6a99e97d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VAcXuJ-Er6gy7yTwEf0WL

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 rqm-supported-circuit-equivalence-6a99e97d -d '<json body>'
```

Example prompt: Can you check whether my optimized quantum circuit is equivalent to my original reference circuit using RQM's supported equivalence verifier? Here are both circuits as RQM Circuit IR objects — use the auto method and cap spending at 0.1 USDC.

## When to prefer this

Use this endpoint when you need programmatic, bounded equivalence checking between two RQM Circuit IR quantum circuits — especially after optimization, transpilation, or refactoring — and need a verifiable engineering assurance result. Prefer this over manual inspection or simulation-based comparison when you need a structured typed work product confirming equivalence. Do not use if you need a formal mathematical proof, need to execute circuits on a QPU, or if your circuits fall outside the supported verifier scope.

## Known failure modes

- Circuit IR objects fall outside the supported verifier scope — verifier returns out-of-scope or unsupported result
- Malformed or invalid Circuit IR object provided — schema validation error
- max_total_price too low to cover the $0.10 USDC per-call cost — payment rejected
- Idempotency key format invalid — request rejected with validation error
- Network or payment gateway failure during x402 transaction — call fails with payment error

## How this service works

Supported circuit equivalence: Compare two RQM Circuit IR circuits within the supported verifier scope. Use when: Use when a bounded request matches rqm.studio.equivalence-request.v1 and the caller needs the declared type... Returns: equivalent, not-equivalent, or unsupported verdict, verification evidence, input hashes. Boundaries: Deterministic bounded local software evidence; not hardware evidence, a formal proof, certification, sign...

## Output

Returns a typed work product indicating whether the two RQM Circuit IR circuits are equivalent within the supported verifier scope, including the equivalence verdict and bounded engineering assurance evidence. Note: this is engineering assurance, not a formal mathematical proof, and applies only within the declared supported scope.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "request": {
   "type": "object",
   "description": "Supported Circuit Equivalence request metadata is discovery-only while execution is disabled.",
   "additionalProperties": true
  },
  "schema_version": {
   "const": "rqm.jobs.bazaar-buyer-job-request.v1"
  },
  "idempotency_key": {
   "type": "string",
   "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]*$",
   "maxLength": 128,
   "minLength": 1
  },
  "max_total_price": {
   "type": "string",
   "pattern": "^(?:0|[1-9]\\d{0,13})(?:\\.\\d{1,6})?$"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/rqm-supported-circuit-equivalence-6a99e97d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from jobs.rqmtechnologies.com](https://www.zero.xyz/host/jobs.rqmtechnologies.com/llms.txt)