This page covers Hyperliquid endpoint plan access, HyperCore method and streaming credit costs, stream and filter limits, and plan errors. SQL Explorer query costs are not listed here; SQL Explorer uses a separate query API.

Plan Access

Feature	Free Trial	Build+	Notes
HyperEVM (/evm)	✓	✓	Available on all plans
Debug & Trace (/nanoreth)	✓	✓	Available on all plans
HyperCore /info endpoint	✓	✓	All 73 methods, including l2Book and recentTrades; see method availability
REST API (/hypercore/*)	✓*	✓	*Free trial uses a shared URL, not account-specific
/hypercore JSON-RPC	✗	✓	Build plan or higher required
/hypercore WebSocket	✗	✓	Build plan or higher; stream and filter limits apply - same as gRPC
HyperCore gRPC streaming	✗	✓	Build plan or higher; stream and filter limits apply - same as WebSocket

View full pricing and plan details →

Rate Limits

Request-per-second limits follow your plan tier and apply to HTTP and JSON-RPC calls, including hl_subscribe and hl_unsubscribe. Data delivered through an open subscription does not count. View plan rate limits.

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.

HyperCore Info Endpoint

All supported /info endpoint methods cost 20 API credits per request.

All 73 info methods are available through Quicknode's /info endpoint, including l2Book and recentTrades. For real-time updates, gRPC streaming is also available on eligible plans:

• l2Book — StreamL2Book provides real-time order book snapshots via gRPC.
• recentTrades — StreamData (TRADES stream) provides real-time trades via gRPC.

gRPC streaming rates vary by method. Standard methods are billed at 10 credits per 0.1 MB, most OrderBook methods at 10 credits per 0.0165 MB, and StreamBboBook at 10 credits per 0.00165 MB. See gRPC Streaming below for the full breakdown.

Exchange API

Exchange 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

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. Billed at 5 credits per block returned. For example, a request returning 50 blocks is charged 250 credits (50 × 5).
hl_getBatchBlocks	5 per block	Up to 200 specified blocks. Billed at 5 credits per block returned. For example, a request returning 50 blocks is charged 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

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. Billed at 5 credits per user address. For example, 50 addresses is charged 250 credits (50 × 5).
hl_batchPortfolioStates	5 per address	Batch portfolio states for up to 500 users. Billed at 5 credits per user address. For example, 50 addresses is charged 250 credits (50 × 5).
hl_batchOpenOrders	5 per address	Batch open orders for up to 100 users. Billed at 5 credits per user address. For example, 50 addresses is charged 250 credits (50 × 5).

gRPC Streaming

gRPC provides streaming with advanced filtering capabilities. Billing is based on post-filter bytes: you are billed only for the data you actually receive after your subscription filters are applied, not the pre-filter stream volume. There is no separate per-message charge.

• Standard methods (Ping, StreamBlocks, and StreamData): 10 credits per 0.1 MB
• OrderBook methods (StreamL2Book, StreamL4Book, StreamL2BookDiff, StreamL4BookUpdates, and StreamTpslUpdates): 10 credits per 0.0165 MB
• StreamBboBook: 10 credits per 0.00165 MB

Plan Limits

These limits apply to both gRPC and WebSocket streaming - the two protocols share the same tier-based caps. Per-field filter caps are in the Streaming Limits table below.

Plan	Concurrent Streams	Named filters per stream
Free Trial	None	-
Build	5	Up to 5
Accelerate	10	Up to 10
Scale	15	Up to 25
Business	50	Up to 50
Enterprise	Custom	Custom

Streaming Limits

These limits apply equally to both WebSocket and gRPC streaming.

Plan	Concurrent Streams	Named Filters per Stream	user field max	coin field max	type field max
Free Trial	None	-	-	-	-
Build	5	5	5	5	5
Accelerate	10	10	10	10	10
Scale	15	25	25	25	20
Business	50	50	50	50	20
Enterprise	Custom	Custom	Custom	Custom	Custom

See the Filtering guide for full details.

Frequently Asked Questions

What does the free trial include for Hyperliquid?▼

The free trial includes access to HyperEVM (/evm and /nanoreth paths) and the HyperCore /info endpoint (all 73 methods, including l2Book and recentTrades).

The REST API is also available on free trial, but uses a shared URL that is not specific to your Quicknode account. See hyperliquidapi.com for details.

Not included on free trial:

• /hypercore JSON-RPC methods
• /hypercore/ws WebSocket
• HyperCore gRPC streaming

Upgrade to Build plan or higher for full HyperCore access. View pricing →

What plan do I need for /hypercore JSON-RPC and WebSocket?▼

Access to /hypercore JSON-RPC methods and /hypercore/ws WebSocket requires a Quicknode Build plan or higher.

On a free trial, attempting to connect to these endpoints will return an error indicating HyperCore access is not enabled for your account.

Upgrade your plan →

What plan do I need for HyperCore gRPC and WebSocket streaming?▼

HyperCore gRPC and WebSocket streaming both require a Quicknode Build plan or higher and use the same limit tiers. Your plan determines how many concurrent streams you can run and how many named filters each stream supports:

• Build: 5 concurrent streams, up to 5 named filters per stream
• Accelerate: 10 concurrent streams, up to 10 named filters per stream
• Scale: 15 concurrent streams, up to 25 named filters per stream
• Business: 50 concurrent streams, up to 50 named filters per stream
• Enterprise: Custom

Filter values per field are plan-tiered (see the Streaming Limits table). On the Build plan, the user, coin, and type fields each support up to 5 values.

See the Pricing page for full credit costs and stream data volume estimates.

What are the concurrent stream and filter limits for WebSocket and gRPC?▼

WebSocket and gRPC use the same limit tiers:

Plan	Concurrent streams	Named filters per stream
Build	5	5
Accelerate	10	10
Scale	15	25
Business	50	50
Enterprise	Custom	Custom

Field value limits per named filter are plan-tiered - see the Streaming Limits table above. On the Build plan, the user, coin, and type fields each support up to 5 values. Exceeding a field cap returns -32602. Exceeding the named-filter cap returns -32000.

Does hl_subscribe count against my RPS limit?▼

Yes, for the management calls. hl_subscribe and hl_unsubscribe are RPC requests and count against your plan's requests-per-second limit. If you open or close many subscriptions in a short burst, you can hit the RPS limit from those calls alone.

Data delivered through an active subscription does not count toward your RPS limit - only the management calls do.

hl_subscribe costs 0 credits. hl_unsubscribe costs 20 credits.

Does Hyperliquid's IP-based connection limit apply to Quicknode endpoints?▼

No. Hyperliquid's public WebSocket enforces a per-IP limit on simultaneous user-specific subscriptions, but this does not apply to Quicknode endpoints. Quicknode runs its own dedicated HyperCore node - your connections go directly to Quicknode's infrastructure, not Hyperliquid's public WebSocket. Your concurrency is governed only by your plan's stream limit.

Why am I getting a 422 error when calling /info methods?▼

A 422 Failed to deserialize the JSON body into the target type error on an /info request indicates that the request body could not be parsed as expected. Check that the JSON includes a valid type and the required fields for that method.

All 73 info methods are supported, including l2Book and recentTrades. See the method availability table and the linked method pages for request examples.

Why does my WebSocket connection return a 'hypercore not enabled' error?▼

This error means your Quicknode account is on the free trial plan, which does not include access to /hypercore/ws.

Upgrade to Build plan or higher to enable HyperCore WebSocket access on your endpoint. View pricing →

Is the /info endpoint available on all plans?▼

Yes, the /info endpoint is available on all plans including the free trial. All 73 info methods are supported, including l2Book and recentTrades.

See the full method availability table for the complete list.

Is the REST API available on free trial?▼

Yes, but with a limitation: on a free trial, the REST API URL is not specific to your Quicknode account. You will use a shared URL rather than your dedicated endpoint.

On a paid plan, your REST API requests route through your dedicated Quicknode endpoint. See hyperliquidapi.com for details on the shared URL, or upgrade your plan for a dedicated endpoint.

How do I upgrade my plan?▼

Visit quicknode.com/pricing to compare plans and upgrade. You can also upgrade directly from your Quicknode dashboard.

If you have questions about which plan fits your use case, reach out via Discord or contact support.

Add-ons

Hyperliquid add-ons bill separately from the credit pool. Peering is $500 per month on top of an active plan.

Hyperliquid Peering

Connect your Hyperliquid non-validating node to three dedicated, SLA-backed sentry peers with full mempool delivery

Questions

Have questions about pricing or need help estimating your usage? Contact our support team.