How to get a Hyperliquid RPC endpoint

Learn how to get a Hyperliquid RPC endpoint for both mainnet and testnet, choose between public and private options, and set up a reliable RPC provider.

TL;DR

Hyperliquid is an L1 with a native order book and an EVM-compatible execution layer (HyperEVM). As usage grows, public HyperEVM RPC access is increasingly constrained for high-frequency workloads.

Starting August 9 2025, public HyperEVM RPC is rate-limited to 100 requests/minute per IP. That is usually fine for testing and light reads, but it is a bottleneck for bots, indexers, and latency-sensitive systems.

This guide explains:

1. Public vs private Hyperliquid RPC access.
2. Full vs archive node trade-offs.
3. How to get a private endpoint for production workloads.
4. How to use official public endpoints for testing.

Hyperliquid API endpoint cheat sheet

Use this as a quick integration reference for HyperEVM RPC access.

Endpoint format

• Mainnet public RPC (read-only): https://rpc.hyperliquid.xyz/evm
• Testnet public RPC (read-only): https://rpc.hyperliquid-testnet.xyz/evm
• Private RPC pattern: https://<your-rpc-host>/evm
• Optional private info endpoint: https://<your-rpc-host>/info

Auth header pattern

• Public endpoints: no auth header.
• Private endpoints (provider-specific):
  Authorization: Bearer <API_TOKEN>
  or
  x-api-key: <API_KEY>

Minimal cURL

```bash
curl -sS https://rpc.hyperliquid.xyz/evm \
-H 'content-type: application/json' \
--data '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

What is a Hyperliquid RPC endpoint?

A Hyperliquid RPC endpoint lets you read data from the HyperEVM (the chain’s EVM-compatible execution layer) over HTTP.  If you’ve worked with Ethereum, this will feel familiar: the HyperEVM implements a subset of the standard JSON-RPC API used across EVM chains.

Hyperliquid runs two execution environments under one consensus: HyperCore, the trading engine that handles the order book and exchange logic, and HyperEVM, the smart contract layer. RPC endpoints only expose the EVM layer. Trading actions are routed through a separate API path with different capabilities.

When you send a request to a Hyperliquid RPC endpoint, you’re querying data or simulating state transitions from the HyperEVM. The RPC is used to read contract state, check balances, fetch logs, and simulate calls, but not to send transactions. Execution happens off-path, through a separate submission layer that functions more like a sequencer than a traditional mempool.

Hyperliquid RPC layer is designed to support bots, dashboards, indexers, and other offchain infra that rely on fast, consistent access to chain data.

This makes the choice of RPC provider (or the decision to self-host) especially important if you’re building production infrastructure.

Public vs private Hyperliquid RPC endpoints

There are two ways to access the HyperEVM RPC: through the public endpoint maintained by the core team, or via a private RPC, either self-hosted or through a provider like Chainstack.

In short: If your workload is occasional and non-critical, public RPC is acceptable.
If you need stable throughput, lower latency variance, observability, or operational guarantees, private RPC is the safer default.

Full node vs archive Hyperliquid node

Hyperliquid nodes can be configured to store varying amounts of historical data. Full nodes typically store recent blockchain state, while archive nodes retain complete historical data from genesis.

How to get a private Hyperliquid RPC endpoint on Chainstack

Chainstack now supports private Hyperliquid RPC endpoints via GEN, available on all paid plans. These endpoints offer higher request throughput than the public RPC, removing the 100 requests/minute limit per IP.

To get started:

1. Log in to your Chainstack account. Create an account if you don’t have one.
2. Create a new project or select an existing project.
3. Choose Hyperliquid as your network and select mainnet or testnet.
4. Deploy a node configured for Hyperliquid RPC access.
5. Once deployed, your private RPC URLs, including the /evm and /info endpoints, will be available in your node dashboard.

You can then use these endpoints in your trading bots, indexers, or real-time apps without worrying about public rate limits.

Chainstack also gives you visibility into how it’s performing: logs, metrics, and request data. You can also lock it down with Access rules to avoid leaking keys or getting spammed.

Here’s what it looks like to spin up your own HyperEVM RPC endpoint in less than two minutes with Chainstack:

💡 Quick tips for stable Hyperliquid RPC performance

• Use HTTP for simple reads, WebSocket for real-time data – WebSockets are great for subscriptions (eth_subscribe, pending txs, logs). For everything else, HTTP is faster and easier to retry.
• Add a fallback RPC – If your primary endpoint fails, route to a backup (public or secondary private). Log failovers so you can catch issues early.
• Cache aggressively – Don’t hit the RPC for static data like token metadata or contract ABIs. Cache locally and refresh only when needed.
• Monitor your usage – Chainstack gives you metrics on latency, errors, and request volume. Use them to spot issues before they break your app.

How to get a public Hyperliquid RPC endpoint

Hyperliquid provides a free, publicly accessible HyperEVM RPC endpoint—ideal for testing, prototyping, or light scripting. It’s maintained by the core team and can be used without signup, but as of August 2025, it’s rate-limited to 100 requests per minute per IP.

Official Hyperliquid public RPC URLs

What’s supported

These endpoints support standard read-only JSON-RPC methods like:

• eth_call – Execute a message call without creating a transaction
• eth_getLogs – Get logs matching a filter
• eth_blockNumber – Get the current block number

Important limitations:

• ❌ No transaction submission
• ❌ No gas estimation
• ❌ No WebSocket support
• ⚠️ 100 requests/minute rate limit per IP

For production applications or anything requiring higher throughput, use a private RPC endpoint instead.

Supported methods / limits / errors

This table summarizes practical method availability and common failure patterns for integration planning.

How to add Hyperliquid to your wallet

MetaMask doesn’t come preloaded with Hyperliquid, and neither do most EVM-compatible wallets like Rabby, or Rainbow. Whether you’re using a private RPC URL from Chainstack or the public endpoint, you’ll need to add the network manually.

The steps below use MetaMask, but they work for any EVM wallet that supports custom networks.

Option 1: Add your private Hyperliquid RPC

To use a private Hyperliquid Mainnet RPC:

1. Open wallet
2. Click the network dropdown → Add network manually
3. Fill in the fields:

To use a private Hyperliquid Testnet:

Option 2: Use a public Hyperliquid RPC URL

If you don’t have a private endpoint, you can use a public RPC URL instead. These are shared across all users and may be rate-limited or less reliable.

These endpoints support standard read-only JSON-RPC methods like eth_call, eth_getLogs, and eth_blockNumber. They do not support transaction submission or gas estimation. Use the same MetaMask steps as above, just paste in the public URL instead of your private one.

Conclusion

Hyperliquid public RPC is useful for testing and light read workloads, but production systems typically require private infrastructure for predictable throughput and reliability.

If your application depends on continuous reads, low latency variance, or operational controls, use private Hyperliquid RPC and treat public endpoints as fallback or development-only access.

FAQ

Recommended reading

If you want to go deeper into the Hyperliquid ecosystem and start building production-ready trading systems, we also recommend checking out the following guides:

• What is Hyperliquid? — an overview of Hyperliquid’s architecture.
• How to build a Hyperliquid trading bot — a step-by-step guide to set up and wire a trading bot.
• Hyperliquid On-Chain Activity Tracker — build automated alerts with Hyperliquid RPC.
• Mastering Hyperliquid — guides to Hyperliquid APIs, authentication, and trading.

Power-boost your project on Chainstack

• Discover how you can save thousands in infra costs every month with our unbeatable pricing on the most complete Web3 development platform.
• Input your workload and see how affordable Chainstack is compared to other RPC providers.
• Connect to Ethereum, Solana, BNB Smart Chain, Polygon, Arbitrum, Base, Optimism, Avalanche, TON, Ronin, zkSync Era, Starknet, Scroll, Aptos, Fantom, Cronos, Gnosis Chain, Klaytn, Moonbeam, Celo, Aurora, Oasis Sapphire, Polygon zkEVM, Bitcoin and Harmony mainnet or testnets through an interface designed to help you get the job done.
• To learn more about Chainstack, visit our  Developer Portal or join our Discord server and Telegram group.
• Are you in need of testnet tokens? Request some from our faucets. Multi-chain faucet, Sepolia faucet, Holesky faucet, BNB faucet, zkSync faucet, Scroll faucet.