Skip to main content

AlphaQuick market data

AlphaQuick streams real-time Hyperliquid market data over a low-latency WebSocket relay: deeper order books and faster updates than the public exchange feed, delivered to many clients from a single upstream connection.

  • Endpoint: wss://feed.alphaquick.io/ws
  • Data: order-book depth (top-of-book up to 200 levels, or the full book) and trades
  • Auth: a bearer API key for bots/servers; a short-lived ticket for the browser
  • Access: an active Hyperliquid Live subscription

Why a relay?​

Connecting every bot and browser directly to the exchange does not scale — each connection competes for the exchange's per-IP limits, pays full network latency, and re-downloads the same book. The relay solves this with fan-out: it holds one upstream connection and broadcasts a normalized, deduplicated stream to every subscriber.

   your bot ─────▶ feed.alphaquick.io ─┐
   your bot ─────▶ feed.alphaquick.io ─┤ fan-out   ┌────────────┐
   browser  ─────▶ feed.alphaquick.io ─┴──▶ ONE ──▶│ HL upstream │
                                          upstream  └────────────┘

Because the relay is the only thing talking to the exchange, adding clients never multiplies exchange connections, and every client sees the same low-latency book.

Two ways to connect​

ForAuthGuide
API keybots, servers, backtestersAuthorization: Bearer aqk_… headerAPI keys
Browser demothe in-app Depth Comparisonshort-lived ticket (handled for you)Demo feed

A browser WebSocket cannot send an Authorization header, so browser sessions use a short-lived ticket instead. Server-side clients use the API-key header — see the guides.

Next steps​