/v1/symbols coverage_by_type. Verify the selected pair with the pairs and freshness routes. It is not the right fit for a core perp, a venue outside Hyperliquid, execution, account state, or wallet signing.
Spot pairs such as HYPE-USDC stay under /v1/hyperliquid/spot/*. They are not core perp symbols with a suffix and should not be routed through a generic asset-price feed.
Spot Route Matrix
How To Choose A Spot Data API
When To Use 0xArchive
0xArchive keeps the Spot pair attached to its route family, history window, data quality result, and export schema. REST responses are route-specific JSON. A local L4 consumer still applies the documented state and gap handling when it reconstructs a book; a snapshot-only consumer can stop at the returned state. Storemeta.request_id when the response exposes it.
Use the Spot routes for pair data, not core perp routes. Use the Data Catalog when the deliverable is a Parquet file rather than a request-by-request response. Plans govern capacity and request windows. Availability is specific to the route, family, symbol, and schema; check the selected operation and coverage before widening a job.