Secure randomness API
What to require from a secure random number API
Learn how to evaluate a secure random number API for random bytes, bounded integers, REST and gRPC integration, receipts, and audit evidence.
Read guideTechnical resources
Build random workflows that remain reviewable
These guides explain how to choose an API interface, interpret statistical validation, design evidence retention, and prepare gaming or drawing workflows for technical review.
Updated August 24, 2026
Evidence architecture
How randomness receipts become reviewable evidence
Understand how randomness receipts, hash chains, and Merkle proofs preserve request history and support independent review without exposing raw secrets.
Read guideAPI integration
REST or gRPC: choose for the workload, not the benchmark headline
Compare REST and gRPC for random bytes, numbers, shuffling, and sampling, including connection behavior, latency measurement, retries, and operations.
Read guideRandomness validation
How to read statistical test results for a random generator
Learn how to interpret PractRand, ENT, Dieharder, NIST STS, and TestU01 BigCrush results and why statistical testing does not replace security review.
Read guideGaming and drawing controls
Prepare random outcomes for review before a dispute occurs
A technical checklist for gaming, probability items, lotteries, and drawings that need secure random generation, evidence retention, and external review.
Read guideReview a real integration with Rantropy
Share the operations you need, expected traffic, evidence policy, and regulatory context. We will identify the API and review controls that fit the workload.