qubitra-sdk 0.1.0__tar.gz

qubitra_sdk-0.1.0/.gitignore

@@ -0,0 +1,12 @@
+# Docs-site build output and Astro's generated types. The generated SDK reference
+# (docs/src/data/reference.json) is NOT ignored — it is committed, so the site builds
+# without a Python toolchain.
+docs/dist/
+docs/.astro/
+# Astro writes its content/type declarations to <root>/.astro regardless of `cacheDir`.
+.astro/
+
+# Also load-bearing for packaging: hatchling builds the sdist from this directory and
+# honours this file, so anything listed here stays out of the distribution. Without the
+# line below a source distribution swallows the whole docs-site dependency tree.
+node_modules/

qubitra_sdk-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

qubitra_sdk-0.1.0/PKG-INFO

@@ -0,0 +1,128 @@
+Metadata-Version: 2.5
+Name: qubitra-sdk
+Version: 0.1.0
+Summary: Qubitra Python SDK (ADR-0041, codename niobium) — the brand-owning qubitra.* facade over a provider-adapter seam; targets the Qubitra API's /v1 surface.
+Project-URL: Homepage, https://github.com/Qubitra/q-platform
+Project-URL: Repository, https://github.com/Qubitra/q-platform
+Project-URL: Issues, https://github.com/Qubitra/q-platform/issues
+Project-URL: Changelog, https://github.com/Qubitra/q-platform/blob/main/pkg/niobium/CHANGELOG.md
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: qpu,quantum,quantum-computing,qubitra,sdk
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Scientific/Engineering :: Physics
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Requires-Dist: httpx>=0.28
+Requires-Dist: pydantic>=2.5
+Description-Content-Type: text/markdown
+
+# niobium — the Qubitra Python SDK
+
+The Python client for the Qubitra platform. Codename `niobium`; it installs as
+`qubitra-sdk` and imports as `qubitra` (ADR-0041 D1).
+
+The SDK speaks q-platform vocabulary — Backends, Jobs, Offerings — and talks to the
+Qubitra API's public `/v1` surface. Which backend a Job actually lands on, and the
+supply chain behind it, is the platform's business: the SDK never names a vendor.
+
+## Install
+
+```bash
+pip install qubitra-sdk
+```
+
+Inside this repo it is a uv workspace member, so `uv sync` at the root installs it
+editable and no publish step is involved.
+
+## Quickstart
+
+```python
+from qubitra import QubitraClient
+
+with QubitraClient() as client:
+    for backend in client.backends.list():
+        print(backend.id, backend.qubit_count, backend.supported_formats)
+
+    job = client.jobs.submit(
+        backend_id="qpu-superconducting-127q",
+        circuit="OPENQASM 3.0; qubit[2] q; bit[2] c; h q[0]; cx q[0], q[1]; c = measure q;",
+        shots=1024,
+        name="bell-pair",
+    )
+
+    job = client.jobs.wait(job.id, timeout=600)
+    if job.status.is_terminal and job.error:
+        raise SystemExit(f"job {job.id} failed: {job.error}")
+
+    print(client.jobs.result(job.id).counts)   # {"00": 512, "11": 512}
+```
+
+Two runnable versions of that sit in `examples/`: `submit_bell_pair.py` is the whole path,
+and `list_backends.py` is the read-only smoke test. Both take their key from the environment:
+
+```bash
+QUBITRA_API_KEY=qpk_... uv run pkg/niobium/examples/submit_bell_pair.py
+```
+
+Against a local stack (`mise run dev:qplat`), add `QUBITRA_API_URL=http://localhost:8080` and
+mint a key on the console's API keys page.
+
+## Configuration
+
+| Variable | Default | Meaning |
+| --- | --- | --- |
+| `QUBITRA_API_KEY` | — | API key (`qpk_…`), required. Resolves to your organization. |
+| `QUBITRA_API_URL` | `http://localhost:8080` | The Qubitra deployment to reach. |
+
+Both are also constructor arguments — `QubitraClient(api_key=…, api_url=…)` — which
+take precedence over the environment.
+
+## Surface
+
+| Call | What it does |
+| --- | --- |
+| `client.backends.list()` / `.get(id)` | The backends available to you, and one by id. |
+| `client.jobs.submit(...)` | Submit a circuit; returns a `Job` immediately. |
+| `client.jobs.list()` | Your organization's jobs, newest first. |
+| `client.jobs.get(id)` / `.result(id)` / `.cancel(id)` | Read status, fetch counts, cancel. |
+| `client.jobs.wait(id)` | Poll until the Job reaches a terminal status. |
+| `client.marketplace.offerings()` | The marketplace catalogue. |
+
+`jobs.result` is valid once a Job is `COMPLETED`; asking earlier raises
+`InvalidRequestError`.
+
+Every failure is a `QubitraError`: `AuthenticationError`, `NotFoundError`,
+`InvalidRequestError`, `InsufficientCreditsError`, or `ProviderError`. Each carries
+the platform's RFC 9457 Problem Details body (ADR-0008) on `.detail` and its HTTP
+status on `.status_code`.
+
+Models are frozen pydantic models; the package ships `py.typed`, so a caller's type
+checker sees the whole surface.
+
+## Layout
+
+- `src/qubitra/` — the public facade: `client.py`, `models.py`, `errors.py`,
+  `credentials.py`.
+- `src/qubitra/_providers/` — the adapter seam (ADR-0041 D2). `base.py` is the
+  protocol the facade depends on; `qubitra.py` implements it over `/v1`. A second
+  platform slots in here without touching the facade.
+- `tests/` — facade behaviour over a fake adapter, plus contract tests driving the
+  adapter's real request path against an httpx `MockTransport`.
+
+The SDK is synchronous (ADR-0041 D7); client objects own their transport, so an
+async twin is additive.
+
+## Tasks
+
+```bash
+mise exec -- uv run pytest pkg/niobium -q     # tests
+mise exec -- mypy pkg/niobium                 # types
+mise exec -- ruff check pkg/niobium           # lint
+```

qubitra_sdk-0.1.0/README.md

@@ -0,0 +1,103 @@
+# niobium — the Qubitra Python SDK
+
+The Python client for the Qubitra platform. Codename `niobium`; it installs as
+`qubitra-sdk` and imports as `qubitra` (ADR-0041 D1).
+
+The SDK speaks q-platform vocabulary — Backends, Jobs, Offerings — and talks to the
+Qubitra API's public `/v1` surface. Which backend a Job actually lands on, and the
+supply chain behind it, is the platform's business: the SDK never names a vendor.
+
+## Install
+
+```bash
+pip install qubitra-sdk
+```
+
+Inside this repo it is a uv workspace member, so `uv sync` at the root installs it
+editable and no publish step is involved.
+
+## Quickstart
+
+```python
+from qubitra import QubitraClient
+
+with QubitraClient() as client:
+    for backend in client.backends.list():
+        print(backend.id, backend.qubit_count, backend.supported_formats)
+
+    job = client.jobs.submit(
+        backend_id="qpu-superconducting-127q",
+        circuit="OPENQASM 3.0; qubit[2] q; bit[2] c; h q[0]; cx q[0], q[1]; c = measure q;",
+        shots=1024,
+        name="bell-pair",
+    )
+
+    job = client.jobs.wait(job.id, timeout=600)
+    if job.status.is_terminal and job.error:
+        raise SystemExit(f"job {job.id} failed: {job.error}")
+
+    print(client.jobs.result(job.id).counts)   # {"00": 512, "11": 512}
+```
+
+Two runnable versions of that sit in `examples/`: `submit_bell_pair.py` is the whole path,
+and `list_backends.py` is the read-only smoke test. Both take their key from the environment:
+
+```bash
+QUBITRA_API_KEY=qpk_... uv run pkg/niobium/examples/submit_bell_pair.py
+```
+
+Against a local stack (`mise run dev:qplat`), add `QUBITRA_API_URL=http://localhost:8080` and
+mint a key on the console's API keys page.
+
+## Configuration
+
+| Variable | Default | Meaning |
+| --- | --- | --- |
+| `QUBITRA_API_KEY` | — | API key (`qpk_…`), required. Resolves to your organization. |
+| `QUBITRA_API_URL` | `http://localhost:8080` | The Qubitra deployment to reach. |
+
+Both are also constructor arguments — `QubitraClient(api_key=…, api_url=…)` — which
+take precedence over the environment.
+
+## Surface
+
+| Call | What it does |
+| --- | --- |
+| `client.backends.list()` / `.get(id)` | The backends available to you, and one by id. |
+| `client.jobs.submit(...)` | Submit a circuit; returns a `Job` immediately. |
+| `client.jobs.list()` | Your organization's jobs, newest first. |
+| `client.jobs.get(id)` / `.result(id)` / `.cancel(id)` | Read status, fetch counts, cancel. |
+| `client.jobs.wait(id)` | Poll until the Job reaches a terminal status. |
+| `client.marketplace.offerings()` | The marketplace catalogue. |
+
+`jobs.result` is valid once a Job is `COMPLETED`; asking earlier raises
+`InvalidRequestError`.
+
+Every failure is a `QubitraError`: `AuthenticationError`, `NotFoundError`,
+`InvalidRequestError`, `InsufficientCreditsError`, or `ProviderError`. Each carries
+the platform's RFC 9457 Problem Details body (ADR-0008) on `.detail` and its HTTP
+status on `.status_code`.
+
+Models are frozen pydantic models; the package ships `py.typed`, so a caller's type
+checker sees the whole surface.
+
+## Layout
+
+- `src/qubitra/` — the public facade: `client.py`, `models.py`, `errors.py`,
+  `credentials.py`.
+- `src/qubitra/_providers/` — the adapter seam (ADR-0041 D2). `base.py` is the
+  protocol the facade depends on; `qubitra.py` implements it over `/v1`. A second
+  platform slots in here without touching the facade.
+- `tests/` — facade behaviour over a fake adapter, plus contract tests driving the
+  adapter's real request path against an httpx `MockTransport`.
+
+The SDK is synchronous (ADR-0041 D7); client objects own their transport, so an
+async twin is additive.
+
+## Tasks
+
+```bash
+mise exec -- uv run pytest pkg/niobium -q     # tests
+mise exec -- mypy pkg/niobium                 # types
+mise exec -- ruff check pkg/niobium           # lint
+```

qubitra_sdk-0.1.0/examples/list_backends.py

@@ -0,0 +1,25 @@
+"""Live smoke: list backends and marketplace offerings through the SDK.
+
+Run against a Qubitra deployment with an API key::
+
+    QUBITRA_API_KEY=qpk_... QUBITRA_API_URL=http://localhost:8080 \
+        uv run pkg/niobium/examples/list_backends.py
+"""
+
+from qubitra import QubitraClient
+
+
+def main() -> None:
+    with QubitraClient() as client:
+        for backend in client.backends.list():
+            kind = backend.type.value if backend.type else "?"
+            qubits = f"{backend.qubit_count}q" if backend.qubit_count else ""
+            state = "available" if backend.available else "unavailable"
+            print(f"{backend.id:32} {kind:10} {qubits:6} {state:12} {backend.name or ''}")
+        print()
+        for offering in client.marketplace.offerings():
+            print(f"{offering.id:38} {offering.type.value:14} {offering.name or ''}")
+
+
+if __name__ == "__main__":
+    main()

qubitra_sdk-0.1.0/examples/submit_bell_pair.py

@@ -0,0 +1,119 @@
+"""Live smoke: dispatch a workload and read its measured counts.
+
+Submits a Bell pair, waits for the platform to run it, and prints the counts. This is the
+whole path — SDK to the Qubitra API to a Temporal workflow to whichever backend the identifier
+resolves to — so it failing says something real about the stack rather than about the SDK.
+
+Run it against a Qubitra deployment with an API key::
+
+    QUBITRA_API_KEY=qpk_... uv run pkg/niobium/examples/submit_bell_pair.py
+
+Against a local stack (``mise run dev:qplat``), point it at onyx as well. Create a key on the
+console's API keys page, or mint one with an OIDC token::
+
+    QUBITRA_API_KEY=qpk_... QUBITRA_API_URL=http://localhost:8080 \
+        uv run pkg/niobium/examples/submit_bell_pair.py
+
+Pass a backend id as the first argument to choose one; the default is a simulator, which is
+where a circuit belongs until it is worth queueing for hardware. Pass a circuit format as the
+second (``OPENQASM_2`` / ``OPENQASM_3``) to force one — otherwise the backend's own
+``supported_formats`` decides, because backends differ in what they accept and the newest
+format is not always the one available.
+"""
+
+from __future__ import annotations
+
+import sys
+
+from qubitra import CircuitFormat, QubitraClient
+
+# A Bell pair: entangle two qubits, measure both. On a simulator the counts land almost
+# entirely on "00" and "11", so a result that is spread across all four outcomes is a
+# visible sign something ran the wrong circuit.
+BELL = {
+    CircuitFormat.OPENQASM_3: """
+OPENQASM 3.0;
+qubit[2] q;
+bit[2] c;
+h q[0];
+cx q[0], q[1];
+c = measure q;
+""",
+    # Backends differ in what they accept, and not every one has caught up to OpenQASM 3 —
+    # `client.backends.list()` reports each one's `supported_formats`.
+    CircuitFormat.OPENQASM_2: """
+OPENQASM 2.0;
+include "qelib1.inc";
+qreg q[2];
+creg c[2];
+h q[0];
+cx q[0],q[1];
+measure q -> c;
+""",
+}
+
+DEFAULT_BACKEND = "sim-statevector-30q"
+SHOTS = 1024
+
+# Preferred first: OpenQASM 3 where a backend takes it, OpenQASM 2 otherwise.
+PREFERENCE = (CircuitFormat.OPENQASM_3, CircuitFormat.OPENQASM_2)
+
+
+def pick_format(client: QubitraClient, backend_id: str) -> CircuitFormat:
+    """The best format this backend accepts, out of the ones this circuit is written in.
+
+    A backend reports what it accepts, and a backend that reports nothing places no
+    constraint of its own — so an empty list means the newest format is worth trying rather
+    than that nothing is.
+    """
+    accepted = set(client.backends.get(backend_id).supported_formats)
+    if not accepted:
+        return PREFERENCE[0]
+    for candidate in PREFERENCE:
+        if candidate in accepted:
+            return candidate
+    raise SystemExit(
+        f"{backend_id} accepts {sorted(accepted)}, and this example writes only "
+        f"{[f.value for f in PREFERENCE]}"
+    )
+
+
+def main() -> int:
+    backend_id = sys.argv[1] if len(sys.argv) > 1 else DEFAULT_BACKEND
+    forced = CircuitFormat(sys.argv[2]) if len(sys.argv) > 2 else None
+
+    with QubitraClient() as client:
+        circuit_format = forced or pick_format(client, backend_id)
+        print(f"using {circuit_format}")
+
+        job = client.jobs.submit(
+            backend_id=backend_id,
+            circuit=BELL[circuit_format],
+            circuit_format=circuit_format,
+            shots=SHOTS,
+            name="bell-pair example",
+        )
+        # submit returns once the platform has accepted the job, not once it has run, so the
+        # first status is PENDING and the id is what everything else is addressed by.
+        print(f"submitted {job.id} to {backend_id} — {job.status}")
+
+        job = client.jobs.wait(job.id, timeout=120, poll_interval=2)
+        print(f"finished  {job.id} — {job.status}")
+
+        if job.status.value != "COMPLETED":
+            # A failed job is a result too, and its error is the useful part.
+            print(f"job did not complete: {job.error or '(no error recorded)'}", file=sys.stderr)
+            return 1
+
+        result = client.jobs.result(job.id)
+        counts = result.counts or {}
+        total = sum(counts.values()) or 1
+        print()
+        for outcome, count in sorted(counts.items(), key=lambda kv: -kv[1]):
+            share = 100 * count / total
+            print(f"  {outcome}  {count:6}  {share:5.1f}%  {'█' * round(share / 2)}")
+        return 0
+
+
+if __name__ == "__main__":
+    raise SystemExit(main())

qubitra_sdk-0.1.0/examples/submit_ionq_circuit.py

@@ -0,0 +1,77 @@
+"""Live smoke: dispatch an IonQ circuit and read its measured counts.
+
+The same Bell pair as ``submit_bell_pair.py``, expressed as an IonQ circuit document rather
+than as OpenQASM. Backends differ in what they accept — ``client.backends.list()`` reports each
+one's ``supported_formats`` — and several providers accept the IonQ circuit schema, so this is
+the path for a backend that does not take QASM.
+
+    QUBITRA_API_KEY=qpk_... uv run pkg/niobium/examples/submit_ionq_circuit.py <backend-id>
+
+Against a local stack (``mise run dev:qplat``), add ``QUBITRA_API_URL=http://localhost:8080``.
+
+The circuit is JSON, but it is still passed as a string: ``circuit`` is text whatever the
+format, and the platform parses the document at the vendor edge.
+"""
+
+from __future__ import annotations
+
+import json
+import sys
+
+from qubitra import CircuitFormat, QubitraClient
+
+# A Bell pair as an IonQ circuit: `h` on qubit 0, then `x` on qubit 1 controlled by qubit 0.
+# `gateset: "qis"` is the standard gate-level set, as against IonQ's native-gate mode.
+BELL = {
+    "gateset": "qis",
+    "qubits": 2,
+    "circuit": [
+        {"gate": "h", "targets": [0]},
+        {"gate": "x", "targets": [1], "controls": [0]},
+    ],
+}
+
+SHOTS = 1024
+
+
+def main() -> int:
+    if len(sys.argv) < 2:
+        print(
+            "usage: submit_ionq_circuit.py <backend-id>\n"
+            "  pick one whose supported_formats includes IONQ_CIRCUIT",
+            file=sys.stderr,
+        )
+        return 2
+    backend_id = sys.argv[1]
+
+    with QubitraClient() as client:
+        job = client.jobs.submit(
+            backend_id=backend_id,
+            circuit=json.dumps(BELL),
+            circuit_format=CircuitFormat.IONQ_CIRCUIT,
+            shots=SHOTS,
+            name="bell-pair (IonQ)",
+        )
+        print(f"submitted {job.id} to {backend_id} — {job.status}")
+
+        # A live queue can outlast a short wait, and the platform keeps polling either way —
+        # so this waits longer than the SDK's default rather than reporting a timeout as
+        # though the job had failed.
+        job = client.jobs.wait(job.id, timeout=900, poll_interval=5)
+        print(f"finished  {job.id} — {job.status}")
+
+        if job.status.value != "COMPLETED":
+            print(f"job did not complete: {job.error or '(no error recorded)'}", file=sys.stderr)
+            return 1
+
+        counts = client.jobs.result(job.id).counts or {}
+        total = sum(counts.values()) or 1
+        print()
+        for outcome, count in sorted(counts.items(), key=lambda kv: -kv[1]):
+            share = 100 * count / total
+            print(f"  {outcome}  {count:6}  {share:5.1f}%  {'█' * round(share / 2)}")
+        return 0
+
+
+if __name__ == "__main__":
+    raise SystemExit(main())