Hyperliquid RPC Endpoint

Flat-rate Hyperliquid RPC provider and Hyperliquid RPC node access: free tier, no KYC, HTTP & WebSocket. Hyperliquid mainnet chain ID 999.

HyperEVM is not a rollup — it runs natively inside Hyperliquid's own Layer 1, sharing state with HyperCore, the high-performance trading engine. Fees, staking and governance all use HYPE, and the network settles in well under a second.

About Hyperliquid

Hyperliquid began as an on-chain perpetuals exchange running its own HyperBFT-based Layer 1 (HyperCore). HyperEVM added Ethereum-compatible smart contracts to that same chain in February 2025, so EVM contracts and native HyperCore state can call each other directly instead of going through a bridge.

HYPE moves between the two execution environments by sending to a reserved address (0x2222222222222222222222222222222222222222), and the network is secured by a small active validator set with delegation. From an RPC point of view the surface is standard eth_*, with unusually short block intervals for a chain this active.

Common Use Cases on Hyperliquid

• Perpetuals and spot trading
• DeFi protocols
• On-chain market data
• Prediction markets

Hyperliquid Mainnet RPC URL (HTTP)

Hyperliquid WebSocket RPC URL

Quick Start: Connect to Hyperliquid

cURL

curl -X POST https://rpc.swiftnodes.io/rpc/hyperliquid?key=YOUR_API_KEY \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

ethers.js

import { JsonRpcProvider } from "ethers";

const provider = new JsonRpcProvider(
  "https://rpc.swiftnodes.io/rpc/hyperliquid?key=YOUR_API_KEY"
);

const blockNumber = await provider.getBlockNumber();
console.log("Hyperliquid block:", blockNumber);

viem

import { createPublicClient, http } from "viem";

const client = createPublicClient({
  transport: http("https://rpc.swiftnodes.io/rpc/hyperliquid?key=YOUR_API_KEY"),
});

const blockNumber = await client.getBlockNumber();

web3.py

from web3 import Web3

w3 = Web3(Web3.HTTPProvider("https://rpc.swiftnodes.io/rpc/hyperliquid?key=YOUR_API_KEY"))
print("Hyperliquid block:", w3.eth.block_number)

Add Hyperliquid to MetaMask

Features of SwiftNodes for Hyperliquid

• Load-balanced across multiple upstream nodes wherever a chain has more than one, with automatic failover
• Health-checked every 2 minutes with automatic failover
• Free tier available — no credit card or KYC required
• Flat-rate monthly pricing with no per-request fees
• HTTP and WebSocket support
• One API key works across all 75+ supported chains, including Hyperliquid

Rate Limits

Hyperliquid RPC methods

Measured weekly through this endpoint: what each method returns on Hyperliquid, its limits, and an example request.

• eth_blockNumbersupported
• eth_chainIdsupported
• eth_getBalancesupported
• eth_getBlockByNumbersupported
• eth_getTransactionByHashsupported
• eth_getTransactionReceiptsupported
• eth_callsupported
• eth_estimateGassupported
• eth_gasPricesupported
• eth_maxPriorityFeePerGassupported
• eth_sendRawTransactionsupported
• eth_getTransactionCountsupported
• eth_getCodesupported
• eth_subscribesupported
• eth_getLogssupported
• eth_getBlockReceiptssupported
• eth_feeHistorysupported
• eth_getProofnot available
• eth_createAccessListnot available
• debug_traceCallsupported
• trace_blocksupported
• trace_transactionsupported

Hyperliquid guides from the blog

• Hyperliquid RPC: A Developer's GuideHow to query HyperEVM over JSON-RPC — chain 999, ~1s blocks, a near-fixed 0.1 gwei base fee, a 1000-block and 1 MiB eth_getLogs cap, no WebSocket, and the one that will cost you money: state methods accept a block number and then ignore it, so historical reads silently return the latest state.

Related EVM chains

Explore RPC endpoints for other EVM networks on SwiftNodes: