Use the Data Catalog when the job needs historical files instead of repeated API calls. A good export order keeps the market, venue family, schema keys, UTC range, estimate or quote, credits, delivery state, and rights decision attached to the files. The catalog uses the same venue taxonomy, schema names, freshness expectations, and market identifiers as the API docs. Choose the market and schema here, then use REST or WebSocket when the product needs programmatic calls instead of file delivery. The Data Catalog checkout is a browser product flow. Build API clients against the public OpenAPI market-data routes; treat checkout calls that are not present in OpenAPI as product implementation details.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.
Public Surface Boundary
The indexed public entrypoint ishttps://www.0xarchive.io/data. Use it as the citation URL for the Data Catalog workflow unless a deeper route has its own public title, canonical URL, and index policy.
Treat /data/catalog as a public catalog route because the live page exposes route-specific public metadata for the catalog. Treat /data/categories/:categorySlug, /data/markets/:venueSlug/:marketSlug, and /dashboard/exports/:id as product navigation or product-state routes unless their route-specific metadata is visible on the public website.
Machine-readable symbol discovery comes from https://api.0xarchive.io/v1/symbols. The response is an object with a top-level symbols array. Use each row’s exchange, symbol, slug, data_types, and coverage fields when building market pickers or export packets. Do not use website-local API-shaped paths such as /api/v1/*/symbols as symbol feeds; those paths belong to the website shell, not the public market-data API.
The symbols feed is live product catalog data, but it is not part of the generated OpenAPI REST reference. Use it for catalog discovery and route selection. Use the OpenAPI bundle for programmatic market-data calls.
Market slugs are generated from venue plus symbol state, so docs and agents should not invent market-detail URLs from plain symbols. Start from the Data explorer, the catalog UI, the symbol feed row, or the frontend route builder when a precise market URL is required. HIP-4 BTC daily outcomes use /data/markets/hip4/btc-daily-outcomes instead of an ordinary generated category entry.
Symbols Feed Contract
The live feed currently returns rows forhyperliquid, spot, hip3, hip4, and lighter. Every row carries exchange, symbol, data_types, coverage_from, coverage_by_type, and size_per_day. Some rows also carry state or display fields:
| Field | Use |
|---|---|
coverage_by_type | Choose the earliest valid date for each selected schema. Use the schema coverage key, such as orderbook, l3_orderbook, l4_orderbook, l4_orders, trades, funding, oi, or liquidations. |
size_per_day | Estimate export size before checkout. Server quotes can replace client estimates after authentication. |
coverage_to | Cap settled-market export end dates. Live markets without coverage_to default the end date to today. |
slug, display_title, outcome_pair, is_settled | Preserve HIP-4 outcome context for BTC daily outcome exports. |
is_active | Show active or delisted state without hiding historical archives. |
Route Slugs
Frontend market routes use venue slugs, not raw exchange labels, in/data/markets/:venueSlug/:marketSlug.
Feed exchange | Route venue slug | Notes |
|---|---|---|
hyperliquid | hyperliquid | Core Hyperliquid perps |
spot | hyperliquid-spot | Hyperliquid Spot pair exports |
hip3 | hip3 | Builder-prefixed symbols such as km:US500 |
hip4 | hip4 | BTC daily outcomes use a special route, not a generated market slug |
lighter | lighter | Lighter.xyz markets |
symbol alone.
Product Routes
| Website route | User intent | Docs support |
|---|---|---|
/data | Start an export order by choosing a market, schemas, and date range | Indexed public entrypoint for this workflow; use this page with Export Schemas and Data Rights |
/data/catalog | Browse all exportable markets | Public catalog route with route-specific public metadata; use /data plus Data Availability and Markets when the job needs product framing instead of catalog navigation |
/data/categories/:categorySlug | Browse a curated market group | Product navigation route; use category slugs below with Data and Venue Coverage for public docs context |
/data/markets/:venueSlug/:marketSlug | Configure one market export | Product navigation route with generated market slugs; use Export Schemas, Export Checkout, and Data Rights |
/dashboard/exports/:id | Review an authenticated export job | Product-state route for status, download links, file format, and support context |
Export Order Packet
Use this packet before a Data Catalog order becomes a purchase, support ticket, warehouse load, or shared research artifact.| Field | Preserve it because… |
|---|---|
| Market and venue family | Hyperliquid core, Spot, HIP-3, HIP-4, and Lighter use different symbol and coverage rules. |
| Symbol-feed row | Preserve exchange, symbol, slug, data_types, and coverage fields from /v1/symbols when they are present. |
| Schema keys | l2_orderbook, l3_orderbook, l4_orderbook, l4_orders, trades, funding, oi, and liquidations produce different files. |
| UTC date range | Coverage, estimates, checkout, and reproducibility depend on the selected start and end dates. |
| Estimate or quote | Size, rows, price, and credit application explain what the buyer accepted. |
| Checkout result | Credit-covered, Stripe-paid, and partially credit-covered orders should be distinguishable later. |
| Delivery state | Dashboard status, file format, download links, and support identifiers explain readiness. |
| Data-rights decision | Public raw downloads, customer feeds, resale, and partner delivery need review before shipping. |
Export Flow
Choose the market
The catalog separates Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, and Lighter markets. Market URLs should preserve venue family and symbol shape.
Choose schemas
Schema options depend on the selected market. L2, L3, L4, trades, funding, OI, liquidations, and order-event history are not interchangeable.
Choose a UTC date range
Ranges are bounded by coverage. Settled HIP-4 outcomes can have an end date; live markets usually use today as the default end.
Review estimate and credits
The browser product shows estimated size, rows, price, and subscriber-credit context before checkout. Authenticated users can see credits applied before any card charge.
Category Slugs
| Category | Website slug | Use |
|---|---|---|
| Popular exports | popular-exports | High-intent starter markets across equities, crypto majors, macro, and outcomes |
| Popular equities | popular-equities | Equity-style HIP-3 and Spot export starts |
| Crypto majors | crypto-majors | Major crypto markets with Hyperliquid-family coverage |
| Commodities | commodities | Oil, metals, and macro commodity markets |
| Indices and FX | indices-fx | Index, currency, and cross-market research starts |
| Pre-IPO markets | pre-ipo-markets | Private-company market history surfaced through supported venues |
| HIP-4 BTC outcomes | hip4-btc-outcomes | Rolling BTC daily outcome series; the special market route is /data/markets/hip4/btc-daily-outcomes |
| Hyperliquid crypto | hyperliquid-crypto | Long-tail Hyperliquid-family crypto markets |
| Lighter crypto | lighter-crypto | Lighter-specific crypto market exports |
Related Pages
Export Schemas
Schema labels, data types, rough columns, pricing units, and coverage keys.
Export Checkout
Quote, credits, checkout, login return, and dashboard job behavior.
Data Rights
Decide whether an export is internal use, derived use, or redistribution.
Markets
Bridge chart-first pages, catalog routes, and API route families.