Which client should I use?

SoftQuantus ships two client families because there are two doors:

	`qcoscloud` — SoftQuantus Cloud	`softqcos` — QCOS direct
Talks to	`platform.softquantus.com` (Execution Plane)	`api.softquantus.com` (QCOS runtime)
You get	Wallet, budgets, instances, GPU/CPU jobs, billed QPU access, evidence per job	The full runtime contract: jobs, sessions, primitives, QEC, bench, artifacts
Auth env	`QCOSCLOUD_API_KEY`	`QCOS_API_KEY`
Install	`pip install qcoscloud` (PyPI publishing in progress — use REST meanwhile)	`pip install softqcos-sdk softqcos`
MCP	`python -m qcoscloud.mcp_server` (9 tools)	`softqcos-mcp` (71 typed tools, hosted at `mcp.softquantus.com`)
Best for	Product teams consuming compute with cost control	Quantum engineers, research workflows, OEM/on-prem integrations

Rule of thumb: if your workflow starts in the Platform console and spends credits, use qcoscloud (Platform guide). If your workflow is the QCOS runtime itself — circuits, sessions, primitives, evidence — use the softqcos family (SDK introduction). Both families use the same sq-live-... API keys created in the Platform console; only the base URL and env var differ. See Which API key do I need?.

​Which client should I use?

Which client should I use?