This page outlines pricing for Hyperliquid JSON-RPC methods, WebSocket subscriptions, and gRPC streaming. All costs are measured in API credits.
Network Specifications
Hyperliquid generates approximately 12 blocks per second, resulting in ~31 million blocks per month. This high block frequency affects data volume and credit consumption for streaming applications.
JSON-RPC Methods
Each JSON-RPC method call consumes credits based on the operation performed. Billing is per API response, meaning every successful response (including empty blocks) is counted.
Hyperliquid can produce blocks without transactions due to its high block frequency. These empty blocks return valid data and are billed at standard rates.
Block Data Methods
| Method | Credits | Description |
|---|---|---|
| hl_getBlock | 20 | Single block data |
| hl_getLatestBlockNumber | 20 | Current block number |
| hl_getLatestBlocks | 5 per block | Up to 200 recent blocks |
| hl_getBatchBlocks | 5 per block | Up to 200 specified blocks |
Portfolio & Account Data Methods
| Method | Credits | Description |
|---|---|---|
| hl_portfolioState | 40 | Single user portfolio state (perp positions, spot balances, account mode) |
| hl_batchClearinghouseStates | 5 per address | Batch perp positions for up to 1000 users |
| hl_batchPortfolioStates | 5 per address | Batch portfolio states for up to 500 users |
| hl_batchOpenOrders | 5 per address | Batch open orders for up to 100 users |
REST API Methods
REST API endpoints for trading operations, builder fee management, and market queries are provided free of charge (0 credits).
| Endpoint | Credits | Description |
|---|---|---|
| POST /exchange (Build Order) | 0 | Build order action for signing |
| POST /exchange (Build Market Order) | 0 | Build market order with 3% slippage |
| POST /exchange (Build Close Position) | 0 | Build close position order |
| POST /exchange (Build Cancel) | 0 | Build cancel order action |
| POST /exchange (Build Modify) | 0 | Build modify order action |
| POST /exchange (Build Approval) | 0 | Build approval for builder fee |
| POST /exchange (Build Revoke) | 0 | Build revocation for builder fee |
| POST /exchange (Send Order) | 0 | Send signed order to exchange |
| POST /exchange (Send Cancel) | 0 | Send signed cancellation |
| POST /exchange (Send Modify) | 0 | Send signed modification |
| POST /exchange (Send Approval) | 0 | Send signed builder fee approval |
| POST /exchange (Send Revoke) | 0 | Send signed builder fee revocation |
| GET /approval | 0 | Check builder fee approval status |
| POST /openOrders | 0 | Query open orders with cancel actions |
| POST /orderStatus | 0 | Check order status with plain-English explanation |
| POST /preflight | 0 | Validate order without signing |
| GET /markets | 0 | List all available markets (perps, spot, HIP-3) |
| GET /dexes | 0 | List all HIP-3 DEX names |
Batch Method Billing
The batch methods hl_getLatestBlocks and hl_getBatchBlocks can return a maximum of 200 blocks per request. These methods are billed at 5 credits per block returned.
For example: A request that returns 50 blocks is charged at 250 credits (50 × 5).
Portfolio Batch Method Billing
The batch methods hl_batchClearinghouseStates, hl_batchPortfolioStates, and hl_batchOpenOrders are billed at 5 credits per user address in the request.
For example: A request for 50 user addresses with hl_batchPortfolioStates is charged at 250 credits (50 × 5).
WebSocket Subscriptions
WebSocket connections enable real-time data streaming from Hyperliquid. Charges include subscription management and data transfer costs. Data volume is calculated based on the total size of messages received from your active subscriptions.
| Operation | Cost |
|---|---|
| hl_subscribe | 0 credits |
| hl_unsubscribe | 20 credits |
| Data streaming | 10 credits per 0.1 MB |
gRPC Streaming
gRPC provides streaming with advanced filtering capabilities. Billing is based on the volume of raw data that matches your subscription filters. gRPC streaming is billed at 10 credits per 0.1 MB of filtered data.
Plan Limits
These limits apply to both gRPC and WebSocket streaming - the two protocols share the same tier-based caps. See the Streaming Limits table for the full breakdown including per-field filter caps.
| Plan | Concurrent Streams | Named filters per stream |
|---|---|---|
| Free Trial | None | - |
| Build | 1 | Up to 5 |
| Accelerate | 5 | Up to 10 |
| Scale | 10 | Up to 25 |
| Business | 25 | Up to 50 |
| Enterprise | Custom | Custom |
Questions
Have questions about pricing or need help estimating your usage? Contact our support team.