Browse documentation
Projects
Projects & collaborationHelp
TroubleshootingDocs / Providers & data / IBM Quantum
Connect IBM Quantum
Connect an IBM Cloud API key to Spinorio for server-side IBM job synchronization and live compiler hardware discovery.
What the connection does
- Validates the IBM Cloud API key through IBM IAM before marking the provider Connected.
- Stores the credential encrypted in the Spinorio control plane; the raw key is not returned by the provider-connection API or added to notebook telemetry.
- Allows the control plane to synchronize eligible captured IBM job status/metrics/results after the notebook or kernel closes.
- Allows Spinorio Compiler to list accessible IBM service instances and discover instance-scoped QPUs for manual compilation-target selection.
The connected credential is not injected into notebook code. If your notebook directly creates QiskitRuntimeService(), authenticate that notebook using the supported Qiskit/IBM mechanism separately.
Connect from Workflow
- 1Prepare IBM access
Use an IBM Cloud account with access to an IBM Quantum service instance and create an IBM Cloud API key.
- 2Open Provider Connections
In Spinorio Lab, open Workflow and locate Provider Connections → IBM Quantum.
- 3Paste the key
Enter the IBM Cloud API key and select Connect IBM Quantum.
- 4Wait for validation
Spinorio validates the key automatically. There is no separate Verify button.
- 5Confirm Connected
The card can show automatic sync status, pending/synchronized job counts, last verification, and any provider error.
Remote job synchronization
When an eligible IBM job identity and service-instance context have been captured, the provider worker can use the stored credential to query IBM after the notebook is no longer running. Historical Workflow records remain if the connection is later disconnected.
Completed jobs can request Refresh from IBM from their Job page. Result retrieval is independent from metrics retrieval; unsupported, missing, or exhausted result retrieval is surfaced explicitly.
Credential handling
- The control plane encrypts stored provider credentials with deployment-owned authenticated encryption and binds them to the Spinorio user/workspace/provider context.
- The native notebook sensor does not receive the stored IBM API key.
- Compiler workers receive validated target configuration, not the IBM API key.
- Project sharing never grants another member the owner’s IBM credential.
Do not place the key in public notebooks, screenshots, support requests, source files, or project-shared notebook cells.