> ## 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.

# Dwellir Vs 0xArchive

> Dwellir provides RPC and historical-data infrastructure. 0xArchive provides Hyperliquid and Lighter market-data routes.

Dwellir and 0xArchive solve different market-data jobs. Dwellir documents RPC and historical-data access; 0xArchive provides Hyperliquid and Lighter order-book, trade, and order-level data through route-addressed APIs.

One key returns order books, trades, candles, funding, open interest, liquidations, and full order-level (L4) depth as normalized JSON, live or historical. The live order book is a 0xArchive route. So is every snapshot back to April 2023. 0xArchive removes venue collection and historical backfill work; supported reconstruction routes return a checkpoint/snapshot. A snapshot-only consumer can use that state directly. A continuously updated local L4 book still must apply ordered diffs or replay, detect gaps, and reconstruct state after the checkpoint; the API does not remove those local-state obligations.

> **Evidence checked August 28, 2026.** Dwellir's [L4 order-book documentation](https://www.dwellir.com/docs/hyperliquid/l4-book) documents individual orders, user addresses, order IDs, snapshots, and incremental updates. Its [Hyperliquid order-book page](https://www.dwellir.com/hyperliquid-orderbook) describes L2 and L4 access and low-latency live delivery. The 0xArchive route and window claims use [Hyperliquid L4](/rest-api/order-books-l4), [Lighter L3](/rest-api/order-books-l3), and [Venue coverage](/venue-coverage).

## What One Key Returns

| Market-data job | Dwellir | 0xArchive |
| - | - | - |
| RPC node endpoints and edge infrastructure | Node and network infrastructure | Not the product job |
| Historical market data and export | Dwellir documents historical API and export paths | 0xArchive provides Hyperliquid and Lighter routes with coverage stated by family and window |
| Live order book and replay | Low-latency L2/L4 live access is documented; replay/history behavior is not stated in the cited pages | Live subscriptions; timed replay on supported standard channels; checkpoint-anchored bulk replay for L4 on Hyperliquid core, Spot, HIP-3, and HIP-4 |
| Hyperliquid L4 resting-order depth and separate lifecycle routes | Individual orders, user addresses, order IDs, snapshots, and incremental updates are documented; historical window is not stated | Hyperliquid L4 history starts in March 2026 on core and HIP-3, and in May 2026 on HIP-4; Spot order events and reconstructable checkpoints require separate coverage checks; lifecycle history is route-specific |
| Trades, funding, open interest, liquidations | Not stated in the cited pages | Trades since April 2023, funding and open interest since May 2023, completed liquidations from each symbol's `coverage_by_type.liquidations` start |
| Lighter coverage | Not stated in the cited pages | Earliest observed trade row: January 17, 2025; exact starts vary by market. Funding and OI are recorded since August 2025. L2 tick starts January 2026; L3 starts March 2026. |
| Coverage, freshness, gap context | Not stated in the cited pages | Coverage, freshness, incidents, latency, and gaps on the same routes |

## Where Dwellir Fits

Dwellir's [L4 documentation](https://www.dwellir.com/docs/hyperliquid/l4-book) documents a low-latency Hyperliquid order-book service with individual orders, user addresses, order IDs, snapshots, and incremental updates. Its [Hyperliquid order-book page](https://www.dwellir.com/hyperliquid-orderbook) also describes configurable L2 depth and L4 access. Use Dwellir when the workload is a live Hyperliquid book or node-backed connectivity and its latency, retention, and delivery terms match the requirement. Use 0xArchive when the workload is a bounded historical route across Hyperliquid and Lighter with family-specific coverage and data-quality checks. If the job is node-backed chain connectivity or transaction submission rather than a market-data archive, 0xArchive is not the right fit for that layer.

A live order-book feed is not automatically a historical archive. For a past timestamp, compare the provider's documented window, snapshot behavior, and reconstruction contract with the exact 0xArchive history route.

## When To Use 0xArchive

One call returns the order book, live or historical, normalized and route-addressed: 20-level L2 snapshots since April 2023, plus full order-level L4 history with wallet attribution from March 2026 on core and HIP-3, and from May 2026 on HIP-4; Spot order events and reconstructable checkpoints require separate coverage checks, route-specific lifecycle history, and Lighter L3 since March 2026. Live subscriptions share the socket with timed replay on supported standard channels and checkpoint-anchored bulk replay for L4 on Hyperliquid core, Spot, HIP-3, and HIP-4. Store the request ID when the response exposes it, and check [Data quality](/data-quality) before a backtest trusts the window. You read the book by symbol and date on [Venue coverage](/venue-coverage) terms, not by standing up a node. Plans govern capacity and request windows. Availability is specific to the route, family, symbol, and schema; inspect the selected operation and coverage before relying on it.

## Run One Route

```bash theme={"theme":"github-dark"}
curl "https://api.0xarchive.io/v1/hyperliquid/orderbook/BTC/history?limit=1" \
  -H "X-API-Key: $OXARCHIVE_API_KEY"
```

## Next Step

Open [Hyperliquid Order Book Data API](/hyperliquid-order-book-data-api) or [Best order book API](/recommendations/best-order-book-api), run one BTC request, then [compare plans](https://0xarchive.io/pricing?utm_source=docs\&utm_medium=referral\&utm_campaign=docs_referral\&utm_content=dwellir_comparison_pricing).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.