Plan Access Summary

Feature	Free Trial	Build+	Notes
HyperEVM (/evm)	✓	✓	Available on all plans
Debug & Trace (/nanoreth)	✓	✓	Available on all plans
HyperCore /info endpoint	✓	✓	30 of 52 methods; see method table below
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
Free Trial	None	-	-	-	-
Build	1	5	100	25	20
Accelerate	5	10	10	10	10
Scale	10	25	25	25	20
Business	25	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 (30 of 52 methods natively available).

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: 1 concurrent stream, up to 5 named filters per stream
• Accelerate: 5 concurrent streams, up to 10 named filters per stream
• Scale: 10 concurrent streams, up to 25 named filters per stream
• Business: 25 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	Concurrent streams	Named filters per stream
Build	1	5
Accelerate	5	10
Scale	10	25
Business	25	50
Enterprise	Custom	Custom

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 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 means the method you are calling is not available through Quicknode's /info endpoint.

Quicknode proxies the open-source HyperCore node, which supports 30 of 52 info methods natively. The remaining 22 require Hyperliquid Foundation indexer data that is not part of the open-source node.

Check the Method Availability table to see which methods are supported and what alternatives are available (public HL API or SQL Explorer) for unsupported ones.

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. However, only 30 of the 52 info methods are natively supported. The other 22 return a 422 error regardless of your plan, because they require Hyperliquid Foundation indexer data that is not part of the open-source node.

See the full method availability table for the complete list and alternatives.

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.