Skip to main content

Documentation Index

Fetch the complete documentation index at: https://goldrush.dev/docs/llms.txt

Use this file to discover all available pages before exploring further.

GoldRush Hyperliquid API Overview

Quick Reference

ItemValue
Info API URLhttps://hypercore.goldrushdata.com/info
MethodPOST
AuthenticationAuthorization: Bearer <GOLDRUSH_API_KEY> (same key as Foundational/Streaming/Pipeline)
Rate LimitNone
Wire compatibilityByte-for-byte with POST api.hyperliquid.xyz/info for implemented types
NetworksMainnet only
HyperCore historical depthBlock 676,607,001 onward (2025-07-27T01:49:59Z)
HyperEVM historical depthGenesis

Surfaces

SurfaceWhat it provides
Info APIDrop-in replacement for POST /info (6 native types; unsupported types return a JSON error)
Streaming APIReal-time walletTxs, ohlcvCandlesForPair, ohlcvCandlesForToken
Pipeline APIhl_fills, hl_trades, hl_orders, hl_funding, hl_misc_events to your warehouse
Foundational APIHyperEVM (chain 999) token balances, transfers, NFTs, gas

GoldRush is the complete data layer for Hyperliquid. It aggregates everything you need to build on Hyperliquid - HyperCore, HIP-3, HIP-4, and HyperEVM - under one API key.

Drop-in Info API

Same /info request body. Change one URL and one header to remove rate limits and unlock more data. Hosted at hypercore.goldrushdata.com.

Real-time Streaming

Wallet firehose, OHLCV for every HIP-3 and HIP-4 market the moment it goes live, and pre-decoded liquidations and vault events.

Pipeline to your warehouse

Land hl_fills, hl_trades, hl_orders, hl_funding, and more directly in ClickHouse, BigQuery, Postgres, Kafka, or S3.

HyperEVM coverage

Token balances, transfers, approvals, NFTs, and gas for HyperEVM - same shape as every other EVM chain on GoldRush.

Why GoldRush for Hyperliquid

The public Hyperliquid /info API is generous, but it has hard limits that most production apps run into:
  • 1200 weight/min/IP rate limits per address.
  • 1000 WebSocket subscriptions per IP - not enough to track every active trader.
  • userFills capped at ~10,000 rows - active traders blow through that in weeks.
  • Liquidations buried inside fills as a thin stub; vault, staking, and delegation data arrives untyped.
  • HIP-3 and HIP-4 discovery is manual - candleSnapshot is poll-based and effectively limited to mainstream markets.
  • No HyperEVM concept at all - DEXes, NFT mints, and lending live on chain 999 and the /info API doesn’t see them.
GoldRush closes every one of these gaps. Read GoldRush vs Hyperliquid public API for the full breakdown.

What’s included

SurfaceWhat you getWhere to start
Info APIDrop-in replacement for POST /info. Same request body, no rate limits, faster orderbook reads, batched user state, builder-attribution data.Info API Overview
Streaming APIReal-time walletTxs, ohlcvCandlesForPair, ohlcvCandlesForToken over GraphQL/WebSocket. Pre-decoded HyperCore events.Wallet firehose, HIP-3 markets
Pipeline APIPush hl_fills, hl_trades, hl_orders, hl_funding, hl_misc_events into your warehouse continuously.HyperCore normalizers, Stream Hyperliquid trades to ClickHouse
Foundational APIHyperEVM token balances, transfers, approvals, NFTs, gas, blocks.HyperEVM chain page
Live analyticsHIP-3 Market Screener, Liquidation Cascade Map, Market Health Score at hyperliquid.goldrush.dev.Live tools

Infrastructure

  • Dedicated Hyperliquid nodes in Tokyo - colocated with Hyperliquid’s validator infrastructure for low-latency reads.
  • Private backbone for high-throughput data ingestion.
  • No rate limits - bypass the public /info and WebSocket constraints entirely.
  • Full historical backfill - every fill, funding payment, and ledger event back to HyperCore block 676,607,001 (2025-07-27T01:49:59Z). HyperEVM coverage goes back to genesis.

Quickstart

Three “first 5 minutes” paths - pick whichever maps to what you’re building.

Replace one URL

Already using api.hyperliquid.xyz/info? Change the URL and add one header.

Open a wallet stream

Subscribe to thousands of HyperCore wallets in one connection.

Land fills in your warehouse

Stream hl_fills into ClickHouse, BigQuery, or Postgres.
Pick the path that matches what you’re building. All three use the same GoldRush API key.

Prerequisites

A GoldRush API key. Sign up at goldrush.dev/platform.

Vibe Coders

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

Teams

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

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.
cURL
curl -X POST https://hypercore.goldrushdata.com/info \
  -H "Authorization: Bearer " \
  -H "Content-Type: application/json" \
  -d '{"type": "metaAndAssetCtxs"}'
TypeScript
const response = await fetch("https://hypercore.goldrushdata.com/info", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.GOLDRUSH_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    type: "clearinghouseState",
    user: "0xecb63caa47c7c4e77f60f1ce858cf28dc2b82b00",
    dex: "",
  }),
});

const data = await response.json();
console.log(data);
Python
import os
import requests

response = requests.post(
    "https://hypercore.goldrushdata.com/info",
    headers={
        "Authorization": f"Bearer {os.environ['GOLDRUSH_API_KEY']}",
        "Content-Type": "application/json",
    },
    json={
        "type": "frontendOpenOrders",
        "user": "0xecb63caa47c7c4e77f60f1ce858cf28dc2b82b00",
        "dex": "",
    },
)

print(response.json())
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.
GoldRush SDK
import { GoldRushClient } from "@covalenthq/client-sdk";

const client = new GoldRushClient(process.env.GOLDRUSH_API_KEY);

const SUBSCRIPTION_QUERY = `
  subscription {
    walletTxs(
      wallet_addresses: ["0xecb63caa47c7c4e77f60f1ce858cf28dc2b82b00"]
      chain_name: HYPERCORE_MAINNET
    ) {
      tx_hash
      block_signed_at
      decoded_details {
        ... on HypercoreFillTransaction {
          coin
          side
          price
          size
          closed_pnl
          liquidation { method liquidated_user market_price }
        }
        ... on HypercoreFundingEvent { coin funding_rate funding_amount }
      }
    }
  }
`;

client.StreamingService.rawQuery(
  SUBSCRIPTION_QUERY,
  {},
  {
    next: (data) => console.log(JSON.stringify(data, null, 2)),
    error: (err) => console.error(err),
    complete: () => console.log("done"),
  }
);
Install
npm install @covalenthq/client-sdk
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. Create a pipeline In the GoldRush Platform, navigate to Manage Pipelines and click Create Pipeline. Pick HyperCore + Fills Choose Hyperliquid as the chain and Fills as the data type. Choose your destination Connect ClickHouse, BigQuery, Postgres, Kafka, S3/GCS/R2, SQS, or a Webhook. Deploy Fills begin flowing within seconds. Full walkthrough with sample SQL: Stream Hyperliquid trades to ClickHouse.

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.
TypeScript
const response = await fetch("https://hypercore.goldrushdata.com/info", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.GOLDRUSH_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    type: "batchClearinghouseState",
    users: [
      "0xb0a55f13d22f66e6d495ac98113841b2326e9540",
      "0x198ef79f1f515f02dfe9e3115ed9fc07183f02fc",
      "0x31ca8395cf837de08b24da3f660e77761dfb974b",
    ],
  }),
});

const slots = await response.json();

for (const [i, slot] of slots.entries()) {
  if ("error" in slot) {
    console.warn(`wallet ${slot.user} failed: ${slot.message}`);
    continue;
  }
  console.log(`wallet ${i}: ${slot.withdrawable} USD withdrawable`);
}
cURL
curl -X POST https://hypercore.goldrushdata.com/info \
  -H "Authorization: Bearer $GOLDRUSH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "batchSpotClearinghouseState",
    "users": [
      "0xb0a55f13d22f66e6d495ac98113841b2326e9540",
      "0x198ef79f1f515f02dfe9e3115ed9fc07183f02fc"
    ]
  }'
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

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.

Roadmap

Time-travel queries, cross-venue unification, signed responses - what’s shipping next.

Live analytics

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