Data products live

Hyperliquid trader + market data

Hyperliquid data
built for decisions.

Build trading, research, and market-intelligence products with live public positions, margin state, liquidation levels, L2/L4 depth, fills, funding, and trader context from the same maintained path that powers Omni Terminal.

Request data access Read the data product docs
Positions + marginLive public trader state and leverage context
LiquidationsLevels and stress views derived from available state
L2 + L4 depthAggregated and order-level market structure
REST + streamsHistorical, snapshot, and live delivery contracts
01

Trader state that connects

Bring positions, leverage, margin use, funding, fills, and activity into the same investigation workflow.

  • Public-wallet positions and margin state support global and profile views.
  • Fill identity and activity context connect market events to observable trader behavior.
  • Wallet-cluster and trader-profile outputs can enrich research and product workflows.
02

Depth beyond a top-of-book quote

Use the maintained orderbook path for market-structure views that need more than a generic ticker endpoint.

  • L2 depth supports price-level liquidity and imbalance views.
  • L4 order-level depth supports queue, identity, and liquidity investigation.
  • Trades, fills, BBO, and TWAP contracts stay aligned with downstream analytics.
03

Derived risk with boundaries

Liquidation and margin-stress outputs are documented analytical views, with the source path and limitations kept explicit.

  • Liquidation levels are tied to observable position and margin state.
  • Historical and live infrastructure supports both snapshots and streaming workflows.
  • Public documentation distinguishes analytical estimates from guaranteed execution outcomes.
OWNED DELIVERY PATH

One source path from node to customer surface.

The API is not a disconnected resale layer. Omni’s node, orderbook, stream processing, derived analytics, and terminal share documented contracts so customer data products stay aligned with the live trading surface.

Inspect the technical evidence
  1. 01
    Owned node + orderbook path

    Observable upstream state and market-depth reconstruction.

  2. 02
    Normalization + fanout

    Stable stream contracts decouple consumers from node internals.

  3. 03
    Historical + derived storage

    ClickHouse, Kafka, and consumers support live and historical views.

  4. 04
    Customer delivery

    REST, WebSocket, shared fanout, or dedicated service models.

Hyperliquid trader + market data

Build on the maintained path.
Keep your team focused on the product.

Request data access Explore managed nodes