Light Rider documentation

Guides for requesting attested quantum entropy, verifying signed receipts, operating the source fleet, and building on the platform. Every response is signed; raw entropy is never stored; unavailable quality tiers fail closed.

receipts: Ed25519 / ML-DSA-65— sources registeredegress: /v1/* · admin: /api/v1/*

Get started

What the platform is and how to get your first attested bytes.

What is Light Rider EMS?

The Entropy Management System: aggregated quantum randomness, a streaming verification pipeline, and attested delivery.

Quickstart

Install an SDK and request your first receipt-attested entropy in a few minutes.

Request entropy

Policies, multi-source extraction, and continuous streaming.

Policies

Route each request to a quality tier — Bell-test verified, vetted QRNG, or lowest latency.

Multi-source extraction

Combine independent sources so output stays uniform even if all but one is compromised.

Streaming entropy

Continuous receipt-attested delivery over WebSocket for dashboards and high-frequency consumers.

Verify & audit

Prove where every byte came from.

Receipts & verification

Every response is signed — Ed25519 or post-quantum ML-DSA-65. Verify attestations independently.

Operate

Run the source fleet: toggles, budgets, and failure handling.

Sources & collectors

The source catalog, enable/disable semantics, budget caps for metered lanes, and auto-disable.

Build

Applications on top of attested entropy.

Synthetic data

Generate synthetic datasets whose every random draw is quantum, with a signed provenance certificate.

Reference

The complete API surface.

API reference

Every public endpoint: entropy egress (/v1/*), the randomness beacon, and the admin registry (/api/v1/*).