> ## Documentation Index
> Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Common questions

> Quick answers about 0xArchive data, interfaces, plans, coverage, and data-use boundaries, with links to the authoritative documentation.

Use this page for the 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 historical and live market data for 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](/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 live subscriptions and ordered historical replay. Use Data Catalog exports for bulk files. SDKs, CLI, MCP Server, Skill, and OpenAPI support different development and agent workflows. [Choose an interface](/tooling) before writing an integration.

## Which plan should I start with?

Start with the [Free tier](/core-concepts/free-tier) to confirm authentication, route fit, response shape, coverage, and freshness. Compare the current plan limits on [Rate limits and credits](/rate-limits) when you need more request volume, concurrency, replay capacity, query range, or support. Use [Contact](https://0xarchive.io/contact?utm_source=docs\&utm_medium=referral\&utm_campaign=docs_referral\&utm_content=common_questions_plan) 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](/venue-coverage) for the exact market and data type, then use [Data quality and freshness](/data-quality) 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](/data-rights) and the binding Data License before shipping a customer-facing data product.

## 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 unsupported coverage. Use the dashboard for account facts, the [status page](https://0xarchive.io/status) for current service state, and [Contact](https://0xarchive.io/contact?utm_source=docs\&utm_medium=referral\&utm_campaign=docs_referral\&utm_content=common_questions_escalation) 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.