Uniblock - Hyperliquid API: HyperEVM Data

Making Hyperliquid easy to build on

Together with Alchemy, GoldRush, Dwellir, Chainstack, and other leading infrastructure providers, Uniblock is building the most comprehensive, high-performance platform for Hyperliquid, offered with fair, transparent pricing.

One key, every provider

999

HyperEVM mainnet · chainId 999

Routed across Alchemy · GoldRush · Dwellir · Chainstack

Chain ID

999 / 998

Providers

4 routed

Info types

60+

RPC methods

100+

JSON-RPC console api.uniblock.dev · live

eth_blockNumberEVM
eth_getBlockByNumberEVM
eth_getBalanceEVM
eth_chainIdEVM
eth_gasPriceEVM
eth_getLogsEVM
+100 more · EVM · Debug · Trace · Erigon

Request POST

POST /uni/v1/json-rpc?chainId=999
X-API-Key: YOUR_UNIBLOCK_API_KEY

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_blockNumber",
  "params": []
}

Response 200 · routed

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": "0x24c4733"
}

Selected Latest block height on HyperEVM.

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.

HyperCore

HyperEVM

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.

Three surfaces, one key.

Info API, WebSockets, and HyperEVM JSON-RPC, all behind a single Uniblock key.

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.

Orders & fills

12 types

Live and historical order state, fill history, TWAP slices, and builder-attributed fills.

Markets & metadata

15 types

The asset universe, order book snapshots, candles, mids, funding history, and margin tables.

Vaults & staking

8 types

Vault summaries and equity, leader performance, delegations, and validator votes.

Builder & deploy

7 types

Builder-deployed perp DEXs, their limits and status, and the deploy auction state.

Lending & outcomes

5 types

Borrow-lend reserve and user state, plus prediction-market outcome metadata.

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.

l2BookDiff

0.1 credits / min

GoldRush-native. A snapshot per coin, then per-block updates carrying only the levels that changed.

l4Book

2 credits / min

GoldRush-native order-level book with user, order ID, client order ID, time-in-force, and trigger metadata.

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.

orderUpdates

1 credit / min

Order lifecycle events: placements, fills, cancels, and rejections.

allFills

1 credit / min

The complete global fill stream, with optional single-market filtering.

liquidationFills

1 credit / min

GoldRush-native global liquidation stream for risk dashboards and liquidation bots.

builderFills

1 credit / min

Attributed fills for builder addresses, carrying builder-fee data.

userNonFundingLedgerUpdates

1 credit / min

Non-funding ledger events such as deposits and withdrawals.

Powered by leading infrastructure providers

One request, routed to the best available provider. Uniblock spreads your Hyperliquid traffic across Alchemy, GoldRush, Dwellir, and Chainstack, with automatic failover behind a single key.

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

Standard reads and calls — blocks, balances, logs, gas, transactions.

Debug

12 methods

Execution traces and raw block/receipt inspection for deep debugging.

Trace

8 methods

Parity-style transaction and block traces for indexers.

Erigon

9 methods

Erigon extensions for header, logs, and block range queries.

Otterscan

11 methods

Explorer-grade lookups powering address and internal-transfer views.

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

Uniblock forwards the native /info contract and returns the upstream response verbatim. Nothing downstream of the call site changes.

Your SDK keeps working

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

Uniblock changes transport and auth only. Any exchange or signing flow your SDK performs is unaffected.

Streams move separately

SDK WebSocket transports still point at the public endpoint. Set skip_ws and connect to the Uniblock stream to lift the subscription cap.

Uniblock vs. building it yourself.

The same Hyperliquid workload, two ways to build it.

Uniblock

Build it yourself

Setup

One key, one endpoint, typed responses.

Coverage

Info API, HyperCore streams, and HyperEVM RPC behind one key.

Limits

No per-IP request weight, no subscription cap.

Reliability

Automatic routing and failover across providers.

Cost

One plan, usage-based, no per-source minimums.

Correctness

Normalized, typed responses you can trust.

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.

V1 · Available now

Partners

Covalent/Goldrush

Alchemy

Dwellir

ChainStack

V2 · Soon

Everything in V1, plus:

Market Data

Staking

Outcomes

User Performance

Asset Data

Preference-based routing

V3 · +3 Months

Everything in V2, plus:

Distributed RPC routing

Broader websocket coverage

Advanced Analytics

HYPE Uptime dashboard

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.

Usage-based

Pay for the reads you make, metered in compute units. No per-source minimums.

One plan

A single Uniblock plan spans every provider, Info type, and method group.

Streams by the minute

Each active subscription bills credits per minute at 5,000 compute units per credit, and stops the moment you unsubscribe.

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?

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.