Quantum Origin is a RESTful API-based service. Four different end-points are available to access the service, keygen, randomness, onboard, usage. The specified endpoints enable the user to tap into a distinct functionality.

Quantum Origin derived encryption keys and randomness are generated on the cloud service’s servers and transferred encrypted to authorized consumers on-demand. Unlike many platforms, Quantum Origin provides requested material immediately, in the same connection as the request is made. It does not queue commands for later execution.

Prior to making requests, users need to be onboarded on to the Quantum Origin server. A shared secret and an authentication data are provided at the end of onboarding process. The returned response is encrypted and can only be decrypted with the aforementioned shared secret. A brief description of each functionality is described below.


The Quantum Origin API can provide quantum-enhanced randomness, which can be directly imported into a designated endpoint such as a hardware security module (HSM).

Key Generation

Using the API, users can generate both classical and post-quantum keys based on verifiable quantum randomness.This feature is described in Key Generation section.

User-initiated Onboarding

To make encryption key or randomness requests, users must be onboarded onto the service. Onboarding is a two-stage process. Stage 1 involves the user receiving a subscription-id and onboarding auth from Quantinuum. These two credentials will be used during stage 2, where the user can make use of the onboard endpoint to self-onboard. The second stage of the process can be repeated multiple times to get a client_id and matching shared_secret for each subsequent onboarding. Stage 1 is executed completely by Quantinuum.

The prior method of Quantinuum-led Onboarding using client certificates remains available for relevant parties. Please connect with your designated technical contant or contact us at for assistance associated with classic onboarding.

API Usage

This endpoint allows a user to check the number of keys or quantity of randomness generated while using the service.