Python interface for the National Quantum Computing Testbed (NQCT).
The NQCT Python SDK lets researchers and developers work with NQCT programmatically from Python, Jupyter notebooks, scripts, and automated workflows. Use it to discover available quantum computing resources, submit work, monitor jobs, and retrieve results.
The SDK provides programmatic access to the same NQCT environment available through the NQCT Cloud portal (see Developer documentation).
NQCT is an evolving platform. We welcome feedback, bug reports, feature requests, and complaints. See Feedback and support below.
Getting started
The easiest way to get started is through the example Jupyter notebooks in this repository.
They are designed to take you from your first connection to NQCT through progressively more advanced workflows.
New to the SDK? Start here:
- Get an NQCT account and API key.
- Install the Python SDK.
- Open the Getting Started notebook.
- Follow the examples and adapt them to your own work.
- Explore the other notebooks as you become familiar with the platform.
Installation
Install the SDK using Python's package manager:
pip install nqct
You will also need an NQCT API key to access the platform. API keys are managed through your NQCT account.
Feedback and support
NQCT is an active research and development platform, and user feedback is an important part of its development.
If you encounter a problem, have a feature request, disagree with how something works, or simply have feedback about your experience, please open an issue on GitHub.
GitHub Issues are also the preferred forum for discussion and feedback.
Open an issue or join the discussion.
Related resources
| Resource | Description |
|---|---|
| NQCT Cloud | NQCT web portal |
| NQCT Python SDK | This repository |
| NQCT Cloud platform | NQCT platform and API |
| NQCT API documentation | API reference |
Project status
The NQCT Python SDK is under active development.
Current functionality and interfaces may evolve as the NQCT platform develops. See the CHANGELOG for significant changes between releases.
For the latest information about supported capabilities, see the example notebooks and current technical documentation.
1 maintainer
Metadata
1 maintainer
Release files for nqct 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| nqct-0.3.0.tar.gz | 345.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nqct-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 375.5 kB
Release files / nqct-0.3.0.tar.gz
| Download URL | nqct-0.3.0.tar.gz |
|---|---|
| Size | 345.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
25f521b8f4595f97511b44ac5779f014cf2455655b2362a160372a2e50f2a611
|
|
BLAKE2b-256 checksum How to use checksums |
35887502bd14f5efc562fcd3890a69b5887040eec753fcd363eede8a2d8fa7ed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 7, 2026.
Transparency logRelease files / nqct-0.3.0-py3-none-any.whl
| Download URL | nqct-0.3.0-py3-none-any.whl |
|---|---|
| Size | 29.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
631154255f31457bf0e6c7084c5ea30fbcb25a610ec7fe80d2fe33faa90c00e9
|
|
BLAKE2b-256 checksum How to use checksums |
b599a52081fbc1c879438dcd5501460a006ef23196dfccb9fa3379d31e133795
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 7, 2026.
Transparency log
