Skip to main content
The Hyperliquid API gives developers programmatic access to two execution layers on one chain: HyperCore, the on-chain order book for perpetuals and spot trading, and HyperEVM, the Ethereum-compatible smart contract layer. Chainstack serves both through a single Hyperliquid node endpoint.

​
Hyperliquid API at a glance

​
Get your own node endpoint today

Start for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.

​
What is the Hyperliquid protocol

Hyperliquid is a high-performance Layer 1 blockchain that focuses on providing a deep liquidity DEX for spot trading and for perpetual trading. The Hyperliquid founder calls it the AWS of liquidity. Hyperliquid uses a custom consensus algorithm called HyperBFT, which is inspired by HotStuff and its successors. State execution operates through two components that share consensus and produce interleaved blocks:
  • HyperCore — provides fully on-chain perpetual futures and spot order books with one-block finality. HyperCore supports 200,000 orders per second, with throughput continuously improving through node software optimization. Order matching, margin, and position management run natively in Rust with zero gas fees.
  • HyperEVM — brings Ethereum-compatible smart contract functionality to Hyperliquid. It runs on chain ID 999 (mainnet) and 998 (testnet), and makes HyperCore’s liquidity and financial primitives available as permissionless building blocks for developers.
The two layers are tightly integrated. HyperEVM contracts read HyperCore order book prices, positions, and balances directly through precompiles — no external oracles — and write actions back to HyperCore through the CoreWriter system contract. See the CoreWriter guide and the infrastructure FAQ for the full architecture.

​
What is the Hyperliquid API

The Hyperliquid API lets developers build trading applications, analytics tools, and portfolio management systems. To read market data and execute trades, an application connects to a Hyperliquid node endpoint, then calls the layer it needs:
  • HyperCore exposes /info for queries (market data, account state) and /exchange for trading actions (orders, cancels, transfers).
  • HyperEVM exposes a standard JSON-RPC interface, plus WebSocket subscriptions for real-time data streaming.

​
HyperCore and HyperEVM API surface

The platform exposes distinct surfaces for each layer. The table below shows what runs where, and which surfaces Chainstack serves directly versus which route through the official Hyperliquid public API.
Chainstack serves HyperEVM on two paths that exist by default on every node: /evm (hl-node-compliant — system transactions stripped from block-shaped responses) and /nanoreth (system transactions included). Append the path you need to your endpoint URL. See Hyperliquid node configuration.

​
What you can build

With a Chainstack Hyperliquid endpoint you can:
  • Query HyperEVM chain state — balances, blocks, logs, receipts, and gas — through the standard Ethereum JSON-RPC interface, compatible with web3.js, ethers, viem, and web3.py.
  • Deploy and call Solidity contracts on HyperEVM with Hardhat, Foundry, and Remix, and read HyperCore state from those contracts through precompiles.
  • Debug and trace transactions with debug_traceTransaction, trace_block, and the Otterscan ots_* namespace on archive nodes.
  • Stream real-time data over WebSocket with eth_subscribe for newHeads, logs, and syncing.
  • Read HyperCore market and account state — meta, clearinghouseState, openOrders, l2Book, candleSnapshot, fundingHistory, and more — through /info.
  • Place, cancel, and modify orders and run transfers, staking, and vault actions through /exchange on the public Hyperliquid API.

​
Methods

Chainstack documents 212 Hyperliquid methods across the two layers: For the complete, per-method availability matrix, see Hyperliquid methods.
Methods marked “Hyperliquid public RPC” are proprietary to the Hyperliquid DEX and have not been open sourced, so they are only available on the public Hyperliquid infrastructure. If you receive Failed to deserialize the JSON body into the target type, switch that call to the public Hyperliquid RPC.

​
How to start using the Hyperliquid API

To use the Hyperliquid API, you need access to a Hyperliquid node endpoint. Follow these steps to sign up, deploy a node, and find your credentials:
  1. Sign up with Chainstack.
  2. Deploy a node.
  3. View node access and credentials.
Now you are ready to connect to the Hyperliquid blockchain and build trading applications.

​
SDKs and tooling

You can call the API directly over HTTP and WebSocket, or use a maintained SDK: Point any SDK at your Chainstack endpoint. See Hyperliquid tooling for setup and the nktkas TypeScript SDK guide for end-to-end examples.

​
Rate limits

The limits below apply to the public Hyperliquid infrastructure. A Chainstack private node removes the HyperEVM request ceiling and gives you dedicated bandwidth and geographic routing.
Private RPC becomes necessary for applications above 100 HyperEVM requests per minute, or that need SLA guarantees, event indexing, or high-frequency trading. For the full weight table and address-based action limits, see the infrastructure FAQ.

​
Networks

Chainstack supports both Hyperliquid mainnet and testnet, with full and archive node modes, WebSocket connections, and debug & trace APIs.
On testnet, archive data is available starting from block 34112653. Queries for blocks before this height will not return historical state.

​
Frequently asked questions

​
What is the difference between HyperCore and HyperEVM?

HyperCore is Hyperliquid’s native, Rust-based trading layer — it runs the perpetual and spot order books on-chain with one-block finality and zero gas fees. HyperEVM is the Ethereum-compatible smart contract layer (chain ID 999) where you deploy Solidity contracts. Both share HyperBFT consensus, and HyperEVM contracts can read HyperCore state through precompiles.

​
What is the HyperEVM chain ID?

999 on mainnet and 998 on testnet. Use the standard JSON-RPC interface at the /evm path of your Chainstack endpoint.

​
Can I place trades through Chainstack?

Trading actions on the HyperCore /exchange endpoint are available only on validator nodes, so they route through the official Hyperliquid API at api.hyperliquid.xyz. Chainstack serves all 83 HyperEVM JSON-RPC methods and 46 HyperCore /info query methods directly, which covers market data, account state, smart contract calls, and HyperEVM transaction submission.

​
Which Hyperliquid methods are available on Chainstack?

129 of 212 documented methods run directly on Chainstack nodes: all 83 HyperEVM JSON-RPC methods and 46 HyperCore /info queries. The remaining 83 (30 proprietary /info methods and 53 /exchange actions) are only available on the public Hyperliquid infrastructure. See the methods reference for the per-method breakdown.

​
Does Hyperliquid support archive data and tracing?

Yes. Chainstack offers full and archive Hyperliquid nodes on both mainnet and testnet, with debug_*, trace_*, erigon_*, and Otterscan ots_* methods for transaction tracing and smart contract debugging. On testnet, archive history starts at block 34112653.

​
What are the Hyperliquid API rate limits?

The public Hyperliquid infrastructure caps HyperEVM at 100 requests/min and REST (/info, /exchange) at 1,200 weight/min. A Chainstack private node removes the 100 requests/min HyperEVM ceiling. See the infrastructure FAQ for the full weight and address-based limits.

​
What is the difference between the /evm and /nanoreth paths?

Both serve HyperEVM JSON-RPC and exist by default on every node. /evm is hl-node-compliant and strips HyperCore ↔ HyperEVM system transactions from block-shaped responses; /nanoreth includes them. See Hyperliquid node configuration.
Last modified on June 25, 2026