# RQM Circuit Assurance Report

> RQM Circuit Assurance Report 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-14).

Validates, compiles, and reports bounded assurance evidence for an OpenQASM 3 circuit, returning a structured work product confirming engineering-level correctness.

## Facts

- Endpoint: POST https://jobs.rqmtechnologies.com/x402/buyer-jobs/circuit-assurance-report-v1
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/rqm-circuit-assurance-report-84b92227
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_SoepYmlIR1ddz3zgtDn32

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-circuit-assurance-report-84b92227 -d '<json body>'
```

Example prompt: Can you validate this OpenQASM 3 circuit and give me a bounded assurance report using the conservative profile? Here's the source: `OPENQASM 3.0; qubit[2] q; h q[0]; cx q[0], q[1];`

## When to prefer this

Choose this endpoint when you need a bounded engineering assurance report for an OpenQASM 3 circuit — especially when you need a typed, documented work product as evidence (e.g. for compliance, audit, or pre-QPU validation). Prefer this over local simulators when you need a structured, externally-generated assurance artifact. Do not use if you only need local deterministic execution or a formal mathematical proof.

## Known failure modes

- Invalid or malformed OpenQASM 3 source returns a validation error with diagnostic details
- Unsupported gate sets or constructs outside the bounded verifier scope return a scope-exceeded error
- Payment authorization failure or insufficient max_total_price causes rejection before execution
- Idempotency key collision with differing request body may cause conflict error
- Source that is valid syntax but fails compilation returns a failed compilation status with evidence

## How this service works

Circuit assurance report: Validate, compile, and report bounded assurance evidence for OpenQASM 3. Use when: Use when a bounded request matches rqm.studio.circuit-assurance-request.v1 and the caller needs the declare... Returns: assurance outcome, warnings, normalized source and evidence. Boundaries: Deterministic bounded local software evidence; not hardware evidence, a formal proof, certification, sign...

## Output

A structured bounded assurance report containing validation results, compilation outcome, and typed engineering evidence for the submitted OpenQASM 3 circuit. The report is scoped to bounded assurance (not a formal mathematical proof) and includes status, any diagnostic messages, and the declared typed work product artifact.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "request": {
   "type": "object",
   "description": "Circuit Assurance Report 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-circuit-assurance-report-84b92227/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)