Live API playground

Call the public gateway directly from your browser using the demo API key, or point the playground at your own self-hosted instance.

Play with the gateway

The demo key is rate-limited and intended for integration tests, CI pipelines and evaluation.

API base URL

Header

X-API-Key: demo

API key

n (32-bit words)

Format

Status: idle

{ }

Quick curl snippets

You can run these directly from your terminal.

# health
curl -s "https://api.re4ctor.com/v1/health"

# random bytes (hex)
curl -s -H "X-API-Key: demo" \
  "https://api.re4ctor.com/v1/random?n=16&fmt=hex"

# dual-signed VRF JSON
curl -s -H "X-API-Key: demo" \
  "https://api.re4ctor.com/v1/vrf?sig=ecdsa" | jq .

Runtime snapshot

Live view into your Re4ctoR SaaS gateway (demo tier).

FIPS 204-ready
PQ combo: ECDSA + ML-DSA-65 (roadmap).

Latency (dev)
Core < 1 ms → Gateway → Core single hop.

Randomness
NIST SP 800-22, Dieharder, PractRand and BigCrush test suites passed on multi-GB samples.

Endpoints

GET /v1/health

Lightweight health check of the gateway.

GET /v1/random

High-entropy random bytes proxied from RE4CTOR Core RNG.

Query	Type	Description
`n`	int	Number of 32-bit words to return (e.g. 4, 8, 32).
`fmt`	string	`hex` (default) or `raw`.

GET /v1/vrf

Dual-signed VRF-style randomness, proxied to the VRF node (internally calling its /random_dual). Response is JSON with ECDSA(secp256k1) + ML-DSA-65 signatures.

Query	Type	Description
`sig`	string	Signature scheme. For now: `ecdsa` (dual ECDSA + ML-DSA-65).

POST /v1/verify

Helper endpoint to verify an Ethereum-style ECDSA signature produced by the VRF output (msg_hash / v / r / s).

JSON body:

{
  "msg_hash": "0x...",
  "r": "0x...",
  "s": "0x...",
  "v": 27,
  "expected_signer": "0x1C901e3bd9..."
}

Note: Browser calls from re4ctor.com to api.re4ctor.com require CORS to be enabled on the gateway. The demo gateway is CORS-enabled for https://re4ctor.com. If your browser or network still blocks the call, you can always try the curl examples above or the Python SDK.