Endpoint Reference

Endpoint Matrix

Aleatoric now publishes both the US and JP production edges. JP access is available to eligible customers using the regional endpoints below.

US (East US 2) — Virginia

Protocol	Endpoint	Port	Transport
JSON-RPC	`https://rpc.aleatoric.systems`	443	HTTPS
gRPC	`hl.grpc.aleatoric.systems`	443	HTTP/2 + TLS
Unified Stream	`https://unified.grpc.aleatoric.systems`	443	SSE over HTTPS
Disk-Sync WebSocket	`wss://disk.grpc.aleatoric.systems`	443	WSS

Japan East — Tokyo

Protocol	Endpoint	Port	Transport
JSON-RPC	`https://rpc-jp.aleatoric.systems`	443	HTTPS
gRPC	`hl-jp.grpc.aleatoric.systems`	443	HTTP/2 + TLS
Unified Stream	`https://unified-jp.grpc.aleatoric.systems`	443	SSE over HTTPS
Disk-Sync WebSocket	`wss://disk-jp.grpc.aleatoric.systems`	443	WSS

JP edge status: JP regional endpoints are available for customer use when the account plan includes Japan East access.

Engine API (Global)

Service	Endpoint	Description
API Gateway	`https://mcp.aleatoric.systems`	Authentication, billing, dashboard proxy
Alpha Dashboard Proxy	`https://mcp.aleatoric.systems/api/v1/unified/*`	Session-authenticated proxy to unified stream

Important: The Unified Stream endpoints listed above (unified.grpc.aleatoric.systems) are for direct SDK/bot access using API keys provisioned via the credential manager. Dashboard clients must connect through the engine proxy at mcp.aleatoric.systems/api/v1/unified/*, which validates session tokens and forwards requests to the hypernode with a service-level key. Connecting directly from the browser will result in a 401 auth error because the hypernode does not accept session tokens.

Health Endpoints

Health checks do not require authentication and return HTTP 200 when the service is operational.

Region	URL	Method
US	`https://unified.grpc.aleatoric.systems/healthz`	GET
JP	`https://unified-jp.grpc.aleatoric.systems/healthz`	GET

# Quick health check
curl -s https://unified.grpc.aleatoric.systems/healthz

{"status": "ok"}

Protocol Quick Reference

Protocol	Auth Method	Tier	Latency Target
JSON-RPC	`x-api-key` header	All tiers	p50 < 50 ms
gRPC	`x-api-key` metadata	Pro+	p50 < 10 ms
Unified Stream (SSE)	`x-api-key` or `Bearer` header	Pro+	p50 < 500 $\mu$ s
Disk-Sync WebSocket	`x-api-key` header or `?api_key=` query	Quant only	Wire-speed

DNS

US and JP production endpoints are published as separate regional targets. Choose the endpoint that matches your entitled region and operating requirements.

TLS

Property	Value
Minimum version	TLS 1.2
Cipher suites	ECDHE+AESGCM, ECDHE+CHACHA20POLY1305
gRPC transport	HTTP/2 with ALPN (`h2`)
Certificate management	Automated (platform-managed)
Certificate management	Managed by Aleatoric

Connection Examples

JSON-RPC

curl -X POST https://rpc.aleatoric.systems \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

gRPC (grpcurl)

grpcurl -d '{"coin":"BTC"}' \
  -H "x-api-key: YOUR_API_KEY" \
  hl.grpc.aleatoric.systems:443 \
  price.PriceService/GetMidPrice

Unified Stream (SSE)

curl -N -H "x-api-key: YOUR_API_KEY" \
  "https://unified.grpc.aleatoric.systems/api/v1/unified/stream"

Disk-Sync WebSocket

const ws = new WebSocket('wss://disk.grpc.aleatoric.systems', {
  headers: { 'x-api-key': 'YOUR_API_KEY' }
});

Next Steps

Regions Overview — Region selection guidance and failover strategy
Authentication — API key authentication details per protocol
Rate Limits — Per-tier, per-region enforcement policies