Hyperliquid, live in your browser. Then what a key returns.

Each example below runs on Hyperliquid’s public API, right now, no key. Next to it, the answer the same question gets from Hypedexer, captured from production and dated: the wallets, the history and the full book the public feed does not keep.

Hyperliquidthis page
Connectingtrades on BTC, ETH, HYPE0 received
  1. Waiting for the next trade.

Every perpetual market, and every fill behind it.

The venue gives the totals: mark, volume, open interest. A key gives the fills those totals are made of, each with the wallet that made it.

public: a market’s totalwith a key: the fills inside it; lit, the two below

Public, keylessPOST https://api.hyperliquid.xyz/info {"type":"metaAndAssetCtxs"}

connectingtop 8 by 24h volume; a column sort reorders these rows only

With a keyrows captured 11/11/2026, 09:33 UTC

The fills, with their wallets.

fills since January 2024
4.40B
completed trades since September 2025
113M
WalletDirectionPriceSizeClosed PnL
0xe59b…cf2eClose Long73,6470.00136 BTC-$0.10
0xf6d9…3e13Close Short73,6470.00136 BTC$0.06

GET /fills/recent?coin=BTCArchive counted on 2026-10-18. Fills before March 2025: Scale and Enterprise, or free on trade-export.hypedexer.com.

The book by price. Then by order, with the address.

The public book adds up the size at each price. The L4 book on our socket lists every resting order on its own, with the wallet that placed it.

public: one size per pricewith a key: each order in it; point at a row below

Public, keylesswss://api.hyperliquid.xyz/ws

HYPE· Hyperliquid · L2
connecting
PriceSize
spread·0 trades
Tape

waiting for the first trade…

last tradednow → long ago

With a keysnapshot 12/11/2026, 00:17 UTC

Every resting order on HYPE.

resting orders in one snapshot
31,862
wallets behind them
2,506
SidePriceSizeWallet
Ask72.1620.160x6978…1cb5
Ask72.1614.830x721e…806d
Ask72.1610.70x6978…1cb5
Bid72.16136.620xf5d8…ad53
Bid72.1585.540x4e60…8f95
Bid72.15826.870x7b7f…dee2

WebSocket l4Book, coin HYPEFirst frame of the subscription. No REST route, no history.

Every exchange a builder deployed, and what trades on it.

The venue's registry lists each HIP-3 DEX and its caps. A key adds what happens on them: volume, open interest, trades, fees, and the deployment auction.

public: the 10 DEXes in the registrywith a key: the trades, and the slot on auction at 1,019.97 HYPE

Public, keylessPOST https://api.hyperliquid.xyz/info {"type":"perpDexs"}

connecting
Deployer

With a keycaptured 12/11/2026, 00:18 UTC

All HIP-3 exchanges, in one call.

volume, last 24h
$5.10B
open interest
$4.61B
trades, last 24h
6.96M
Exchanges10 DEXes, 283 assets
Fees, last 24h$510K
Deployment auctionopen, 1,019.97 HYPE, ends 13/11/2026, 00:00 UTC

GET /hip3/overview

The next funding rate. And every one before it.

The venue predicts the next print on three exchanges. A key returns the prints already paid, hour by hour, for any market, with the premium behind each.

public: the next print, predictedwith a key: every print since 2023-05-12; lit, the two below

Public, keylessPOST https://api.hyperliquid.xyz/info {"type":"predictedFundings"}

connecting
Market

With a keyrows captured 11/11/2026, 09:33 UTC

Funding history, hour by hour.

first print served, 2023-05-12
2023
BTC, paid atRate per hourPremium
11/11 09:00 UTC0.00125%-0.0344%
11/11 08:00 UTC0.00125%-0.0272%

GET /funding/fundingHistory?coin=BTC

Or ask it in plain language.

The MCP server puts the same archive inside Claude or Cursor. Three real questions, replayed as they were answered.

See the MCP server
an assistant with the Hypedexer MCP servercaptured 11/11/2026, 09:43 UTC
  1. You

your agentMCP serverHyperCoreHyperEVMElysium
askinghd_buildersyour agent reads the question

And read the chains over RPC.

HyperEVM and Elysium JSON-RPC on archive nodes, with the same key: every Data API plan carries a monthly RPC quota. Two real calls, replayed.

$ 

HTTP/2 200
x-rpc-requests: 1

{"jsonrpc":"2.0","id":1,"result":"0x3088255"}
# block 50,889,301
Replay of a production call, Nov 10, 2026, 11:58 UTC

Four services, one key.

A stake with Enigma can pay for a Data API plan, and every Data API plan carries RPC.

Start free: 5,000 credits a month, no card.

Every answer marked With a key on this page comes from one key. Start free, then let a stake with Enigma pay for the plan.