One key, every provider
999
HyperEVM mainnet · chainId 999
Routed across Alchemy · GoldRush · Dwellir · Chainstack
Info types
RPC methods
- +100 more · EVM · Debug · Trace · Erigon
POST /uni/v1/json-rpc?chainId=999 X-API-Key: YOUR_UNIBLOCK_API_KEY { "jsonrpc": "2.0", "id": 1, "method": "eth_blockNumber", "params": [] }
{ "jsonrpc": "2.0", "id": 1, "result": "0x24c4733" }
APIs that power Hyperliquid products, without running the infrastructure.
Blocks & transactions
Read HyperEVM blocks and transactions directly. No node to run, sync, or babysit.
Tokens & transfers
Balances, transfers, and metadata for any HyperEVM token, normalized and ready to render.
Trading & market data
HyperCore positions, orders, fills, funding, and order book depth for trading interfaces and bots.
HyperEVM JSON-RPC
Standard JSON-RPC over one endpoint. Blocks, logs, calls, and state with no node operations.
Smart provider routing
Every request is routed to the best available provider automatically, behind one API key.
Failover & uptime
Automatic retries and re-routing keep the endpoint responsive when a provider degrades.
Hyperliquid is two halves. You need both.
HyperCore runs the order book. HyperEVM runs the contracts. Uniblock covers both behind one key, which matters most for the half you cannot run a node for.
What it is
The native trading engine: order book, perpetuals, and spot.
An EVM-compatible chain for standard Solidity contracts.
How you reach it
Info API over REST, and HyperCore WebSockets for live data.
HyperEVM JSON-RPC on chain 999, testnet 998.
Node access
Controlled by Hyperliquid. You cannot run one yourself.
Permissionless. You can run your own node if you want to.
What you build on it
Trading UIs, copy-trade bots, portfolio and PnL tracking.
Contracts, on-chain dashboards, indexers, and wallet flows.
Info API
A drop-in path to Hyperliquid’s /info REST contract. Request and response shapes match. Requests route through the provider waterfall with automatic failover.
HyperCore WebSockets
Real-time order book and account streams over one connection. L2 snapshots, per-block diffs, order-level L4 depth, fills, and liquidations.
HyperEVM JSON-RPC
Standard JSON-RPC access to HyperEVM, chain 999 and testnet 998. State reads, transactions, and contract calls run with existing EVM tooling.
Every HyperCore read, one POST body.
Account state
12 types
Perp and spot account summaries, margin usage, abstraction mode, sub-accounts, and agent permissions.
clearinghouseState · spotClearinghouseState · webData2 · activeAssetData · userFees
Orders & fills
12 types
Live and historical order state, fill history, TWAP slices, and builder-attributed fills.
openOrders · frontendOpenOrders · historicalOrders · userFillsByTime · userTwapSliceFills
Markets & metadata
15 types
The asset universe, order book snapshots, candles, mids, funding history, and margin tables.
l2Book · candleSnapshot · allMids · meta · fundingHistory
Vaults & staking
8 types
Vault summaries and equity, leader performance, delegations, and validator votes.
vaultSummaries · userVaultEquities · leadingVaults · delegatorSummary · validatorL1Votes
Builder & deploy
7 types
Builder-deployed perp DEXs, their limits and status, and the deploy auction state.
perpDexs · perpDexLimits · maxBuilderFee · spotDeployState
Lending & outcomes
5 types
Borrow-lend reserve and user state, plus prediction-market outcome metadata.
borrowLendUserState · allBorrowLendReserveStates · outcomeMeta · settledOutcome
Uniblock synthetic types
Composed on our side · not in the public contract
portfolioState
One normalized account view composed across perpetuals, spot balances, and user abstraction. No client-side stitching.
batchClearinghouseStates
Perp clearinghouse state for up to 50 users in a single request instead of 50 round trips.
batchPortfolioStates
Full portfolio state for up to 50 users at once. Built for leaderboards and copy-trade fan-out.
Order book and account events, down to the order.
Order book
Subscribe per coin, or omit the filter to stream every asset.
l2Book
0.5 credits / min
Aggregated L2 snapshots and updates: bids and asks by significant figures.
subscribe · { type: l2Book, coin: HYPE }
l2BookDiff
0.1 credits / min
GoldRush-native. A snapshot per coin, then per-block updates carrying only the levels that changed.
subscribe · { type: l2BookDiff, coin: HYPE }
l4Book
2 credits / min
GoldRush-native order-level book with user, order ID, client order ID, time-in-force, and trigger metadata.
subscribe · { type: l4Book, coin: BTC }
Wallet & account activity
Event streams for monitored addresses and for the exchange as a whole.
userFills
1 credit / min
Live trade fills for the wallets you specify, batched per block.
subscribe · { type: userFills, user: 0x… }
orderUpdates
1 credit / min
Order lifecycle events: placements, fills, cancels, and rejections.
subscribe · { type: orderUpdates, user: 0x… }
allFills
1 credit / min
The complete global fill stream, with optional single-market filtering.
subscribe · { type: allFills }
liquidationFills
1 credit / min
GoldRush-native global liquidation stream for risk dashboards and liquidation bots.
subscribe · { type: liquidationFills }
builderFills
1 credit / min
Attributed fills for builder addresses, carrying builder-fee data.
subscribe · { type: builderFills }
userNonFundingLedgerUpdates
1 credit / min
Non-funding ledger events such as deposits and withdrawals.
subscribe · { type: userNonFundingLedgerUpdates }
Focus Alchemy · Primary RPC + Enhanced APIs · Operational
More than a proxy for Hyperliquid.
No per-IP caps
The public /info API meters a request-weight budget per IP, and the public WebSocket caps you at 1,000 subscriptions per IP. Both limits are removed. Plan-level rate limits still apply.
Routed through leading providers
Hyperliquid traffic routes across Alchemy, GoldRush/Covalent, Dwellir, and Chainstack. A single provider outage does not take the connection down.
One bill
Info API, WebSockets, and HyperEVM meter to the same project. One account, one invoice.
Migration
Migration is a URL change and a header. Existing Hyperliquid integrations keep their request and response shapes.
Every HyperEVM method group, one endpoint.
EVM
60+ methods
Debug
12 methods
Trace
8 methods
Erigon
9 methods
Otterscan
11 methods
Migration is a URL and a header.
Before · public API
per-IP weight cap
POST https://api.hyperliquid.xyz/info
Content-Type: application/json
{ type: clearinghouseState, user: 0x0000…0000 }
After · Uniblock
routed · no per-IP cap
POST https://api.uniblock.dev/uni/v1/hyperliquid/info?chainId=999
Content-Type: application/json
x-api-key: YOUR_UNIBLOCK_API_KEY
{ type: clearinghouseState, user: 0x0000…0000 }
Bodies stay identical
01
Uniblock forwards the native /info contract and returns the upstream response verbatim. Nothing downstream of the call site changes.
Your SDK keeps working
02
Point hyperliquid-python-sdk at the /uni/v1/hyperliquid prefix, attach the key as a default header, and every typed helper still resolves.
Signing is untouched
03
Uniblock changes transport and auth only. Any exchange or signing flow your SDK performs is unaffected.
Streams move separately
04
SDK WebSocket transports still point at the public endpoint. Set skip_ws and connect to the Uniblock stream to lift the subscription cap.
Setup
One key, one endpoint, typed responses.
Source APIs, SDKs, and glue code to wire up and maintain.
Coverage
Info API, HyperCore streams, and HyperEVM RPC behind one key.
Three integrations: public /info, the public WebSocket, and a node.
Limits
No per-IP request weight, no subscription cap.
Per-IP weight budget and 1,000 subscriptions per IP.
Reliability
Automatic routing and failover across providers.
You build health checks and swap providers by hand.
Cost
One plan, usage-based, no per-source minimums.
Separate accounts, minimums, and upkeep per source.
Correctness
Normalized, typed responses you can trust.
You own normalization, edge cases, and drift.
What’s shipping for Hyperliquid.
From what’s live today to the next two release windows: partners, surfaces, and API coverage on a single timeline.
Fair, transparent pricing.
One meter across the Info API, WebSockets, and HyperEVM, and across every provider in the waterfall. No juggling separate contracts, no surprise minimums, just the Hyperliquid data you actually use.
01
Usage-based
Pay for the reads you make, metered in compute units. No per-source minimums.
02
One plan
A single Uniblock plan spans every provider, Info type, and method group.
03
Streams by the minute
Each active subscription bills credits per minute at 5,000 compute units per credit, and stops the moment you unsubscribe.
04
Free to start
Generate a key and call Hyperliquid in minutes, no contract.
Before you build
What is the difference between HyperCore and HyperEVM?
Which network does this cover?
How do I authenticate?
Do I need to run a Hyperliquid node?
Can I keep using my existing Hyperliquid SDK?
Are there per-IP rate limits?
What happens if a provider degrades?
How is it priced?
Start building
One key. Every Hyperliquid read.
Generate a project key and call the Info API, the streams, and HyperEVM in minutes. Uniblock handles routing, retries, and failover across Alchemy, GoldRush, Dwellir, and Chainstack so you can just build.