qbraid-core
Python library providing core abstractions for software development within the qBraid ecosystem, and a low-level interface to a growing array of qBraid cloud services. The qbraid-core package forms the foundational base for the qBraid CLI, the qBraid SDK, and qBraid Lab.
You can find the latest, most up to date, documentation here, including a list of services that are supported.
See also: qbraid-core-js
Getting Started
You can install qbraid-core from PyPI with:
python -m pip install qbraid-core
Local configuration
After installing qbraid-core, you must configure your account credentials:
- Create a qBraid account or log in to your existing account by visiting account.qbraid.com
- Navigate to Account > API Keys in the left-sidebar, and then click "Create API Key". See API Key docs.
- Save your API key from step 2 in local configuration file. On Linux and macOS, this file is located at
~/.qbraid/qbraidrc, where~corresponds to your home ($HOME) directory. On Windows, the equivalent default location is%USERPROFILE%\.qbraid\qbraidrc.
[default]
api-key = YOUR_KEY
url = https://api-v2.qbraid.com/api/v1
Or generate your ~/.qbraid/qbraidrc file via the qbraid-core Python interface:
>>> from qbraid_core import QbraidSessionV1
>>> session = QbraidSessionV1(api_key='API_KEY')
>>> session.save_config()
>>> session.get_available_services()
['agents', 'compute', 'environments', 'projects', 'runtime', 'skills', 'storage']
Other credential configuration methods are available using the qBraid-CLI.
Verify setup
After configuring your qBraid credentials, verify your setup by running the following from a Python interpreter:
>>> import qbraid_core
>>> quantum_runtime_client = qbraid_core.client('runtime')
>>> devices = quantum_runtime_client.list_devices()
>>> for device in devices:
... print(device.qrn, device.status)
Community
- For feature requests and bug reports: Submit an issue
- For discussions and/or specific questions about qBraid services, join our discord community
- For questions that are more suited for a forum, post to Stack Overflow with the
qbraidtag.
Release files for qbraid-core 0.6.31
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| qbraid_core-0.6.31.tar.gz | 609.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| qbraid_core-0.6.31-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.1 MB
Release files / qbraid_core-0.6.31.tar.gz
| Download URL | qbraid_core-0.6.31.tar.gz |
|---|---|
| Size | 609.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1566d3ad2cf1fc592a42e2b766431bddb010d49750e5ced3f05cc26fe9391b66
|
|
BLAKE2b-256 checksum How to use checksums |
c951e852c5921f483d00dc0c4fbb93aed57a4a77d93ef7de7ae105e3bcbf87ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / qbraid_core-0.6.31-py3-none-any.whl
| Download URL | qbraid_core-0.6.31-py3-none-any.whl |
|---|---|
| Size | 478.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a2093a504e1d633e9849f8577f1e0441ae2034fffaf541cc4ca4f109baee5091
|
|
BLAKE2b-256 checksum How to use checksums |
845053c207fafb63989fc4c1c43a3f7299854af0fc3e1aa75fec2a9c57abb9cb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for qbraid-core 0.6.31
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
