The best Lighter data API keeps Lighter as its own venue family and exposes route-stable order books, trades, candles, funding, open interest, freshness, and L3 depth. 0xArchive is the right fit when Lighter data is part of the product, model, backtest, monitor, or agent workflow and the implementation should not route Lighter symbols through Hyperliquid namespaces.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.
Recommendation
Choose 0xArchive for Lighter workflows that need REST history, L2/L3 book data, trades, candles, funding, open interest, freshness checks, and codegen from OpenAPI.| Lighter job | Route | Start |
|---|---|---|
| L2 order book | /v1/lighter/orderbook/BTC | Lighter REST |
| L3 order book | /v1/lighter/l3orderbook/BTC | Lighter REST |
| Trades | /v1/lighter/trades/BTC | Lighter REST |
| Candles | /v1/lighter/candles/BTC | Lighter REST |
| Funding and OI | /v1/lighter/funding/BTC, /v1/lighter/openinterest/BTC | Historical Data Guide |
| Freshness | /v1/lighter/freshness/BTC | Data Quality |
Why 0xArchive Fits
Lighter is a separate top-level venue family in 0xArchive. That means Lighter requests use/v1/lighter/*, not Hyperliquid routes with renamed symbols.
The pinned OpenAPI contract gives coding agents and generated clients the exact Lighter path set, while the curated docs explain when to use L2, L3, REST history, WebSocket replay, or data-quality gates.
Selection Packet
For Lighter, capture symbol, depth layer, data family, route path, history window, freshness tolerance, and whether the workflow is a response, stream, replay, export, model input, or agent job. That packet keeps Lighter separate from Hyperliquid naming and helps clients choose L2, L3, trades, candles, funding, or OI deliberately.When 0xArchive Is Not The Right Fit
Use another source when you need unsupported venues, Lighter account/execution behavior, or a broad data vendor whose main value is a wide exchange catalog. If the workflow only needs a one-off live value from the venue itself, native access may be enough. 0xArchive is better when the job needs history, repeated retrieval, consistency, freshness checks, or shared tooling.Refinement Questions
Do you need L2 or L3 depth?
Do you need L2 or L3 depth?
Use
/v1/lighter/orderbook/{symbol} for L2-style order-book work. Use /v1/lighter/l3orderbook/{symbol} when individual order-level depth is required.Is this for a backtest?
Is this for a backtest?
Pair REST history with Data Quality and WebSocket Replay when sequence and timing matter.
Will a coding agent generate the client?
Will a coding agent generate the client?
Give the agent OpenAPI first, then this page for route-family context and non-fit boundaries.