QDMI is a C interface for managing quantum devices. It connects an application's Client Interface calls to device implementations through a driver. Its session, query, and job interfaces cover configuration, capability discovery, submission, and result retrieval. See the architecture.
QDMI grew out of Munich Quantum Valley (MQV) and is used in the Munich Quantum Software Stack (MQSS). It also contributes to reference-architecture and integration work across Germany, Europe, and the international openQSE community. See Ecosystem and Community for deployments, implementations, and opportunities to participate.
QDMI was created jointly by TUM's Chairs of Design Automation and Computer Architecture and Parallel Systems and the Leibniz Supercomputing Centre. It is maintained by MQV gGmbH and MQSC, with contributions from the wider community. Participation is open to organizations and individuals worldwide.
The interface package supplies headers and CMake helpers. Executing calls requires a compatible driver and device implementation. For an implementation smoke test with synthetic results, use the bundled mock device. For execution APIs and a local simulator, see MQT Core.
The C interface lets native HPC software, drivers, and device libraries share a common ABI. Opaque handles keep implementation details behind that boundary. Other languages can use it through bindings, including the C++ and Python wrappers supplied by MQT Core.
Yes. QDMI uses a C ABI that other languages can call. MQT Core provides C++ and Python wrappers, plus Qiskit and PennyLane adapters. These wrappers and adapters are implementation facilities, rather than part of the QDMI C specification.
No. Query the selected device's capabilities, including accepted program formats, and check the return codes of optional queries and operations. Available results depend on the program, device, and execution mode. For example, statevectors are simulator capabilities, rather than hardware measurement results.
Use the headers and documentation corresponding to your driver and device libraries. QDMI minor releases can introduce breaking changes. The Client Interface provides an ABI query; loaders compare major and minor versions and ignore patch differences. See the CMake installation guide, architecture, and upgrade guide.
Use Support for questions and bug reports and Contributing for contributions. See the @ref ecosystem-publications "publications" for citation information and the license for reuse terms.