Hyperliquid - High-Performance Trading Infrastructure
Complete guide to Hyperliquid integration with Dwellir. Access HyperEVM JSON-RPC endpoints and L1 gRPC streaming for order books and trading data.
HyperLiquid RPC
With Dwellir, you get access to our global HyperLiquid network which always routes your API requests to the nearest available location, ensuring low latency and the fastest speeds.
Get your API keyHyperliquid plans and pricing
- gRPC and Order Book: $299/month for gRPC or $199/month for the Order Book, added to an API platform plan. Each streamed message costs 1 API credit.
- Dedicated Node Cluster: Starts at $4,000/month and 2 dedicated nodes. HyperEVM JSON-RPC, Info, gRPC and Order Book access are included, with no usage fees.
Details: Hyperliquid pricing · Shared plans · Rate limits · Authentication
Choose an access path
| Need | Start with | Use it for |
|---|---|---|
| Stream node records or replay recent data | L1 gRPC Streaming API | Raw blocks, fills, statuses, book diffs, events, and TWAPs, with V3 server-side filtering where supported |
| Consume live L2/L4 books and trades | Order Book WebSocket API | Purpose-built order books and trade streams |
| Query indexed candles, fills, orders, and TWAPs | Hyperliquid Index | Queryable historical market and account data |
| Download node files and long-range raw data | Archival data | S3 Bucket files for research, replay, and backtesting |
| Query current market and user state | HyperCore Info endpoint | HTTP request-response queries for metadata, positions, vaults, and exchange state |
| Keep your own node peered and in sync | Hyperliquid Peering | Reserved gossip peer slots with full mempool and a 99.9% uptime SLA |
How Hyperliquid works
For endpoint selection, symbols, quiet streams, replay, reconnects, freshness, and peering, see streaming troubleshooting.
For the protocol-level picture, including HyperBFT consensus, HyperCore, HyperEVM, API servers, nodes, and public rate limits, see How Hyperliquid's infrastructure works.
Hyperliquid nodes write raw protocol records to disk. Dwellir exposes available raw feeds through gRPC, while the historical archive preserves native files for longer-term workflows.
Data written by the node
| Node source | Purpose | Live access | Archival data |
|---|---|---|---|
replica_cmds | Hyperliquid blocks, signed actions, responses, and consensus metadata | StreamBlocks, GetBlock | S3 Bucket from 2025-01-25 to 2026-09-28 |
node_fills_by_block | Per-account execution records grouped by sequential block number | StreamFills, GetFills, hl_getBatchBlocks | S3 Bucket from 2025-07-27 to 2026-09-28; tick data; indexed fills |
node_order_statuses_by_block | Order lifecycle events, including opens, fills, cancellations, and rejections | StreamOrderStatuses, GetOrderStatuses | S3 Bucket from 2026-01-22 to 2026-09-28; indexed order history |
node_raw_book_diffs_by_block | Native order-level additions, updates, and removals | StreamRawBookDiffs, GetRawBookDiffs | S3 Bucket from 2026-01-22 to 2026-09-28 |
misc_events_by_block | Miscellaneous protocol events | StreamMiscEvents, GetMiscEvents | S3 Bucket from 2026-06-29 to 2026-09-28 |
node_twap_statuses_by_block | TWAP lifecycle events | StreamTwapStatuses, GetTwapStatuses | S3 Bucket from 2026-07-01 to 2026-09-28 |
periodic_abci_states | Periodic RMP state dumps that can seed generated order-book snapshots | Dedicated Node Cluster gRPC | S3 Bucket from 2026-04-14 to 2026-09-28 |
Order books and derived data
V3 market streams expose typed live views without backfill. Use Archival data or indexed history when you need historical coverage.
Order-book reconstruction requires a snapshot or another known state seed followed by ordered diffs. Raw diffs alone are insufficient. For trades, a match can contain multiple makers. Within one block, group fills by (coin, tid). Across blocks, include block_number or block_time because tid is not globally unique.
Why Build on Hyperliquid?
Hyperliquid is a high-performance Layer 1 blockchain purpose-built for decentralized trading, offering both EVM compatibility through HyperEVM and specialized L1 features through gRPC streaming.
Blazing Fast Performance
- Sub-second finality - Near-instant transaction confirmations
- 200,000 orders/second - Unprecedented throughput for DeFi
- Predictable low fees - Stable and minimal transaction costs
Dual API Architecture
- HyperEVM - Full EVM compatibility for Solidity smart contracts
- L1 gRPC Streaming - Real-time order books and market data
- Native Trading Primitives - Built-in support for spot and perpetuals
Trading-Optimized Infrastructure
- Fully on-chain order books - No off-chain components
- HyperBFT consensus - Optimized for trading performance
- Real-time market data - Stream fills, trades, and order updates
Quick Start with Hyperliquid
Pricing and access
Dwellir provides HyperEVM JSON-RPC and HyperCore trading data, including Info, gRPC, and Order Book endpoints. An EVM RPC endpoint alone does not include HyperCore market streams.
On the shared cluster, add gRPC ($299/month) or Order Book ($199/month) access to an API plan. Both add-ons are metered: each streamed message costs 1 API credit.
A Dedicated Node Cluster starts at $4,000/month and 2 dedicated backend nodes. HyperEVM JSON-RPC, Info, gRPC, and Order Book access are included and unmetered. There are no separate gRPC or Order Book add-on fees.
HyperEVM JSON-RPC is sold through the Dwellir API platform on the same plans as every other network, billed at 1 API credit per response. Create an API key in the dashboard and use the HyperEVM endpoint:
curl -sS -X POST https://api-hyperliquid-mainnet-evm.n.dwellir.com/<your-api-key> \ -H 'Content-Type: application/json' \ -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'Installation & Setup
Network Information
| Parameter | Value | Details |
|---|---|---|
| Chain ID | 999 | Mainnet |
| Block Time | < 1 second | Sub-second finality |
| Gas Token | HYPE | Native token |
| Consensus | HyperBFT | Trading-optimized |
API Reference
HyperEVM JSON-RPC API
HyperEVM provides full Ethereum compatibility, supporting all standard JSON-RPC methods for smart contract deployment and interaction.
EVM Integration Examples
Order Book WebSocket API
Access real-time L2 and L4 order-book data through the Order Book WebSocket API:
Orderbook API Overview & Calculator
Explore the hosted orderbook endpoint, throughput calculator, and deployment options for Hyperliquid market data workloads.
WebSocket API Documentation
Reference for subscriptions, message formats, connection behavior, and real-time order book stream integration.
L1 gRPC Streaming API
Access Hyperliquid's native Layer 1 features through our specialized gRPC interface:
Available gRPC Streams
- Order Book Snapshots - Generated snapshots through the snapshot RPCs
- Block Streaming - Real-time block updates
- Trade Streams - Live trade execution data
- Fill Streams - Order fill notifications
Quick gRPC Example (V3)
Common Integration Patterns
Algorithmic Trading
Combine HyperEVM smart contracts with L1 streaming for sophisticated trading:
// Deploy strategy contract via HyperEVM
const strategy = await deployContract(strategyABI, strategyBytecode);
// Stream blocks via gRPC for trading data
const blockStream = grpcClient.StreamBlocks();
blockStream.on('data', async (block) => {
const signal = analyzeBlockData(block);
if (signal.shouldTrade) {
await strategy.executeTrade(signal.params);
}
});Market Making
Provide liquidity using real-time data:
# Monitor block data via gRPC
for block in stub.StreamBlocks(timestamp):
data = analyze_block(block)
if data.spread > target_spread:
# Place orders via HyperEVM
place_limit_orders(provider, spread)DeFi Composability
Build complex DeFi applications:
// Leverage Hyperliquid's native features
contract YieldVault {
function harvestAndCompound() external {
// Access perpetuals for hedging
// Use spot for liquidity
// Compound yields automatically
}
}Use Cases
Perpetuals Trading
Leverage Hyperliquid's native perpetuals with up to 40x leverage (BTC), fully on-chain order books, and sub-second execution.
Spot Trading
Access deep liquidity for spot markets with minimal slippage and predictable fees.
Market Making
Provide liquidity using HyperEVM smart contracts combined with L1 streaming for optimal spreads.
Cross-Chain Arbitrage
Build bridges and arbitrage bots leveraging Hyperliquid's speed advantage over other chains.
Agent Skill
The Hyperliquid agent skill gives AI coding agents procedural knowledge for building on Hyperliquid through Dwellir's infrastructure. It follows the open Agent Skills standard, making it portable across 40+ AI coding agents including Claude Code, Cursor, and Windsurf.
Install it with a single command:
npx skills add dwellir-public/hyperliquid-skillsOnce installed, the skill automatically activates when your agent encounters Hyperliquid-related tasks. It covers HyperEVM JSON-RPC, the Info API, gRPC streaming, order book WebSocket access, and native API routing for order placement.
Resources & Support
Developer Resources
- HyperEVM JSON-RPC - Full Ethereum-compatible RPC interface
- L1 gRPC API Reference - Streaming API documentation
- V2 and V3 proto contracts - Checked-in service definitions and version guidance
- Testing Tools - 16MB Go binary for stream verification
API Access
- gRPC and Order Book add-ons: $299/month and $199/month on any API plan, metered per streamed message
- Dedicated Node Cluster: from $4,000/month with gRPC and Order Book add-ons included
- Custom Endpoints - Isolated infrastructure for your application
- Uncapped Throughput - No rate limits on dedicated node clusters
Need Help?
- Email: support@dwellir.com
- HyperEVM Docs: Standard Ethereum JSON-RPC methods
- L1 Streaming: gRPC API Reference
- Dashboard: dashboard.dwellir.com
Build on Hyperliquid with Dwellir: HyperEVM JSON-RPC on the standard API plans, L1 streaming add-ons, or a Dedicated Node Cluster. Create an API key
rpc_methods
List all available RPC methods on Hydration. Essential for API discovery, capability detection, and building dynamic tooling for Substrate-based chains.
How Hyperliquid's Infrastructure Works
HyperBFT consensus, HyperCore and HyperEVM execution, API servers, non-validating nodes, and the public rate limits that shape production Hyperliquid infrastructure.

