Aegis Optikon — TRNG API Documentation

Base URL

Authentication

All API requests require your API key:

x-api-key: YOUR_API_KEY

Find it on your Dashboard.

Available Endpoints

• GET /random — Retrieve true random bytes
• GET /entropy — Inspect entropy pool status
• GET /proof — Verify lineage of an output
• GET /health — Service uptime & status
• POST /comment — Submit documentation feedback

GET /random

GET /random?bytes=32

Returns physically sourced entropy mixed through a deterministic cryptographic pipeline.

• bytes — number of bytes (tier‑dependent)

curl -H "x-api-key: YOUR_API_KEY" \
"https://aegisoptikon.com/random?bytes=64"

{
  "entropy": "4f9c2a1e...",
  "id": "b2f1c9e8",
  "remainingCredits": 998736
}

GET /entropy

GET /entropy

{
  "poolSize": 32768,
  "sources": 14,
  "lastUpdate": 1734567890
}

GET /proof

GET /proof?id=OUTPUT_ID

{
  "output": "4f9c2a1e...",
  "sourceHash": "a7b91c...",
  "mixHash": "f0e3d9...",
  "timestamp": 1734567890
}

GET /health

{
  "status": "ok",
  "uptime": 123456,
  "entropySources": 14
}

Tier Capabilities

Per‑Request tier always returns 32 bytes.

SDK Examples

Node.js

const apiKey = "YOUR_API_KEY";
const res = await fetch("https://aegisoptikon.com/random?bytes=32", {
  headers: { "x-api-key": apiKey }
});
console.log(await res.json());

Python

import requests
res = requests.get(
  "https://aegisoptikon.com/random?bytes=32",
  headers={"x-api-key": "YOUR_API_KEY"}
)
print(res.json())

Go

req, _ := http.NewRequest("GET",
  "https://aegisoptikon.com/random?bytes=32", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
body, _ := ioutil.ReadAll(res.Body)
fmt.Println(string(body))

Rust

let res = reqwest::Client::new()
  .get("https://aegisoptikon.com/random?bytes=32")
  .header("x-api-key", "YOUR_API_KEY")
  .send().await?.text().await?;
println!("{}", res);

PHP

$opts = ["http" => ["header" => "x-api-key: YOUR_API_KEY"]];
echo file_get_contents(
  "https://aegisoptikon.com/random?bytes=32",
  false, stream_context_create($opts)
);

Security Model

• Physically sourced entropy from distributed sensors
• Cryptographic mixing using SHA‑256 hash chains
• Deterministic reproducibility for verification
• Tamper‑evident outputs via public proofs
• HTTPS‑only transport
• Per‑user API key isolation

Mixing Pipeline

raw_entropy → SHA256(sourceHash)
           → SHA256(poolHash + timestamp)

Threat Model

• Compromised source → mitigated by multi‑source mixing
• Replay attacks → mitigated by timestamped proofs
• Transport interception → mitigated by HTTPS
• Server compromise → mitigated by public verification

Verifiable Randomness

1. Public Entropy Pool

GET /entropy

2. Output Lineage

GET /proof?id=OUTPUT_ID

3. Recomputable Hash Chain

mixHash = SHA256(sourceHash + timestamp)

4. Tamper‑Evident Guarantees

• Server cannot alter outputs without breaking proofs
• Entropy manipulation becomes detectable
• Timestamps prevent replay

Compliance & Audit

Audit Features

• Per‑output cryptographic proofs
• Public entropy transparency
• Deterministic mixing algorithm
• Timestamped lineage

Use Cases

• Online casinos
• Lotteries
• Financial simulations
• Security‑critical randomness

Compliance Roadmap

• ISO/IEC 18031 alignment
• NIST SP 800‑90B entropy validation
• GLI‑19 casino RNG certification
• Open‑source proof verifier

Leave a Comment

Your feedback helps improve the API documentation.