Use this page for product and setup questions that often come before a first API call. Follow the linked page when you need the exact current contract.
What does 0xArchive provide?
0xArchive provides current and historical market data through two top-level venue APIs: Hyperliquid and Lighter. Hyperliquid core, Spot, HIP-3, and HIP-4 are Hyperliquid-scoped market families. Lighter is a separate venue family. Available schemas and history vary by market and data type, so verify the exact symbol and window on Venue coverage before relying on a result.
Which interface should I use?
Use REST for bounded history and point-in-time requests. Use WebSocket for real-time subscriptions and channel-specific replay. Core Hyperliquid L4 replay uses checkpoint-anchored bulk delivery. Spot, HIP-3, and HIP-4 L4 channels are real-time only.
Lighter channels support historical replay but not live subscriptions through the 0xArchive WebSocket. Use REST for current data and REST, WebSocket replay, or exports for historical data.
Which plan should I start with?
Start with the Free tier to confirm authentication, route fit, response shape, coverage, and freshness. Compare the current plan limits on Rate limits and credits when you need history older than Free’s most recent rolling 30 days, more request volume, concurrency, replay capacity, query range, or support. Use Contact when the published plans do not match the workload.
How do I verify coverage and freshness?
Coverage is not uniform across symbols or schemas. Check Venue coverage for the exact market and data type, then use Data quality and freshness before a backtest, production query, replay, or export. History available for one schema does not establish the start date for another.
Can I redistribute the data?
Internal research, trading, backtesting, storage, models, and materially transformed product outputs are generally permitted within the documented boundaries. Raw resale, bulk republication, API mirroring, substitute feeds, benchmarks, indices, financial products, and white-label or OEM delivery require written permission. Read Data rights and redistribution and the binding Data License before shipping a customer-facing data product.
What does 0xArchive not provide?
0xArchive is a market-data service, not an account or execution service. It does not provide current balances, portfolio state, margin state, current positions, order execution, private trading APIs, or a general Hyperliquid node or RPC service. It also does not provide unlisted venue APIs outside current Hyperliquid and Lighter coverage.
Some historical market-data responses may include source-derived user_address or builder_address fields for client-side analysis. Those fields do not provide current account state or a private trading interface. For current Lighter data and historical Hyperliquid or Lighter market data, use the documented market-data interfaces and verify the symbol and window on Venue coverage.
What should the assistant not answer?
The website assistant should not guess about account status, billing changes, private usage, current incidents, custom commercial terms, legal interpretation, unpublished roadmap, or undocumented coverage. Use the dashboard for account facts, the status page for current service state, and Contact for sales, support, or rights questions.
Do not send API keys, credentials, personal data, or other secrets to the assistant. Questions and conversation context are sent to Mintlify to generate an answer, and Mintlify retains conversation history for assistant analytics. The website keeps a bounded copy in this browser until you clear it. 0xArchive does not operate a separate conversation database. Clearing the browser copy does not delete that provider copy. AI-generated answers may be wrong. Verify important details against the linked documentation and product surfaces. 
