Skip to main content
Pick the path that matches what you’re building. All four use the same GoldRush API key.

Prerequisites

A GoldRush API key. Sign up at goldrush.dev/platform, or apply to the Early Builders Program for free credits.

Vibe Coders

$10/mo - Built for solo builders and AI-native workflows.

Teams

$250/mo - Production-grade with priority support.

Early Builders

Pre-revenue? Up to 1M credits over 12 months, free.

1. Drop-in Info API

If your code already calls POST https://api.hyperliquid.xyz/info, swap the URL to https://hypercore.goldrushdata.com/info and add an Authorization: Bearer header. The request body and response shape stay byte-for-byte identical.
That’s it. No rate limits, faster reads, and the response is byte-equal to Hyperliquid (modulo live-value drift). See the full migration guide for SDK overrides and behavioral notes:

Info API Migration Guide

Side-by-side examples in JS, Python, and cURL - including how to point existing SDKs at GoldRush.

2. Stream wallet activity

Subscribe to one or many HyperCore wallets in real time over WebSocket. Pre-decoded events include fills with liquidation context, funding payments, vault actions, and 20+ ledger subtypes.
The walletTxs subscription has zero rate limits and scales to thousands of concurrent wallet subscriptions per connection. See Wallet firehose for the full pattern.

3. Pipe fills to your warehouse

Stream HyperCore fills into ClickHouse, BigQuery, Postgres, Kafka, or S3 with one config - no ETL on your side.
1

Create a pipeline

In the GoldRush Platform, navigate to Manage Pipelines and click Create Pipeline.
2

Pick HyperCore + Fills

Choose Hyperliquid as the chain and Fills as the data type.
3

Choose your destination

Connect ClickHouse, BigQuery, Postgres, Kafka, S3/GCS/R2, SQS, or a Webhook.
4

Deploy

Fills begin flowing within seconds.

4. Fan out across many wallets

Need account state for many wallets at once? batchClearinghouseState and batchSpotClearinghouseState accept 1 to 50 wallets per call and fan them out in parallel against our private node. There is no equivalent on the public Hyperliquid /info API. Each slot in the response is either the raw upstream object for that wallet (success) or a thin error envelope ({error, user, message}) when an individual wallet fails. The HTTP status stays 200 OK even on partial failure - always check for the error key on each slot.
Duplicates in users are removed (case-insensitive); input order is preserved for the survivors. For batches larger than 50, issue multiple calls. Use cases: portfolio dashboards, multi-wallet PnL aggregators, fleet-level liquidation risk monitoring, treasury balance reconciliation. Full reference: batchClearinghouseState, batchSpotClearinghouseState.

What’s next

WebSocket API

Drop-in wss:// replacement with l2Book, l2BookDiff, and the GoldRush-native l4Book order-level stream. No per-IP subscription cap.

HIP-3 markets

Real-time OHLCV for every builder-deployed perp market - equities, commodities, niche assets.

Liquidations & vault events

Pre-decoded LedgerLiquidation, LedgerVaultDeposit, LedgerVaultWithdraw, and 17 more subtypes.

Live analytics

HIP-3 Market Screener, Liquidation Cascade Map, Market Health Score.