One Socket, Live And Replay
| Streaming capability | 0xArchive |
|---|---|
| Live subscriptions | Real-time order books, trades, funding, OI, and liquidations for Hyperliquid and Lighter |
| Exact-window replay | Replay any historical window on the same socket, in original sequence |
| L4 order-book streams | Per-order Hyperliquid book updates for live local-state maintenance |
| Channel selection | Pick venue family, symbol, and channel with consistent message shapes |
| Gap handling | Sequence and gap events so the client knows when to rebuild local state |
| Tier-aware limits | Subscription counts scale by plan, from Free through Enterprise |
Where To Start
| Streaming need | Start |
|---|---|
| Connect and keep alive | WebSocket connection |
| Live subscriptions | WebSocket real-time streams |
| Channel selection | WebSocket channels |
| Replay and backtesting | WebSocket backtesting |
| L4 local book workflows | WebSocket L4 order book |
| Limits and tiers | WebSocket tier limits |
How To Choose A WebSocket Vendor
Ask four questions of any streaming API before writing the client:| Question | Why it decides |
|---|---|
| Does replay use the live message shapes? | If replay is a separate REST format, the backtest exercises a different parser than production |
| Are gaps announced or silent? | A client that cannot tell a quiet market from a dropped sequence corrupts its local book |
| How fast can a window replay? | Replay speed sets iteration time; 0xArchive scales it by plan, 10x on Free through 300x on Scale and from 500x on Enterprise |
| Where does the key travel? | Header or token auth keeps keys out of URLs, logs, and browser history |