TII Quantum Cloud Client
Install
Install first the package dependencies with the following commands.
We recommend to start with a fresh virtual environment to avoid dependencies conflicts with previously installed packages.
python -m venv ./env
source activate ./env/bin/activate
The tii-quantum package can be installed through pip:
pip install tii-quantum
For Jupyter notebook support (including progress bars and rich UI), you can install the optional dependencies:
pip install "tii-quantum[notebook]"
Quick start
Once installed, the provider allows to run quantum circuit computations on remote labs using Qibo.
⚠️ Note: to run jobs on the remote cluster it is mandatory to own a validated account. Please, sign up to your preferred institution to obtain the needed token to run computations on the cluster.
The following snippet provides a basic usage example.
Replace the your-token string with your user token received during the
registration process. To check which devices are available with your account
please visit the dashboard at your institution.
import qibo
import tii_quantum
# create the circuit you want to run
circuit = qibo.models.QFT(5)
# authenticate to server through the client instance
token = "your-token"
client = tii_quantum.Client(token)
# run the circuit
device = "device_name"
project = "project_name"
job = client.run_circuit(circuit, device=device, project=project, nshots=1024)
result = job.result()
print(result)
The device name indicates the specific system or machine that will process the
job. The project name corresponds to the project or group to which the user
belongs and which will be charged for the service usage.
MCP server
If you want to interact with TII Q-Cloud from an LLM agent, the
tii-quantum-mcp package
provides an MCP server built on top of this
client. It lets agents submit circuits, track job status, retrieve results, and
inspect quotas through standard MCP tools.
Metadata
Release files for tii-quantum 0.1.3
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 | Actions |
|---|---|---|---|---|
| tii_quantum-0.1.3.tar.gz | 23.9 kB | Without provenance | Details for tii_quantum-0.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tii_quantum-0.1.3-py3-none-any.whl | Python 3 | none | any | Details for tii_quantum-0.1.3-py3-none-any.whl |
Total release size: 52.2 kB
Release files / tii_quantum-0.1.3.tar.gz
| Download URL | tii_quantum-0.1.3.tar.gz |
|---|---|
| Size | 23.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bb28b8cc3bbcfcfd33b15b7889967f3ee8cd2c0e5ee5caee1db1ab2ef1f57f26
|
|
BLAKE2b-256 checksum How to use checksums |
de706e9ddcd3e5df52f65e523313ec8a4b2ed3234a3bd2f5fe04f0bfc54ed9e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / tii_quantum-0.1.3-py3-none-any.whl
| Download URL | tii_quantum-0.1.3-py3-none-any.whl |
|---|---|
| Size | 28.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e641326bfa0322e1d02a21cda5c61116ec69f9db0783082974bf825ae611d780
|
|
BLAKE2b-256 checksum How to use checksums |
2980c23923a831794d261ac47fbe48ea9648fe4ea6adc2ac0a729bc244070866
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for tii-quantum 0.1.3
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.