Workload specific
Every route begins with circuit requirements and explicit user constraints.
THE QUANTUM EXECUTION LAYER
Hard constraints first. Eligible candidates ranked by projected quality, queue, cost, and reliability. Full decision trace on every job.
▸ Circuit profile01 / 05
NETWORK
Past and present affiliations of individual advisors and supporters. Organizations shown do not imply institutional endorsement.
// 01 — BUILT FOR QUANTUM WORKLOADS
Every route begins with circuit requirements and explicit user constraints.
Review estimated execution cost and routing inputs before provider submission.
Use one request and one result lifecycle across configured backends.
Preserve candidate scores, rejection reasons, and the selected route.
// 02 — QCI ENGINE
QCI combines circuit compatibility, projected execution quality, queue time, cost, reliability, and user constraints into a workload-specific route decision.
The selected route should not simply be the fastest, cheapest, or highest-fidelity option. Hard constraints are applied first; eligible candidates are then ranked under the chosen policy.
01 / Route
02 / Transpile
OPENQASM 2 · BELL.QASMh q[0];
cx q[0], q[1];
measure q -> c;DEPTH 4 · 2 GATES→QCI AER GPU · LOCALh q[0];
cx q[0],q[1];
measure q -> c;OPT LEVEL 2 · ARTIFACT SAVED03 / Price
per QPU-hour
04 / Deploy
UNIFIED API
Submit Qiskit or OpenQASM once. QCI applies constraints, produces the quote, and returns a normalized job lifecycle regardless of provider.
qci_live_your_workspace_keycurl https://api.qrouter.dev/api/v1/jobs \
-H "Authorization: Bearer $QROUTER_API_KEY" \
-H "Idempotency-Key: bell-001" \
-H "Content-Type: application/json" \
-d '{
"circuit": "OPENQASM 2.0; ...",
"shots": 1024,
"target": "auto",
"routing_mode": "balanced"
}'{ "id": "job_qr_7c91", "backend": "ibm-brisbane", "quote": "$0.658", "status": "submitted" }