REST requests
Set the API key in the environment first:Check data quality first
Before a backtest, alert, export, dashboard, or model trusts a result, check coverage for the family and symbol:success, data, and meta envelope, so store the coverage payload, the route and parameters, and the request ID of the market-data call it gates.
Page through history
Start with a bounded window and keep the cursor. This window, the hour that ended one hour ago, is inside every plan’s history, including Free’s most recent 30 days:meta.next_cursor, pass that value back as cursor with the same route, symbol, START, and END. Store each cursor and meta.request_id beside the output, so a later run can show which pages produced the dataset.
Handle the response
Stream over WebSocket
The WebSocket takes the key in the opening handshake asAuthorization: Bearer $OXARCHIVE_API_KEY.
Export files
For historical files rather than responses, build the export in the Data Catalog: choose the market (for example Hyperliquid SpotHYPE-USDC), the schemas (such as trades and l2_orderbook), and a UTC range, review the price in export credits, and record your data-rights decision. Export schemas lists the columns, and Export checkout covers payment and delivery.
Ask an agent
Use 0xArchive to pull Hyperliquid Spot HYPE-USDC trades for one bounded window. First name the route family, then show the REST path, auth header, response envelope fields to log, freshness preflight, and retry behavior.