Quantum randomness.
Provably real. API simple.

True random numbers from real quantum hardware — not a formula that just looks random. Every response ships with a signed certificate you can independently verify.

curl -X POST https://qbitseed-api-production.up.railway.app/random \
  -H "Authorization: Bearer $QBITSEED_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"bits": 256}'
Live entropy reservoir: nominal · Heron QPU execution thread active

Why quantum, not pseudo-random

Every other RNG API on the market — including the “quantum” ones — is a formula under the hood. QbitSeed sources entropy from real IBM Quantum hardware instead.

Classical RNGs are predictable in principle

Most "random" numbers come from a deterministic formula seeded from a starting value. It looks random, but it's reconstructable if that seed is ever exposed or guessed — and quantum computing is expected to make that easier, not harder.

Regulation is catching up to the gap

Post-Quantum Cryptography mandates, NIST SP 800-90A/B, and ETSI's quantum-safe standards are pushing buyers toward entropy sources they can prove, not just trust.

Some industries can't get by on “good enough”

iGaming needs certified, auditable fairness (GLI-19). Crypto wallets need keys an attacker can't reconstruct. Encryption needs entropy that was never derived from anything predictable in the first place.

How it works

Step 1

You call the API

POST /random with how many bits you need. One request, one response — no job polling.

Step 2

Real quantum hardware runs

A circuit executes continuously on IBM Quantum's Heron QPU to keep the entropy reservoir topped up. If it ever runs dry, a monitored failover layer hands off to an OS-backed CSPRNG — never silently, and never mislabeled: the response's source field always names the block that actually filled it.

Step 3

The response is signed

Every batch gets an Ed25519-signed certificate recording exactly where its entropy came from, tied to a real job ID.

Step 4

You verify it, independently

GET /certificates/{id}/verify checks the signature yourself — you don't have to take our word for the source.

Built for

Select a vertical to see how QbitSeed's entropy and provenance model fits.

Blockchain & crypto wallets

Quantum-secure key generation for wallets and DeFi protocols. Seed material that isn't derived from a formula an attacker could eventually model.

Key-generation grade entropyEd25519-signed provenance

One request. A real answer.

source tells you exactly where your randomness came from — every time, including the honest classical failover if the entropy pool is momentarily empty.

Request

curl -X POST https://qbitseed-api-production.up.railway.app/random \
  -H "Authorization: Bearer <your-api-key>" \
  -H "Content-Type: application/json" \
  -d '{"bits": 256}'

Response

{
  "request_id": "3f9a1c2e-7b4d-4e8a-9c1f-2d6e8a4b7c3f",
  "bits": 256,
  "data_base64": "k3F9j2QwX7...",
  "source": "ibm_quantum",
  "certificate_id": "a1b2c3d4-5e6f-4a7b-8c9d-0e1f2a3b4c5d",
  "certificate_url": "/certificates/a1b2c3d4-5e6f-4a7b-8c9d-0e1f2a3b4c5d",
  "issued_at": "2026-09-01T14:22:03Z"
}

Pricing

Start free, no card required. Every paid tier meters overage instead of hard-rejecting requests once you're past quota.

Free

$0

150 requests/month

No card required

Developer

$58/mo

10,000 requests/month

$0.0116/request over quota

Pro

$368/mo

100,000 requests/month

$0.0040/request over quota

Enterprise

$998/mo

Custom quota

Negotiated per contract

Gaming

$7,353/mo

2,000,000 requests/month + compliance package

$0.0040/request over quota

  • ›Priority QPU job scheduling
  • ›GLI-19-ready compliance package: signed certificate export per batch
  • ›Metered overage, never a hard cutoff mid-traffic

Randomness you don't have to trust — just verify.

Free tier, no card required. Paid tiers when you need more.