Self-hosted MCP server retired; hosted MCP is the only supported MCP path
This closes the sunset timing left open in 2.6.0. The self-hosted, open-source MCP server is retired. Nothing is removed: the npm package still installs and every existing self-hosted setup keeps working. It is no longer developed.
- The 0xarchive-mcp GitHub repository is archived and read-only. Its URL, releases, and history stay available. The npm package @0xarchive/mcp-server stays published and installable, and is marked deprecated so the migration notice appears at install time.
- Migrate by pointing your MCP client at https://mcp.0xarchive.io/mcp as a streamable-HTTP server. There is no package to install and no API key to place in your environment: the hosted MCP uses OAuth. Setup guide: https://docs.0xarchive.io/mcp-server
- The hosted MCP exposes a superset of the self-hosted tool surface, so migration does not cost you any tools.
- No data, endpoint, or pricing changes. REST, WebSocket, the SDKs, the CLI, and the Claude Code Skill are unaffected.
- The legacy unversioned REST routes deprecated in 2.6.0 are unchanged by this release and remain available.
Liquidation levels and trigger levels: projected forced-liquidation maps with history, on Hyperliquid and HIP-3
The liquidation-levels endpoints now serve projected forced-liquidation levels computed from clearinghouse positions and margin state. The pending stop-loss and take-profit map moved to its own trigger-levels endpoints. Both families are historical with cursor pagination, and both are available on Hyperliquid perps and HIP-3.
- GET /v1/hyperliquid/liquidations/{symbol}/levels (and the HIP-3 equivalent) returns where open positions are projected to liquidate: price buckets of long and short notional with position counts, computed from positions and margin state and refreshed about every 45 minutes. Accuracy is validated against liquidation prices reported by the exchange.
- GET /v1/hyperliquid/orders/{symbol}/trigger-levels (and the HIP-3 equivalent) carries the pending stop-loss and take-profit trigger-order map that previously lived on the liquidations path, with an as_of freshness timestamp and side totals.
- Both families gained /history endpoints: cursor pagination via meta.next_cursor, summary=true for cheap snapshot discovery, and at= (epoch ms) point-in-time reads on the current endpoints. Snapshots are retained from July 27, 2026: trigger levels every 15 minutes, liquidation levels about every 45 minutes.
- Breaking note: before this release the HIP-3 /liquidations/{symbol}/levels path served the trigger-order map. Clients reading trigger buckets from that path should move to /orders/{symbol}/trigger-levels.
- SDKs 1.8.0 (TypeScript, Python, Rust) add typed methods for all four families, plus fixes: WebSocket l4_snapshot and l4_batch frames are now surfaced in Rust and Python (previously dropped), Rust candles and liquidations-by-user calls are repaired, spot pair and TWAP types now match the wire, and TypeScript L2 full-depth pagination cursors work again.
- Hosted MCP 1.1.0: 13 new tools (levels and trigger levels on both venues, HIP-4 questions, Lighter liquidations), corrected order-status enums, and removal of filters the backend does not implement.
- OpenAPI 1.6.0 documents all eight levels operations with exact response schemas.
Hosted MCP is canonical; self-hosted MCP and legacy unversioned routes deprecated
The hosted MCP is now the canonical MCP entry point. The self-hosted, open-source MCP server and a small set of legacy unversioned REST routes are deprecated in favor of their supported equivalents. Path change only — no data changes.
- Two canonical paths going forward, pick whichever matches your client: the hosted MCP (mcp.0xarchive.io/mcp) for MCP-capable clients, or the Claude Code Skill (curl+jq against the REST API, no MCP involved) for skill-capable coding agents. They are separate integrations, not the same thing.
- The self-hosted, open-source 0xarchive-mcp GitHub repo is deprecated. Existing self-hosted deployments continue to work for now; migrate to the hosted MCP for new integrations.
- Legacy unversioned REST routes /v1/orderbook, /v1/trades, /v1/funding, /v1/openinterest, and /v1/instruments are deprecated in favor of their /v1/hyperliquid/* equivalents.
- Sunset timing for the self-hosted MCP and legacy routes is pending internal confirmation; nothing is being removed with this release.
Pricing and route reliability
Free replaced trials, paid plan limits are current, and repaired Spot/L4 routes are live in production.
- Trials are retired; Free is the entry path with no card, full endpoint coverage, full history with 90D query windows, 50k credits, 15 RPS, 10 WS, and 10x replay.
- Build is 80M credits, 50 RPS, 500 WS, 50x replay, 10 API keys, and $50 monthly export credits.
- Pro is 400M credits, 150 RPS, 3,000 WS, 100x replay, 100 API keys, and $300 monthly export credits.
- Scale is self-serve: 2B credits, 500 RPS, 20,000 WS, 300x replay, 200 API keys, and $1,500 monthly export credits.
- Spot export quotes, spot order history, spot freshness L4 fields, wallet profiles, and wallet cancel-speed metrics were repaired in production.
REST credits are now billed per row
REST API billing moved from a flat cost per call to per-row metering. You pay for the rows a request returns, not a fixed fee per route, so most workflows get about 2x or more data per credit. Monthly allowances are unchanged and no client code changes are required.
- Formula: charged = max(1, ceil(rows_returned / rows_per_credit)), with a 1 credit minimum per request
- Trades, fills, L2 order book history, funding, open interest, liquidations, and Lighter L3 order book: about 1 credit per 1,000 rows
- Candles: about 1 credit per 10,000 rows
- L4 routes (diffs, orders, flow, TP/SL, reconstruction): about 1 credit per 5,000 rows
- Single value endpoints (current order book, current funding, current open interest, summary, prices, freshness, instruments, symbols, pairs, outcomes): 1 credit
- Monthly allowances unchanged: Free 10M, Build 80M, Pro 400M, Enterprise 1B
- WebSocket and historical replay billing unchanged: 1 credit per message
- Opt-in Apache Arrow output (?format=arrow) is available for the trades family and is billed the same as JSON, never cheaper or more expensive
Spot trades history now goes back to March 2025
Hyperliquid spot trades now cover March 22, 2025 onward, over a year of history. Priority gas auction payments and spot transfers are also available going back several months.
- GET /v1/hyperliquid/spot/trades/{symbol}: full trade history with builder fees, twap_id, fee token, and real EVM transaction hashes per fill, back to March 22, 2025
- GET /v1/hyperliquid/spot/orders/{symbol}/history: order lifecycle (open, filled, canceled, rejection variants) for all 294 pairs
- GET /v1/hyperliquid/spot/twap/{symbol} and /v1/hyperliquid/spot/twap/user/{user}: TWAP order tracking
- GET /v1/hyperliquid/spot/orderbook/{symbol} and /v1/hyperliquid/spot/orderbook/{symbol}/history: L2 order book snapshots and history
- GET /v1/hyperliquid/spot/orderbook/{symbol}/l4 and l4/diffs (Pro+): full L4 reconstruction with per-order user attribution
- GET /v1/hyperliquid/spot/pairs and /pairs/{symbol}: spot pair metadata for all 294 pairs
- Spot orderbook and L4 data remain live-only (May 5, 2026 onward) because Hyperliquid does not publish historical order book snapshots for spot
Hyperliquid spot data live
Hyperliquid spot is now a first-class exchange in the archive. 294 pairs covered in real time from May 5, 2026 onwards via spot-ingester (public WebSocket) and node-ingester (Singapore prod node).
- 5 new WebSocket channels: spot_orderbook, spot_trades, spot_l4_diffs, spot_l4_orders, spot_twap
- 13 new REST endpoints under /v1/hyperliquid/spot/* (orderbook, trades, orders, twap, pairs, freshness, etc.)
- Build+ tier for orderbook, trades, and TWAP. L4 diffs and L4 orders are Pro+
- Symbol convention is dashed: PURR-USDC, HYPE-USDC, HFUN-USDC. Bare tokens (HFUN) also accepted. Server resolves to wire format internally; users never see @107-style ids
- L4 lifecycle covers open, filled, canceled, selfTradeCanceled, badAloPxRejected, insufficientSpotBalanceRejected, iocCancelRejected, minTradeNtlRejected
- Verbose schema kept: builder address + builder fee per fill, fee token (24+ tokens, not just USDC), real EVM transaction hashes, twap_id joins between fills and parent TWAP orders
- No funding rates, no open interest, no liquidations. These are perp-only constructs and do not exist for spot
- No historical backfill of orderbook or L4 in this release. Live forward only
Real-Time Liquidations
The `liquidations` and `hip3_liquidations` WebSocket channels now stream in real time, sub-second from a Hyperliquid node. Previously these channels only supported historical replay.
- New real-time channels: liquidations (Hyperliquid), hip3_liquidations (HIP-3) — Build+
- Sourced in real time from the Hyperliquid node's per-block fill data with the `is_liquidation` flag; sub-second latency, no S3 lag
- Same wire format as `trades` / `hip3_trades` (each item is a fill record with `is_liquidation: true`), so existing trade-parsing code drops in unchanged
- Liquidation events continue to flow on `trades` / `hip3_trades` for backward compatibility — subscribers to both channels should dedupe on `tid`
- Available on both wss://api.0xarchive.io/ws and wss://stream.0xarchive.io/ws
- Maker + taker still emit separately (one fill = two records, paired by `tid`) — same as the trades channel
- Historical replay via `{"op": "replay", "channel": "liquidations", ...}` continues to work; the previous "historical only" gate has been removed for real-time `subscribe`
HIP-4 Outcome Markets
Hyperliquid HIP-4 binary outcome markets are now ingested end-to-end: per-side L2 and L4 order books, trades, candles, open interest, and per-outcome aggregates that combine both sides of a market.
- GET /v1/hyperliquid/hip4/outcomes — list outcomes with `is_settled` filter
- GET /v1/hyperliquid/hip4/outcomes/{outcome_id} — detail with `aggregated_oi` (paired-set supply, side parity)
- GET /v1/hyperliquid/hip4/outcomes/by-slug/{slug} — Hyperliquid-style URL slug lookup
- GET /v1/hyperliquid/hip4/instruments, /orderbook/{symbol}, /trades/{symbol}, /candles/{symbol}, /openinterest/{symbol} — per-side market data (coins are numeric ids 0, 1, 10, 11, ...; `#`-prefixed form is also accepted)
- L4 routes (Pro+): /orderbook/{symbol}/l4, /l4/diffs, /l4/history, /orders/{symbol}/{history,flow,tpsl}
- WebSocket channels: hip4_orderbook, hip4_trades, hip4_open_interest (realtime + replay); hip4_l4_diffs, hip4_l4_orders (realtime only, Pro+). HIP-4 candles are REST probability-history series, not a dedicated WebSocket channel
- Bulk Parquet exports for hip4 l2_orderbook, l4_orderbook, l4_checkpoints, l4_orders, trades, oi, outcomes
- Settlement provenance: each settled outcome records block_number, block_time, and oracle_tx_hash
- No funding or liquidations by design — HIP-4 is fully collateralized binary outcomes; candle prices represent implied probabilities, not USD prices
- mark_price for HIP-4 is implied probability in [0, 1], not USD — mirrors upstream `markPx` on purpose
- Coverage begins May 2, 2026 (first day outcomes appeared on chain)
Extended Fill Fee Breakdown
Trade/fill responses now include a full fee breakdown: builder fees, HIP-3 deployer fees, priority fees (HYPE burned for write priority), client order IDs, and TWAP execution IDs.
- New fill fields: builder_address, builder_fee, deployer_fee, priority_gas, cloid, twap_id
- builder_fee — fee charged by the builder/relay that routed the order (in quote currency)
- deployer_fee — HIP-3 deployer's trading fee share (in quote currency)
- priority_gas — HYPE burned for order write priority (IOC orders on HIP-3)
- cloid — client-assigned order ID for tracking fills back to submissions
- twap_id — TWAP execution ID for fills belonging to a TWAP parent order
- Available on all trade/fill endpoints for Hyperliquid and HIP-3
- Included in Parquet bulk exports and all three SDKs (Python, TypeScript, Rust v1.4.0)
- MCP server updated to v1.6.0, CLI updated to v1.4.0
L2 Full-Depth Orderbook & Reconstruction SDKs
Full-depth L2 orderbook endpoints for Hyperliquid and HIP-3, plus orderbook reconstruction helpers in all three SDKs.
- GET /orderbook/:symbol/l2 — full-depth L2 snapshot at any timestamp (depth varies by tier)
- GET /orderbook/:symbol/l2/history — paginated L2 checkpoints (depth varies by tier)
- GET /orderbook/:symbol/l2/diffs — tick-level L2 price-level changes (Pro+)
- Available for both Hyperliquid and HIP-3 (6 new endpoints)
- L4OrderBookReconstructor in Python, TypeScript, and Rust SDKs — reconstruct L4 and L2 books client-side
- New CLI commands: oxa l2 get, oxa l2 history, oxa l2 diffs
- 6 new MCP tools for L2 orderbook access
- Reconstruction docs: server-side (one API call) and client-side approaches
L4 Order-Level Data & TP/SL History
Full order-level orderbooks, order lifecycle events, and TP/SL history for Hyperliquid and HIP-3.
- GET /orderbook/:symbol/l4 — L4 orderbook at any timestamp with user attribution (Pro+)
- GET /orderbook/:symbol/l4/diffs — individual order changes over time (Pro+)
- GET /orderbook/:symbol/l4/history — periodic L4 checkpoints (Build+)
- Order lifecycle history, order flow aggregation, and TP/SL order history
- Real-time L4 WebSocket channels: l4_diffs, l4_orders, hip3_l4_diffs, hip3_l4_orders (Pro+)
- L4 diffs available from March 10, 2026; checkpoints and reconstruction from March 11, 2026
Full HIP-3 Builder Coverage
Expanded HIP-3 support from 29 markets (xyz + km) to all 125+ markets across every active builder.
- All 6 builders now supported: xyz (XYZ), flx (Felix Exchange), hyna (HyENA), km (Kinetiq Markets), vntl (Ventuals), cash (dreamcash)
- New asset classes: crypto majors (hyna:BTC, hyna:ETH, hyna:SOL), thematic indices (vntl:MAG7, vntl:SPACEX, vntl:OPENAI), commodities (flx:PALLADIUM, flx:PLATINUM), and more
- All data types available: orderbook, trades, candles, funding rates, open interest
- Data available from March 4, 2026 for new markets
Lighter & HIP-3 Convenience Endpoints
Freshness, summary, and pre-aggregated price history now available across Hyperliquid core, Hyperliquid HIP-3, and Lighter.
- GET /v1/lighter/freshness/:symbol, /summary/:symbol, /prices/:symbol
- GET /v1/hyperliquid/hip3/freshness/:coin, /summary/:coin, /prices/:coin
- Pre-aggregated price history intervals (5m, 15m, 30m, 1h, 4h, 1d) — no client-side rollups needed
- Python, TypeScript, and MCP SDKs updated
Multi-Channel WebSocket Replay
Stream multiple channels synchronized on a single WebSocket connection.
- Replay orderbook + trades + funding + open interest in timestamp order
- Synchronized multi-channel replay
- Initial replay_snapshot messages for each channel before timeline starts
- Lighter and HIP-3 WebSocket channels (orderbook, trades, candles, OI, funding)
WebSocket Gap Detection
Automatic gap detection during historical replay.
- Server-side gap detection with configurable thresholds
- gap_detected messages notify clients of data gaps
- Thresholds: 2 min for orderbook/candles/liquidations, 60 min for trades
- SDK support via onGap() / on_gap() callbacks
Data Quality Monitoring
New endpoints for monitoring data coverage, incidents, latency, and SLA compliance.
- GET /v1/data-quality/status - System health overview
- GET /v1/data-quality/coverage - Data coverage by exchange
- GET /v1/data-quality/coverage/:exchange/:symbol - Symbol-level gap detection
- GET /v1/data-quality/incidents - Incident tracking
- GET /v1/data-quality/latency - Real-time latency metrics
- GET /v1/data-quality/sla - SLA compliance reporting
Liquidations API
Historical liquidation events for Hyperliquid.
- GET /v1/hyperliquid/liquidations/:coin - Liquidation history by symbol
- GET /v1/hyperliquid/liquidations/user/:user - Liquidations by user address
- WebSocket liquidations channel for replay/streaming
- Data available from December 2025 onwards
WebSocket Streaming
Real-time data streaming via WebSocket connections.
- Subscribe to real-time order book updates
- Stream trades in real time
- Funding rate push notifications
- Connection health monitoring
OAuth Authentication
Sign in with GitHub and Google for faster onboarding.
- GitHub OAuth integration
- Google OAuth integration
- Automatic account linking
Performance Improvements
Significant improvements to API response times.
- Reduced average response time by 40%
- Optimized database queries for order book history
- Added response compression for large payloads
Bug Fixes
Various bug fixes and stability improvements.
- Fixed pagination in trades endpoint
- Resolved timezone handling in candle data
- Fixed rate limit header accuracy
Initial Release
Official launch of 0xArchive.io API.
- Order book snapshots from April 2023
- Trade history API
- Funding rates and open interest
- OHLCV candle data
- Self-serve API key management
- Usage dashboard and analytics
