canonical: https://jentic.com/apis/0xarchive.io/0xarchive # 0xArchive API The 0xArchive API serves current and historical market data for the Hyperliquid and Lighter decentralised perpetuals venues, including spot pairs, HIP-3 builder perpetuals, and HIP-4 outcome markets. It returns trades, OHLCV candles, funding rates, open interest, and both native and full-depth L2 and L4 order book snapshots and diffs for a symbol. Liquidation events, liquidation levels, cumulative volume delta, and wallet classification are available across each venue. Webhook subscriptions and watched-address alerts let a client follow new deliveries without polling. ## For AI agents Read Hyperliquid and Lighter perpetuals and spot market data for AI agents: trades, OHLCV candles, funding rates, open interest, liquidations, and full-depth order books by symbol. ## Scope Does not place orders, hold funds, or execute trades on any venue. Use for reading Hyperliquid and Lighter market data only. ## Capabilities - Pull current and historical trades for a Hyperliquid or Lighter perpetual by symbol - Retrieve OHLCV candles and funding rate history for a market and interval - Read native and full-depth L2 and L4 order book snapshots and diffs for a symbol - Track open interest, liquidation events, and liquidation levels across Hyperliquid, HIP-3, and HIP-4 markets - Subscribe to webhook deliveries for watched wallet addresses and market events - Classify Hyperliquid wallets by order count, traded volume, and cancel rate ## Use cases ### AI market-research agent for perpetuals An AI agent researching a token's microstructure needs grounded market data without wiring a bespoke client. Through Jentic the agent searches for 'get recent trades for a perpetual', loads the matching 0xArchive operation with its input schema, and reads trades and candles for the symbol with the API key injected at call time. The agent returns a summary of recent flow for a Hyperliquid or Lighter market without browsing the reference docs. Example prompt: Fetch the latest trades via GET `/v1/hyperliquid/trades/{symbol}` and hourly candles via GET `/v1/hyperliquid/candles/{symbol}` for a symbol, then summarise recent price action ### Backtesting data pipeline Quantitative researchers backfilling a strategy pull historical candles, funding, and open interest for a basket of symbols. 0xArchive exposes cursor-paginated history for each series, so a pipeline can page from a start timestamp to an end timestamp per market. Funding rate history pairs with candle data to reconstruct carry-adjusted returns for Hyperliquid and Lighter perpetuals. Example prompt: Page GET `/v1/hyperliquid/funding/{symbol}` and GET `/v1/hyperliquid/candles/{symbol}` from a start to an end timestamp and store the merged series ### Liquidation monitoring A risk dashboard tracks forced liquidations and clustering of stop levels for the symbols it watches. 0xArchive returns individual liquidation events, aggregated liquidation volume, and bucketed liquidation levels for a symbol. Combined with trigger-level history, this lets a monitor flag when a market is approaching a dense band of resting stops. Example prompt: Poll GET `/v1/hyperliquid/liquidations/{symbol}` for a symbol and alert when liquidation volume over the last hour exceeds a threshold ### Order book depth analysis A microstructure study needs reconstructed depth rather than top-of-book quotes. 0xArchive serves native 20-level and full-depth L2 order book snapshots, L2 diffs, and L4 order book data for a symbol, plus point-in-time history by timestamp. An agent can rebuild the book at a chosen moment to measure spread, imbalance, and depth at price. Example prompt: Fetch GET `/v1/hyperliquid/orderbook/{symbol}/l2` at a given timestamp and compute bid-ask depth imbalance for the top levels ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/v1/hyperliquid/trades/{symbol}` | Get Hyperliquid trades for a symbol | | GET | `/v1/hyperliquid/candles/{symbol}` | Get Hyperliquid OHLCV candles | | GET | `/v1/hyperliquid/orderbook/{symbol}/l2` | Get full-depth L2 order book | | GET | `/v1/hyperliquid/funding/{symbol}` | Get funding rate history | | GET | `/v1/lighter/trades/{symbol}` | Get Lighter trades for a symbol | | GET | `/v1/hyperliquid/hip4/outcomes` | List HIP-4 outcome markets | | POST | `/v1/webhooks/subscriptions` | Create a webhook subscription | | GET | `/v1/data-quality/coverage` | Get coverage summary | ## Key resources - **Hyperliquid markets** — Instruments, trades, candles, funding, open interest, order books, and orders for Hyperliquid core perpetuals and spot - **HIP-3 and HIP-4 markets** — Builder perpetuals (HIP-3) and outcome markets (HIP-4) with their own instruments, trades, candles, and order books - **Lighter markets** — Instruments, trades, candles, funding, and order books for Lighter mainnet and Lighter on Robinhood Chain - **Webhooks** — Endpoints, subscriptions, deliveries, and watched wallet addresses for push notifications ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 59 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 73 / 100 - Developer Experience & Jentic Compatibility: 78 / 100 - AI-Readiness & Agent Experience: 57 / 100 - Agent Usability: 43 / 100 - Security: 50 / 100 - AI Discoverability: 80 / 100 - **View full report:** https://jentic.com/apis/0xarchive.io/0xarchive/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring 0xArchive by hand means registering an API key, sending it in the X-API-Key header, and handling cursor pagination across hundreds of symbol routes split over Hyperliquid, HIP-3, HIP-4, and Lighter. Through Jentic you install once, import 0xArchive from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** 0xArchive is a read-only data API whose markets sit under symbol paths such as `/v1/hyperliquid/trades/{symbol}`, so a rule can pin your agent to the market-data operations it needs. You choose which operations it may call, so webhook-management routes like deleting an endpoint or rotating a secret are not included unless you add them. - **Credential handling:** Your 0xArchive API key is stored once, encrypted, by your own Jentic One instance and attached to each request at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'get recent trades for a perpetual' or 'read the funding rate', and Jentic returns the matching 0xArchive operation with its input schema, including the symbol and pagination parameters, so the agent calls the right endpoint directly. ## Related APIs - **CoinGecko** — Broad crypto price and market data across thousands of assets, rather than venue-level perpetuals microstructure - **CoinAPI** — Multi-exchange market data including order books and OHLCV across many centralised venues - **Kraken** — Spot exchange with live market data and order placement for a centralised venue ## FAQ ### What authentication does the 0xArchive API use? 0xArchive authenticates with an API key sent in the X-API-Key request header, as declared in its OpenAPI spec. A handful of endpoints such as GET /health and GET `/v1/symbols` are public and need no key, while the market-data routes expect the key. Through Jentic the key is held by your own instance and attached to each call, so the agent never sees it. ### Can I pull historical candles and funding rates with the 0xArchive API? Yes. GET `/v1/hyperliquid/candles/{symbol}` returns OHLCV candles for a symbol and interval, and GET `/v1/hyperliquid/funding/{symbol}` returns funding rate history. Both are cursor-paginated between a start and end timestamp, so an agent can page back across the available history for Hyperliquid, HIP-3, HIP-4, and Lighter markets. ### What are the rate limits for the 0xArchive API? The OpenAPI spec does not declare numeric rate limits, and limits vary by access tier and route. Check the 0xArchive documentation at https://docs.0xarchive.io/ for the current per-plan limits before scripting bulk history extraction. ### Is there a 0xArchive MCP server? You do not need an MCP server to give your agent 0xArchive. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the market-data operations it needs on demand without loading another server's tool definitions into its context. ### How do I read a symbol's order book through Jentic? Search Jentic for 'get the full-depth order book for a symbol', load the GET `/v1/hyperliquid/orderbook/{symbol}/l2` operation, and execute it with the symbol and an optional timestamp. The response carries the depth levels so the agent can measure spread and imbalance. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Can I limit what my agent is allowed to do with the 0xArchive API? Yes. Write a rule that allows only the read operations your task needs, such as fetching trades and candles for a symbol, and the agent can read that market data and nothing else. Every operation sits behind a path your rule can pin, and each call the agent makes is logged for review.