Three pipes, no dumping ground.
Every message lands with the team that can act on it, and each route states how fast you hear back. Most questions are answered in the docs; everything else is below.
Dedicated nodes, custom SLAs, contracts
Dedicated or co-located fleet, private throughput, custom datasets, procurement and security review. The first call is technical scoping with an engineer, not a sales pitch.
Response within one business day
Keys, quotas, connections, billing
Stream disconnects, rate limits, key management, invoices. Include your key prefix (never the full key) and the endpoint you're hitting. It saves a round trip.
Response within one business day · priority on Pro and Enterprise
Custom datasets, research, integrations
Custom backfills and dataset builds, research collaborations, platform integrations, or reselling the feeds inside your product. Bring a schema sketch if you have one.
Response within two business days
The short answers.
The four questions inbound mail asks most. The full set lives on the product and pricing pages.
Request an API key for self-serve tiers, or contact us for Enterprise: dedicated nodes, custom SLAs, and custom datasets.
Get an API key, point a gRPC client at stream.hyperliquidrpc.com:443, and pass your key in the x-api-key metadata. Reflection is enabled, so grpcurl and auto-generated stubs work out of the box.
Streams are sub-second. We run a self-operated Hyperliquid node fleet with automated failover and redundancy.
Yes. The trust center summarizes our security posture and data handling; SLA terms are published at /sla; review documents are available under NDA through the trust-center request form. Enterprise contracts support custom terms and DPAs.
No question, just want to try it?
Pro is one key against the real feeds, live in minutes, month-to-month billing. No call required.