Open Quantum
How devices with openquantum: IDs work through qBraid: linking an Open Quantum account, how jobs are billed, and what they accept.
Using Open Quantum API credentials of your own, without qBraid? See Open Quantum (self-managed).
Devices whose ID starts with openquantum: run through Open Quantum, using an Open Quantum account you link to qBraid. You still submit with QbraidProvider and your qBraid API key, and jobs appear in your qBraid Quantum Jobs. The difference is billing: these jobs spend your Open Quantum credits, not qBraid credits.
| Device ID | Vendor page |
|---|---|
openquantum:aqt:qpu:ibex-q1 | AQT |
openquantum:ionq:qpu:forte-1 | IonQ |
openquantum:ionq:qpu:forte-enterprise | IonQ |
openquantum:iqm:qpu:garnet | IQM |
openquantum:iqm:qpu:emerald | IQM |
openquantum:rigetti:qpu:cepheus-1-108q | Rigetti |
Before you submit
- Connect an Open Quantum account in Account > Profile > Integrations. See Open Quantum for the steps.
- Check that account’s Open Quantum credit balance. Buying qBraid credits doesn’t add to it.
Then submit as you would to any other device:
from qbraid.runtime import QbraidProvider
provider = QbraidProvider()
device = provider.get_device("openquantum:iqm:qpu:garnet")
bell = """
OPENQASM 3.0;
include "stdgates.inc";
qubit[2] q;
bit[2] c;
h q[0];
cx q[0], q[1];
c = measure q;
"""
job = device.run(bell, shots=100)
print(job.result().data.get_counts())Programs can be written in any framework qBraid supports. qBraid converts them to OpenQASM before they reach Open Quantum.
Execution plans
Open Quantum jobs submitted through qBraid run on Open Quantum’s public execution plan. Requesting any other plan in runtime_options is refused before the job is created.
Related links
- Open Quantum integration: connecting an account, credit types, and troubleshooting
- Run on qBraid: installing the SDK and saving your qBraid API key
- Open Quantum (self-managed):
OpenQuantumProviderwith your own Open Quantum credentials - Open Quantum documentation
Thanks for your feedback.

