Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt

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

Funding, open interest, and candles are compact series, but they still need venue family, symbol, coverage, and timestamp discipline. Do not assume one family supports all three for every market, and do not treat current values, historical pages, and candle intervals as interchangeable records.

Route Families

NeedStart with
Hyperliquid core candles/v1/hyperliquid/candles/{symbol}
Hyperliquid core funding/v1/hyperliquid/funding/{symbol} and /current
Hyperliquid core OI/v1/hyperliquid/openinterest/{symbol} and /current
Hyperliquid Spot candles/v1/hyperliquid/spot/candles/{symbol}
HIP-3 candles/v1/hyperliquid/hip3/candles/{symbol}
HIP-3 funding/v1/hyperliquid/hip3/funding/{symbol} and /current
HIP-3 OI/v1/hyperliquid/hip3/openinterest/{symbol} and /current
HIP-4 candles/v1/hyperliquid/hip4/candles/{symbol}
HIP-4 OI/v1/hyperliquid/hip4/openinterest/{symbol} and /current
Lighter candles/v1/lighter/candles/{symbol}
Lighter funding/v1/lighter/funding/{symbol} and /current
Lighter OI/v1/lighter/openinterest/{symbol} and /current

Field Rules

Funding rates, premiums, open interest, mark prices, oracle prices, and candle values should be handled with decimal-safe parsing when precision matters. HIP-4 price fields are probability-like. Store venue family and symbol with every series so downstream joins do not mix core perps, Spot, HIP-3, HIP-4, and Lighter. For dashboards and backtests, store the route path and interval next to the value. A candle interval, current funding record, and historical funding page can share symbol text while carrying different time semantics.

Workflow

1

Choose the series

Decide whether the job needs funding, current funding, OI, current OI, or candles.
2

Probe one window

Pull one symbol and small window before widening across markets or history.
3

Check freshness and incidents

Use data-quality routes before the series feeds alerts, dashboards, backtests, exports, or models.
4

Store time semantics

Keep route, interval, timestamp, window, request ID, and data-quality decision with output.

Evaluation Fit

These routes are usually the first place a research workflow leaves raw events and enters feature engineering. Keep the series easy to review: decimal-safe parsing, explicit interval labels, no silent backfills, and a stored data-quality result for the window.

Next Step

Use Historical Market Data for long windows, Point-In-Time Backtesting for model-safe joins, Example Responses for payload shapes, or Data Quality before alerts and dashboards.
Last modified on May 20, 2026