Quantum Machines
Quantum Machines is a Tel Aviv, Israel-based quantum control company that builds the Quantum Orchestration Platform (QOP) — a unified hardware and software stack for controlling quantum processors at the pulse level. Its hardware portfolio centers on the OPX+ and OPX1000 controllers, which are built around a custom Pulse Processing Unit (PPU) architecture that executes classical control and real-time feedback alongside arbitrary waveform generation, with sub-microsecond classical-quantum round trips and 160 ns active reset latency. The platform is programmed in QUA, the company's domain-specific pulse-level language, exposed to developers through the qm-qua Python SDK and an extensive open-source ecosystem under the qua-platform GitHub organization (QUAlibrate, QUAM, qua-libs, py-qua-tools, qua-dashboards). Quantum Machines also ships peripheral hardware including the Octave up/down converter (to 18 GHz), QDAC-II ultra-low-noise DACs, QSwitch, QBox, and the QCage/QBoard/QFilter cryogenic line. The platform is qubit-modality agnostic, supporting superconducting, semiconductor spin, trapped-ion, neutral-atom, and color-center systems, and is used by university labs (MIT, Caltech, Harvard, Princeton, Weizmann) and quantum startups (Alice & Bob, Diraq, EeroQ). Quantum Machines has partnered with NVIDIA on the DGX Quantum hybrid quantum-classical compute platform and acquired the Delft-based QHarbor Bioscience team as a European R&D hub. Quantum Machines does not currently publish a public REST API, OpenAPI specification, or self-service developer signup; the QOP control surface is reached exclusively via the qm-qua Python SDK against an OPX/OPX1000 controller (hardware or qm-saas cloud simulator).
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Quantum Machines the way a machine reads it — 14 machine-readable artifacts across 13 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Quantum Machines scores 12.5/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Quantum Machines
Each block below is one kind of artifact we hold for Quantum Machines. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 13
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
qm-qua Python SDK
Official Python SDK for the QUA pulse-level programming language. Provides the QuantumMachinesManager client, qua DSL (program, declare, play, measure, wait, save, stream_proces...
qm-saas Cloud Simulator
Cloud-hosted OPX simulator distributed as the qm-saas Python package. Allows developers to author and validate QUA programs without physical OPX hardware; mirrors the qm-qua cli...
QUA Libraries (qua-libs)
High-level libraries and reference experiments built over QUA. Covers superconducting, semiconductor, NV, and other qubit modalities with ready-to-run calibration scripts and ex...
py-qua-tools
Toolbox of Python utilities for QUA experiments — analog filters, mixer calibration, plotting, calibration helpers, and integrations with common lab instruments. Distributed on ...
Quantum Abstract Machine (QUAM)
Framework for abstracting and managing quantum programming environments on top of QUA. Provides an object model for qubits, resonators, pulses, and configuration; serializes to ...
QUAM Builder
Builder tool for generating QUAM state from hardware wiring and configuration inputs.
QUAlibrate
User-programmable calibration software for large-scale quantum computers. Orchestrates calibration graphs (calibration nodes and their dependencies) on top of QUA/QUAM.
QUAlibrate App
TypeScript front-end web application for running and visualizing QUAlibrate calibration graphs.
QUAlibrate Core
Core Python library that defines the calibration node and graph abstractions used by QUAlibrate.
QUAlibrate Runner
Execution service that runs QUAlibrate calibration nodes and graphs.
QUAlibrate Config
Configuration management package for QUAlibrate deployments.
QUAlibration Libraries
Collection of calibration graph building blocks (qubit spectroscopy, Rabi, T1, T2, readout calibration, etc.) for QUAlibrate.
QUA Dashboards
Interactive dashboards (Plotly Dash / Streamlit) for visualizing QUA experiment results and live data streams.
Scroll within the panel for all 13 ·
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Quantum Machines — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Company 7
The organization behind the API
Scroll within the panel for all 7 ·
Other 9
Properties that don't map to a standard resource type
Scroll within the panel for all 9 ·
← All providers · Data indexed from github.com/api-evangelist/quantum-machines · machine-readable index on apis.io