Authentication

API Key Authentication

All Aleatoric Data feeds require an API key for access. Keys are provisioned through the dashboard and managed centrally by the credential management service.

Passing Your Key

Protocol	Method
JSON-RPC	x-api-key HTTP header
gRPC	x-api-key metadata or Authorization: Bearer metadata
Unified Stream (SSE)	x-api-key HTTP header or Authorization: Bearer header
Disk-Sync WebSocket	x-api-key header or ?api_key= query parameter

Example Headers

# HTTP header (most common)
curl -H "x-api-key: ak_live_c51nSdWI..." https://rpc.aleatoric.systems

# Bearer token (gRPC metadata)
metadata = [("authorization", "Bearer ak_live_c51nSdWI...")]

Key Scopes

Keys can be scoped by service and region:

• chain:hyperliquid — Access to Hyperliquid feeds
• region:us / region:jp — Region-specific access
• stream:read — Unified Stream access
• status:read / status:admin — Status API access

Rate Limiting

Rate limits are enforced per API key at the Nginx gateway:

Tier	Requests/min	Requests/sec
Basic	100	2
Pro	120,000	200
Quant	Unlimited	Unlimited

When rate limited, you’ll receive a 429 Too Many Requests response. See Rate Limits for details.

Key Rotation

Keys can be rotated from the dashboard without downtime. Create a new key, update your clients, then revoke the old key.