0xArchive serves an AI Catalog
manifest at /.well-known/ai-catalog.json on 0xarchive.io, declaring
9 agentic resources
that a discovery service can index without asking anyone’s permission.
Run against this exact body with the project’s own
conformance CLI.
Declared identity
404
did:web:0xarchive.io —
resolving it returns 404. A did:web: that does not resolve is a string, not an identity, and does not earn the identity affordance here.
Discovery path
predecessor
Answered only at /.well-known/ai-catalog.json. ARD v0.91 renamed the path to /.well-known/ard.json and made the old one an optional courtesy, so a consumer implementing only the current spec will not find this manifest.
Declared spec version
1.0
The specVersion in the manifest. 1.0 is current for the AI Catalog data model; anything lower is an earlier draft. ARD reads this field as transport-defined and ignores it.
Optional affordances missing. None of these break a client, but each one costs the publisher search relevance or verifiability.
content-type-not-ai-catalog-json
did-web-does-not-resolve
9 entries
5 media types
30 representative queries
0 trust manifests
Host identifier: did:web:0xarchive.io
What this manifest advertises
0xArchive REST API
urn:air:0xarchive.io:api:rest
Request-response API for current and historical market data across Hyperliquid and Lighter, including order books, trades, candles, funding, open interest, order history/flow, TP/SL, and data quality. Liquidation events span Hyperliquid core, HIP-3, and Lighter; projected forced-liquidation price levels span core and HIP-3. Direct requests use the `X-API-Key` header; Lighter provides L3 and Hyperliquid families provide L4 reconstruction.
“query current or historical Hyperliquid and Lighter market data over REST”
“retrieve Lighter L3 or Hyperliquid L4 order-book history”
“analyze liquidation events or projected forced-liquidation price levels”
“inspect order history, order flow, TP/SL, or data quality through OpenAPI”
0xArchive WebSocket API
urn:air:0xarchive.io:api:websocket
Use live subscriptions for supported Hyperliquid channels. Use historical replay for Hyperliquid and Lighter over `wss://api.0xarchive.io/ws`; authenticate with `Authorization: Bearer `. Timed replay includes Lighter L3, while Hyperliquid core `l4_diffs` and `l4_orders` use checkpoint-anchored bulk replay with speed ignored; all Spot channels and HIP-3/HIP-4 L4 are real-time-only. Liquidation channels cover Hyperliquid core and HIP-3.
“stream live Hyperliquid market data over WebSocket”
“replay a bounded Lighter orderbook, trades, candles, funding, open interest, or L3 history window over WebSocket”
“replay Hyperliquid core L4 diffs or orders as a checkpoint-anchored bulk stream”
“subscribe to Spot or HIP-3/HIP-4 L4 channels in real time”
“maintain local order-book state with reconnect and gap recovery”
0xArchive Hosted MCP Server
urn:air:0xarchive.io:server:market-data
Hosted MCP server for read-only market-data discovery and retrieval across Hyperliquid and Lighter. Connect to `https://mcp.0xarchive.io/mcp` with client-managed OAuth; the protected resource advertises `mcp:market.read`, and no 0xArchive API key is required.
“discover Hyperliquid and Lighter datasets through hosted MCP”
“retrieve historical market data through read-only MCP tools”
0xArchive Knowledge Bundle (OKF)
urn:air:0xarchive.io:knowledge:okf-bundle
One-fetch Open Knowledge Format bundle of typed Markdown concepts covering venue taxonomy, datasets, coverage windows, access, authentication, entitlements, pricing, and x402. Use the archive for local agent ingestion or browse the same knowledge tree at `https://0xarchive.io/okf/`.
“what venues, depth, and history does 0xArchive cover”
“read 0xArchive access, authentication, entitlement, and pricing concepts”
“ingest the 0xArchive knowledge base in one fetch”
0xArchive Wallet Access (SIWE + x402)
urn:air:0xarchive.io:capability:x402-payment
Wallet-native authentication and programmatic 30-day Build or Pro access. Existing active wallet accounts can sign in with SIWE; new or existing eligible wallets can purchase access with x402 USDC on Base, with account and API-key issuance only after successful settlement. No API key is needed to start.
“find 0xArchive SDK, CLI, authentication, and production reliability guidance”
“compare 0xArchive coverage, pricing, exports, and purchase routes”
0xArchive Data Catalog & Bulk Parquet Export
urn:air:0xarchive.io:dataset:data-catalog
Browse available coverage and order large historical datasets as S3-delivered Parquet exports. Use this surface for backtests and dataset-scale downloads that are impractical through per-request REST; one-off purchases need no subscription, while Build, Pro, and Scale export credits apply before checkout.
“order a bulk Parquet export of historical market data”
“download a dataset-scale order-book history for backtesting”
“purchase a one-off market-data export without a subscription”
0xArchive Public Coverage Manifest
urn:air:0xarchive.io:dataset:public-coverage
Machine-readable BTC coverage manifest for Hyperliquid and Lighter. HIP-4 has candles and outcome-side open interest but no funding dataset or liquidation endpoint. Free covers the most recent rolling 30 days with a maximum 30-day span per request or replay; Build and above keep the full retained archive. Use it to discover dataset types, provenance, and per-type coverage start dates.
“which Hyperliquid and Lighter BTC datasets does 0xArchive publish”
“find the published coverage start date by BTC dataset type”
“inspect the machine-readable source and generation time for public coverage”
0xArchive Fixed BTC Samples and Reconstruction Proofs
urn:air:0xarchive.io:dataset:public-btc-samples
Fixed, versioned BTC samples for every published Hyperliquid and Lighter dataset type, with browser previews, Parquet files, checksums, and source metadata. Independently runnable Hyperliquid L4 and Lighter L3 proof bundles demonstrate offline reconstruction; they do not imply WebSocket replay availability. No account or API key is required.
“download a no-login Hyperliquid or Lighter BTC market-data sample”
“verify Hyperliquid L4 offline reconstruction with a fixed proof bundle”
“inspect a Lighter L3 BTC Parquet sample before using the API”
How it is served
The publishing guide asks for three things at the transport layer, because a crawler is the
consumer that matters and a crawler is a browser-shaped client.
HTTPS only — yes (HTTP 200)
Content-Type: application/json —
yes
Access-Control-Allow-Origin: * —
yes
Evidence. Fetched https://0xarchive.io/.well-known/ai-catalog.json on 2026-09-13, HTTP
200. The verbatim body is stored alongside its manifest in the
0xArchive repository
as ai-catalog/0xarchive-ai-catalog.json. Nothing on this page is derived
or generated: an AI Catalog manifest is served from the publisher’s own domain or it does not
exist, which makes it — like an
A2A Agent Card — one of the few agent artifacts that cannot be
produced on a provider’s behalf. Grades are recomputed on every build; the specification is a
v0.9 draft and
these verdicts will move when it does.
Every descriptor here is available over the APIs.io API and to AI agents over MCP. Agent Discovery is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for agent discovery
3 MCP tools reach this
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.