Representative coverage
This cross-section comes from the public Catalog at2026-08-27T20:33:10.112Z. It is representative, not exhaustive. Use
Catalog for current coverage and exact market IDs.
Venue IDs are not interchangeable. For example, Lighter uses numeric market IDs,
while other venues expose asset or pair-like identifiers. Always use the exact
market value returned by Catalog.
Choose a client method
Choose the narrowest typed method for the series you need. Use
events or
replay when event interleaving and stored order matter more than a single
derived dataset.
Set one bounded analysis range
Use one Catalog row and one time window across the following recipes. This makes the resulting series easier to compare.Compare carry and mark price
Funding and mark-price rows are point series. DataFrame output gives you flat, timezone-aware columns for alignment and resampling.funding_rate and funding_interval together instead of assuming every rate
uses the same period.
Analyze trade flow
Use raw trades for signed flow and interval methods for price, participation, benchmark, and realized-volatility series.extra.<name>. Use the
normalized trade fields for cross-venue comparisons.
Measure liquidity
Use BBO for top-of-book spreads anddepth_metrics for depth, imbalance, and
slippage estimates. Both support DataFrame output.
Choose an order-book workflow
l2_snapshots reconstructs complete books for you. Use it when you want to
inspect or sample full state:
l2_updates returns raw standardized snapshots and deltas. Feed them into
OrderbookBuilder when your application controls when complete books are
materialized:
Related documentation
- Funding rates and Mark prices for carry and reference-price fields
- Trades, OHLCV, Volume, VWAP, and Volatility for trade-flow analysis
- BBO and Depth metrics for derived liquidity fields
- L2 snapshots and updates for reconstruction behavior
- Event envelope for timestamps and stored ordering