Plan Access Summary

Feature	免費試用	Build+	註釋
HyperEVM (/evm)	✓	✓	Available on all plans
Debug & Trace (/nanoreth)	✓	✓	Available on all plans
HyperCore /info endpoint	✓	✓	50 of 52 methods; 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 →

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
免費試用	無	-	-	-	-
建置	5	5	100	25	20
加速	10	10	10	10	10
比例	15	25	25	25	20
商業	50	50	50	50	20
企業	自訂	自訂	自訂	自訂	自訂

See the Filtering guide for full details.

常見問題

What does the free trial include for Hyperliquid?▼

The free trial includes access to HyperEVM (/evm 以及 /nanoreth paths) and the HyperCore /info endpoint (50 of 52 methods natively available).

該 REST API is also available on free trial, but uses a shared URL that is not specific to your Quicknode account. See hyperliquidapi.com 詳情請參閱。

Not included on free trial:

• /hypercore JSON-RPC 方法
• /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), with the exception that the Build plan uses the server hard caps for user (100) and coin (25). The type field is capped at 20 for all paid plans.

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	並行流	Named filters per stream
建置	5	5
加速	10	10
比例	15	25
商業	50	50
企業	自訂	自訂

Field value limits per named filter are plan-tiered - see the Streaming Limits table above. The Build plan uses the server hard caps for user (100) and coin (25). The type field is capped at 20 for all paid plans. 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 以及 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 means the method you are calling is not available through Quicknode's /info endpoint.

Quicknode supports 50 of 52 info methods natively. For l2Book 以及 recentTrades, Quicknode offers purpose-built gRPC alternatives: StreamL2Book delivers full order book snapshots up to 100 price levels deep every block, and StreamData (TRADES stream) provides real-time trade data with lower latency.

Check the Method Availability table to confirm which method you are calling and see recommended alternatives.

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. 50 of the 52 info methods are natively supported. For l2Book 以及 recentTrades, Quicknode offers purpose-built gRPC alternatives with better performance (StreamL2Book up to 100 price levels deep, StreamData TRADES stream).

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.