BlogFor dapps, bots and indexers on HyperEVM

HyperEVM RPC: Endpoints, Limits and Archive Access

HyperEVM RPC URLs and chain IDs, what the public endpoint allows, and how to get archive state, wide eth_getLogs and WebSocket on your own key.

HyperEVM is the EVM chain that runs alongside Hyperliquid's order book. Like any EVM chain, you reach it through a JSON-RPC endpoint: a wallet, Foundry, viem, ethers or an indexer all speak the same protocol.

Hyperliquid runs a public endpoint that anyone can use without signing up. This guide lists the URLs, what the public endpoint allows, where it stops, and how to get archive access when you need more.

The short answer

NetworkChain IDPublic endpointOn a Hypedexer key
HyperEVM mainnet999https://rpc.hyperliquid.xyz/evmhttps://rpc.hypedexer.com/hyperevm/$KEY
HyperEVM testnet998https://rpc.hyperliquid-testnet.xyz/evmhttps://rpc.hypedexer.com/hyperevm-testnet/$KEY
Elysium mainnet99901https://rpc.hypedexer.com/elysium/$KEY
Elysium testnet99801https://rpc.hypedexer.com/elysium-testnet/$KEY

The public URLs and chain IDs are the ones in Hyperliquid's HyperEVM documentation. On a Hypedexer key, the same URLs answer over WebSocket with wss:// instead of https://.

Adding HyperEVM to a wallet

In MetaMask or any EVM wallet, add a network by hand:

  • Network name: HyperEVM
  • RPC URL: https://rpc.hyperliquid.xyz/evm, or your own https://rpc.hypedexer.com/hyperevm/$KEY
  • Chain ID: 999
  • Currency symbol: HYPE

HYPE on HyperEVM has 18 decimals, on mainnet and testnet alike. A wallet cannot set a header, which is why the Hypedexer key goes in the path: the URL works as pasted.

What the public endpoint allows

The public endpoint is the right place to start, and for a wallet or a light script it is often all you need. Its limits, from Hyperliquid's own documentation:

the public endpoint: state at the latest block onlyan archive node: state at any block, back to the first
  • 100 requests a minute per IP for rpc.hyperliquid.xyz/evm (rate limits).
  • Latest block only for eth_call, eth_estimateGas, eth_getBalance, eth_getCode, eth_getStorageAt and eth_getTransactionCount. Requests that need historical state are not supported on the default implementation (JSON-RPC).
  • eth_getLogs over 50 blocks at most per query, with up to 4 topics.
  • No WebSocket: there is no WebSocket JSON-RPC on the public endpoint, so no eth_subscribe.

None of this is a flaw. A shared endpoint has to be fair to everyone, and Hyperliquid's documentation itself points to other providers for archive functionality.

When you need more

You outgrow the public endpoint the day one of these becomes part of the job:

  • Reading the past. A balance, a contract's storage or the result of an eth_call at a block that is not the latest one: an accounting snapshot, a backtest, a dispute over what a vault held on a given day.
  • Indexing events. Fifty blocks per eth_getLogs means thousands of calls to walk a contract's history, each one counted against 100 a minute.
  • Following the chain live. New blocks and logs pushed over eth_subscribe instead of polling.
  • Steady volume. A bot or a backend that cannot share a per-IP budget with everyone behind the same address.

Archive RPC on a Hypedexer key

Hypedexer serves HyperEVM and Elysium JSON-RPC from archive nodes run by Enigma, a Hyperliquid validator. Every block's state is queryable, over HTTPS and WebSocket.

Public endpointFree keyPaid plans
Requests100 a minute, per IP10 a secondup to 300 a second
Statelatest block onlyany block, archiveany block, archive
eth_getLogs range50 blocks2,000 blocksup to 100,000 blocks
WebSocketnoneeth_subscribeeth_subscribe

Every plan carries a monthly quota of RPC requests:

  • Free: 1M requests a month, no card.
  • RPC plan: 15M requests a month for $49, at 50 requests a second. JSON-RPC only, no Data API.
  • Data API plans: Starter includes 25M, Growth 150M, Scale 500M, on top of the API credits.

Most calls count as one request. eth_getLogs, eth_getFilterLogs and eth_getBlockReceipts count three, Otterscan's ots_* two, and eth_chainId nothing. Each response reports what it counted, so usage is never a surprise at the end of the month. Full plans are on pricing, and the methods, limits and errors in the RPC docs.

Calls to copy

The latest block:

bash
curl https://rpc.hypedexer.com/hyperevm/$HYPEDEXER_KEY \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

A balance at a past block, which the public endpoint refuses:

bash
curl https://rpc.hypedexer.com/hyperevm/$HYPEDEXER_KEY \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_getBalance","params":["0xYourAddress","0x1000000"]}'

With Foundry, the URL goes straight into --rpc-url:

bash
cast block-number --rpc-url https://rpc.hypedexer.com/hyperevm/$HYPEDEXER_KEY
cast balance 0xYourAddress --block 16777216 --rpc-url https://rpc.hypedexer.com/hyperevm/$HYPEDEXER_KEY

And new blocks pushed over WebSocket:

json
{"jsonrpc":"2.0","id":1,"method":"eth_subscribe","params":["newHeads"]}

sent on wss://rpc.hypedexer.com/hyperevm/$HYPEDEXER_KEY.

FAQ

What is the HyperEVM chain ID? 999 on mainnet, 998 on testnet.

What is the HyperEVM RPC URL? https://rpc.hyperliquid.xyz/evm is Hyperliquid's public endpoint. With a Hypedexer key, https://rpc.hypedexer.com/hyperevm/$KEY.

Is there a free HyperEVM RPC? Yes: Hyperliquid's public endpoint, at 100 requests a minute per IP and latest-block state. A free Hypedexer key gives 1M requests a month on archive nodes, with no card.

Does the HyperEVM RPC support WebSocket? Not the public endpoint. On a Hypedexer key, every plan serves WebSocket with eth_subscribe.

How do I query HyperEVM state at a past block? You need an archive node: the public endpoint answers state calls for the latest block only. Any Hypedexer key serves every block.

Does it also serve Hyperliquid's order book data? No: HyperEVM RPC is the EVM chain. Fills, the order book, funding and liquidations from HyperCore come from the Data API, on the same key.

Keep reading.

  • For bots, dashboards and data pipelines

    Hyperliquid API Limits: Rate Limits, WebSocket, History

    Hyperliquid's API rate limits, WebSocket limits and history caps, quoted from the official docs, and what changes on a Hypedexer key.

    • REST: a weight budget per IP
    • History: the most recent items only
    • WebSocket limits
    • +2

    4 min read

  • For analysts, researchers and AI agents

    A Read-Only Hyperliquid MCP Server for Claude and Cursor

    Connect Claude or Cursor to Hyperliquid's full history: read-only tools, no wallet and no private key, hosted or local, every answer traceable.

    • Read-only, and no private key
    • What the agent can reach
    • Connect it: hosted, nothing to install
    • +3

    4 min read

  • Start here: every dataset, since when

    Hyperliquid Historical Data: What Exists and How to Get It

    Where Hyperliquid historical trades, fills, funding and order book data live, how far back each goes, and how to download it, from January 2024 to today.

    • The short answer
    • What the official Hyperliquid API gives you
    • What the public S3 archive gives you
    • +2

    5 min read

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