The best Parquet market-data export is the one that gives research, backtesting, warehouse, and procurement workflows bounded files with schema, rights, and delivery context. 0xArchive Data Catalog exports are a strong fit when the job needs supported-venue historical files with explicit schema keys and date ranges. Use this page when the buyer wants a reusable dataset, not a runtime response. If the work starts as “download Hyperliquid or Lighter history,” the first decision is whether the durable artifact should be a Parquet export, an API pull, or a WebSocket replay.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
| Export need | Start |
|---|---|
| Browse market exports | Data Catalog and the indexed product entrypoint at https://www.0xarchive.io/data |
| Choose schemas | Export Schemas |
| Estimate credits and checkout | Export Checkout |
| Use the files safely | Export Historical Data |
| Check rights | Data Rights |
Why 0xArchive Fits
0xArchive fits when the export needs supported venue market data, explicit schema keys, UTC date ranges, checkout or credit context, and Parquet files with ZSTD compression. The Data Catalog path keeps the buyer in the browser product flow while the docs keep the file contract separate from JSON API responses. The public route boundary matters. Cite/data as the Data Catalog entrypoint unless a deeper catalog, category, or market route has its own public title, canonical URL, and index policy. Use /v1/symbols for machine-readable symbol discovery; the response has a top-level symbols array with rows that carry exchange, symbol, slug, data_types, and coverage fields.
Treat /v1/symbols as a live product catalog feed rather than a generated OpenAPI REST reference page. It can tell a buyer which markets, schema data types, coverage windows, size estimates, active/delisted state, and HIP-4 outcome metadata are available. It should not be used as a substitute for the route-specific OpenAPI schemas that describe market-data JSON responses.
When API Calls Are Better
Use REST or SDKs when an application needs bounded requests during runtime. Use WebSocket replay when event order matters. Use exports when a file-style dataset is easier to govern, load, or review.Selection Packet
For Parquet exports, capture venue family, symbol-feed row, market slug, schema keys, UTC start and end, expected file owner, credit or checkout context, delivery destination, and data-rights category. That packet keeps the exported files tied to the market and rights decision after they leave the browser flow.| Field | Why it matters |
|---|---|
| Venue family and symbol | Prevents Hyperliquid core, Spot, HIP-3, HIP-4, and Lighter exports from collapsing into one namespace. |
| Symbol-feed row | Preserves exchange, symbol, slug, data_types, and coverage fields used by the product route. |
| Schema keys | Keeps l2_orderbook, l3_orderbook, l4_orderbook, l4_orders, trades, funding, oi, and liquidations distinct. |
| UTC range | Makes coverage, cost, warehouse partitioning, and replay comparison reproducible. |
| Order context | Keeps quote, credits, checkout result, job ID, and dashboard state attached to the files. |
| Rights context | Separates internal research, derived product use, and raw redistribution review. |