Developers. The wire in the wire.

Entanglement API v3. OpenQASM 3 in, Bell pairs out.

Ship Bell pairs from your laptop.

The developer kit gets you onto the backbone before hardware exists on your desk. Simulator first, sandbox keys second, pilot unit third. The API contract does not change between the three.

API sheet

The whole surface,
one page.

A handful of endpoints. No SDK zoo, no client generator, no version roulette. The protocol document is 14 pages and we keep it that way.

Entanglement API v3, public contract
Parameter Value Note
Endpointqntp://api.qunetlabs.com/v3TLS with post quantum handshake
PrimitivesH, CNOT, CZ, T, SWAPPlus measure and reset
Pair requestPOST /pairsReturns pair id and fidelity
Circuit submitPOST /circuitsOpenQASM 3 accepted
AuthBearer keySandbox and production key spaces
Printout 04.2. Values from the Q1 pilot device, batch P-02.
Program tiers Start free. Upgrade when the simulator feels small.
Console Free
  • Simulator with 30 qubits
  • 10 minutes monthly QPU time
  • QNTP protocol reference
  • Community forum
Enroll
Lab 240 USD per month
  • 8 hours monthly QPU time
  • Entanglement API sandbox keys
  • Two cooling tanks included
  • Office hours with the firmware team
Enroll
Foundry 1,900 USD per month
  • Dedicated calibration window weekly
  • Unlimited metro entanglement peering
  • Pre release hardware samples
  • Named support engineer
Enroll
Bench photo The interface you are coding against
A black and white architectural structure built from triangles and repeating patterns
Fig. 31. Entanglement interface truss, metro point of presence two.

Join the developer program.

Free tier opens today. Lab tier includes two tanks monthly once your unit ships.

Reserve your unit