A price your bot can act on, in one command.

Simple, reliable price and trade feeds that integrate in minutes, drop-in compatible with the stubs you already generated.

Your problem

The parts you keep working around.

01

You need a price that moves, not a 400-field firehose to parse first.

02

Provider migrations usually mean rewriting the client layer.

03

Polling REST for prices burns rate limits and still lags.

The proof

The tape, without the parse.

Coin, price, size, pushed sub-second over gRPC. This is the compact view; the full stream adds notional, maker/taker role, and the trader's wallet when you want them.

StreamSwaps · BTC

replay

BTCsell 67002.00.07995
BTCbuy 67002.00.07782
BTCbuy 67002.00.01395
BTCbuy 67002.00.12389
BTCbuy 67001.00.04205
BTCbuy 66999.00.09828
BTCbuy 66999.00.07279
BTCsell 67000.00.06172
BTCsell 67001.00.03489
BTCbuy 67001.00.05221

Simulated trades in the StreamSwaps format, capped at the UI render rate. The wire pushes every fill.

Integration sketch

First price in one command.

grpcurl against the public endpoint with your key. When the bot outgrows the shell, generate stubs in any language via reflection. No SDK lock-in, and QuickNode/Dwellir stubs keep working.

Read the docs
# A BTC price feed in one commandgrpcurl -H 'x-api-key: YOUR_KEY' \  stream.hyperliquidrpc.com:443 \  hyperliquid_btc_price.v1.BtcPriceStreaming/StreamBtcPrices # Or live BTC trades, filtered server-sidegrpcurl -H 'x-api-key: YOUR_KEY' \  -d '{"market_type":"ALL","coins":["BTC"]}' \  stream.hyperliquidrpc.com:443 \  hyperliquid_swaps.v1.SwapStreaming/StreamSwaps
Where to start

The plan that fits.

Pro

$49/moRecommended

Every stream, production rate limits.

Pro carries every stream a bot needs (price tickers, trades, the L2 book) at production rate limits, from $49/mo.

Compare both plans

First message in minutes.

Pro covers every feed a bot needs (price ticker, trades, and the book) at production rate limits.