qcoscloud
The customer SDK, CLI and MCP server for SoftQuantus compute — one prepaid wallet across QPU (via QCOS), on-demand GPU (via Softquantus Cloud), and free simulation. The platform Execution Plane authorizes, meters and settles every call; this client never touches a cloud or a credential.
pip install qcoscloud # SDK + CLI
pip install "qcoscloud[mcp]" # + the MCP server for AI agents
export QCOSCLOUD_API_KEY=sq-live-… # create one in the console → API Keys
SDK
from qcoscloud import QCOSCloud
qc = QCOSCloud() # reads QCOSCLOUD_API_KEY
qc.credits() # prepaid balance (USD)
bell = """OPENQASM 2.0;
include "qelib1.inc";
qreg q[2]; creg c[2];
h q[0]; cx q[0],q[1]; measure q -> c;
"""
qc.simulate(qasm=bell, shots=1000) # FREE test simulation
qc.run("ionq.qpu.aria-1", qasm=bell, shots=2000, instance="research")
qc.gpu_job(gpu="a100-80gb", command="python train.py", minutes=30) # GPU
qc.workload(job_id) # status + cost
CLI
qcoscloud credits
qcoscloud computers
qcoscloud instances create research --plan prepaid --qpus ionq.qpu.aria-1
qcoscloud simulate --qasm bell.qasm --shots 1000
qcoscloud run --target ionq.qpu.aria-1 --qasm bell.qasm --shots 2000 --instance research
qcoscloud gpu --type a100-80gb --command "python train.py" --minutes 30
qcoscloud workloads
MCP (for AI agents — the SynapseX Lab, Claude Desktop, Cursor)
python -m qcoscloud.mcp_server # stdio MCP server
Exposes 12 tools: get_credits, list_computers, list_instances,
create_instance, list_targets, run_simulation, run_qpu_job,
run_gpu_job, run_cpu_job, get_workload, get_evidence, and
cancel_workload. An AI can drive compute safely — every run is metered
against the same wallet with the same cost guardrails.
See docs/COMPUTE_INTEGRATION.md (full integration) and
docs/LAB_AI_INSTRUCTIONS.md (desktop lab + AI instructions).
Cost safety
Runs reserve their worst-case cost before provisioning, so you can never
overspend; GPU is stopped/deprovisioned when its reservation is exhausted; the
free plan runs simulators at $0. Errors carry a machine reason
(insufficient_credits, runtime_bound_required, free_plan_limit_met, …)
and a human hint.
Metadata
Release files for qcoscloud 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| qcoscloud-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for qcoscloud-0.1.1-py3-none-any.whl |
Release files / qcoscloud-0.1.1-py3-none-any.whl
| Download URL | qcoscloud-0.1.1-py3-none-any.whl |
|---|---|
| Size | 10.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
176c6771de6556b91e634100324c5da09b6d0e5222b41712b6ac8ab0894114f5
|
|
BLAKE2b-256 checksum How to use checksums |
e0d129980e36d35194d8fa9b5403b9e9e58b64944f47a77ffac1a4ce8314e55c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.7
|
Security for qcoscloud 0.1.1
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.