The Open Quantum integration lets you submit jobs through qBraid and pay with your connected Open Quantum account’s credits.

A job that costs no qBraid credits can still consume Open Quantum credits. Buying qBraid credits does not fund your Open Quantum balance. Check the provider’s balance and pricing before submitting work.

Create your Open Quantum account

  1. Open Open Quantum and start sign-up.
  2. Complete the provider’s registration and any remaining onboarding steps.
  3. Sign in and review the account’s available credits before connecting it to qBraid.

If Open Quantum displays a welcome-credit offer, follow its claim instructions and confirm that the credits appear in your provider balance. Offer availability and eligibility are controlled by Open Quantum. Welcome credits are not a guaranteed allocation from qBraid.

Connect Open Quantum to qBraid

  1. Sign in to qBraid Account.
  2. Open Account > Profile.
  3. Find Integrations and locate Open Quantum.
  4. Select Connect. Your browser navigates to the Open Quantum authorization flow.
  5. Sign in to the Open Quantum account you want to use and complete authorization.
  6. Wait to return to qBraid Profile, then check the connection as described below.

You can also reach Profile’s connection setup from the connection prompt in Circuit Composer.

Confirm the connection

On success, qBraid displays Open Quantum connected. The Open Quantum entry shows a green status dot, Connected as followed by the linked account, and a Disconnect button. Check that this is the account whose credits you intend to use.

Run a job through qBraid

  1. Open Devices and find the Open Quantum device you want to use.
  2. Check its availability and provider pricing.
  3. Use Circuit Composer or the qBraid Runtime to submit your circuit to that device.
  4. Open Quantum Jobs to inspect the job’s status, results, or error.

For a local Python environment, install the qBraid SDK and configure your qBraid API key. Open Quantum’s installation guide explains local and Lab authentication. Its backend guide lists Open Quantum device identifiers, and its examples provide complete circuits.

Review provider credits

Open the Open Quantum billing page to check the linked account’s balance and transactions. Review consumption and expiration entries if the balance is lower than expected.

Open Quantum distinguishes two credit types:

TypeSource and useProvider’s documented expiration
SparkFree or promotional credits for Public execution plans.90 days after grant.
FullPurchased credits for Public or Private execution plans.12 months.

For Public plans, Open Quantum spends Spark credits before Full credits. Private plans require Full credits. Check the provider’s credit documentation for current terms and its pricing page for rates.

To buy provider credits, open the Open Quantum portal’s credit purchase flow, select an amount, complete Stripe checkout, and confirm the updated provider balance. These credits remain separate from your qBraid wallet.

Disconnect or change accounts

  1. Open Account > Profile > Integrations.
  2. Select Disconnect beside Open Quantum.
  3. Wait for the entry to return to Connect.
  4. To use another Open Quantum account, select Connect, authorize that account, and verify Connected as afterward.

Link an account again before submitting another Open Quantum job through qBraid.

Troubleshoot the connection or a failed job

  • If the connection status cannot load, select Retry. A status-loading error does not establish that the account is disconnected.
  • If authorization fails, return to Profile, select Connect, and complete the flow while signed in to the intended qBraid account.
  • If jobs fail after connection, confirm the Connected as account, check its Open Quantum balance and credit expiration, and inspect the target device’s availability and job error.
  • If Spark credits are available but the selected execution plan requires Full credits, review the provider’s supported plans before retrying.

If the error continues, open Support with the job identifier and error message. Do not include credentials.