HYPE-USDC in their own route family, never folded into core perp symbols or generic asset-price feeds.
One key returns pair discovery, order books, trades, TWAP, and full order-level (L4) depth as normalized JSON, with named fields and a request ID on every response. Spot trades go back to March 2025; native L2 and TWAP since May 2026; order-level (L4) depth since March 2026.
What One Key Returns
How To Choose A Spot Data API
Four questions separate the candidates faster than any feature list:
A vendor that folds Spot into a generic asset-price feed fails the first question, and everything downstream of it, before price or coverage even comes up.
When To Use 0xArchive
Spot workflows break when pair semantics get treated like core perp symbols. 0xArchive keepsHYPE-USDC attached to Spot-specific routes and schemas all the way downstream: route-stable REST, OpenAPI for generated clients, examples, per-pair freshness, and Parquet exports for the same window. The order books, trades, TWAP, and L4 depth come back normalized, live or historical, every response carrying a request ID and a data-quality path you can check before a backtest trusts the data. Every route, market family, and schema is available on every tier, including Free, and agents reach the same pairs through the hosted MCP server at https://mcp.0xarchive.io/mcp. Every Spot trade, order book, and fill. One API. 0xArchive is not the right fit when the pairs you need trade on a centralized exchange or a venue other than Hyperliquid and Lighter.
Check This Yourself
Three requests answer the table above against the live API. List the pairs and their coverage fields:Next Step
Start with Hyperliquid Spot REST, keep the pair symbol such asHYPE-USDC, then attach Data quality before turning the result into a model input, export, or agent call. For full order-level depth, see Order book routes. Compare plans.