/info endpoint, its HyperCore WebSocket, and a HyperEVM node yourself — with automatic provider failover, unified authentication, and no public-API per-IP caps to work around.
Every request is authenticated with a project API key. Create your project and
grab your key from the Uniblock dashboard.
New to Hyperliquid’s architecture? Start with
HyperCore vs. HyperEVM.
What you can build
Hyperliquid Info API
A drop-in replacement for Hyperliquid’s public
/info REST API. Same request and response shapes, routed through Uniblock’s provider waterfall — no per-IP request-weight cap, automatic failover.Hyperliquid WebSockets
Real-time HyperCore order book and account streams —
l2Book, l2BookDiff, l4Book, fills, and liquidations — over one connection, with no per-IP subscription cap.Hyperliquid EVM
Standard JSON-RPC access to HyperEVM (chain
999, testnet 998) — read state, send transactions, and call contracts with familiar EVM tooling.Why route Hyperliquid through Uniblock
- No per-IP caps. The public
/infoAPI caps you at a request-weight budget per IP, and the public WebSocket caps you at 1000 subscriptions per IP. Uniblock lifts both — plan-level rate limits still apply (a429on burst; details). - One key, one bill. Info API, WebSockets, and HyperEVM share the same project API key and are metered in compute units.
- Automatic failover. Requests flow through the unified provider waterfall (Alchemy, Dwellir, Chainstack, GoldRush/Covalent), so a single provider outage doesn’t take you down.
- Drop-in migration. Request and response shapes match Hyperliquid’s own contracts, so migrating usually means changing one URL and adding a header.
The two halves of Hyperliquid
Hyperliquid is two components with different jobs, and which offering you use depends on which half you need:
See HyperCore vs. HyperEVM for the full breakdown.
Get started
Hyperliquid Quickstart
Three ~5-minute paths: call the Info API, connect a WebSocket, and query HyperEVM over JSON-RPC.