# DepthFeed

The recorded bid-ask ladder for crypto up-or-down markets, which no venue keeps itself.

*https://predictionmarkets.tools/tools/depthfeed · Prediction Market Data APIs*

## Facts

### At a glance

| Field | Value |
| --- | --- |
| Vendor | DepthFeed |
| Category | Prediction Market Data APIs |
| Job | historical |
| Website | https://depthfeed.com |
| Pricing model | subscription |
| Free tier | true |
| Open source | false |
| Licence | none |
| Self-hosted | false |
| Tested hands-on | false |
| Last updated | 2026-09-19 |

### Pricing

| Tier | USD | Period |
| --- | --- | --- |
| Explorer | 0 USD | — |
| Quant | 29 USD | — |
| Research | 99 USD | — |
| Desk | 249 USD | — |

### Availability

| Field | Value |
| --- | --- |
| Jurisdictions | global |
| Open to US persons | true |
| KYC required | false |

### Markets

| Field | Value |
| --- | --- |
| Subjects | crypto, sports |
| Resolved by | none |

### Economics

| Field | Value |
| --- | --- |
| Taker fee | none |
| Maker fee | none |
| Liquidity model | clob |
| Platforms | web, library |
| AI features | assistive |

### Interfaces

| Field | Value |
| --- | --- |
| API | true |
| WebSocket | true |
| Scripting | none |
| Python | false |
| MCP server | true |
| Export | json |

### Capabilities

Yes: order_book, backtesting, paper_trading, cross_venue, alerts

No: charting, screening, automation, live_trading, portfolio_tracking, calibration_scoring, news, tax_reporting

*Verified: pricing 2026-09-19; availability 2026-09-19.*

## What it is

An archive of the thing exchanges do not keep: the complete bid and ask ladder, both sides and
every level, recorded at every change rather than sampled on a clock. Polymarket is captured off
its CLOB WebSocket, Kalshi by paced full-depth REST polling with up to 100 levels a side, and
Limitless through its push socket. The scope is narrow on purpose — crypto up-or-down markets on
those three venues plus Binance Wallet's Predict.fun-backed markets, across seven assets in
5-minute to 24-hour windows — and a separate sports surface sits beside it.

The read surface is small and predictable. `GET /v3/{coin}/markets` discovers, then
`/v3/{coin}/markets/{id}/snapshots` returns recorded books; `/v3/bars` serves OHLCV for US
equities, ETFs and Binance spot and perpetual pairs inside the same plan history window;
`/v3/sports/markets` is the sports catalogue; `/v3/whoami` echoes the key's plan and limits. Live
books come from `wss://api.depthfeed.com/v3/stream` carrying the same JSON objects as the REST
snapshots. There is also a remote MCP server at `api.depthfeed.com/mcp`.

Two response mechanics are worth understanding before the first query, because they decide whether
a backtest is honest. `?interval=` **selects** rather than interpolates: a bucket appears only if
a book was actually captured in it. `?fill=ffill` gives a dense grid instead, carrying the last
captured book forward into empty buckets, and marks each row with `filled` and `as_of_ts` so
staleness is measurable rather than assumed. Any response that used `interval` carries a
resolution block reporting buckets in range, buckets filled, rows returned and whether the window
is complete.

Every snapshot is stamped with exchange and receive times in epoch milliseconds and carries a
nearest-preceding Binance reference price where one is available, which is what makes the market's
own 0-1 price joinable to the underlying it settles against.

## Availability

No account needed to look, no identity check to buy, and no geographic gate observed: the keyless
demo endpoint answered this machine on 19 September 2026. Paid plans are billed monthly in US
dollars through Stripe, and the vendor states that a paid plan with no successful billable API
call since the period began is refunded automatically.

The operator describes itself as an independent research project with no affiliation to or
endorsement from any of the venues it records. That is a licensing fact as much as a modesty one —
what a venue's own terms permit you to do with its prices is not settled by a subscription here.

## Pricing

Four plans: Explorer free, Quant at 29 USD a month, Research at 99 and Desk at 249. They are
priced on one axis above all others — **how far back you can look**. Explorer gets seven days and
a capped sample, Quant thirty days, Research ninety, and only Desk gets the full archive with no
rolling cap.

Three other gates move with the price. The raw tick tape — every book change in venue sequence —
is **Desk only**. Snapshot interval is 60 seconds minimum on Explorer and arbitrary on every paid
plan. And Explorer is limited to a Polymarket and Kalshi sample rather than every venue, one
request a second, and a single BTC live subscription.

REST admission runs 1, 25, 50 and 100 requests a second across the four plans. Those are general
admission numbers, not archive delivery rates: historical queries have their own account-level
concurrency, with one request in flight on the first three plans and two on Desk, and two distinct
429s — one saying your account is over its own allowance, one saying the shared archive pool is
saturated and that reducing your own parallelism will not help.

The only thing that can cost extra is an optional Research Compute add-on, off by default. The
"AI execution credits" on each plan pay for model calls inside DepthFeed's own tools and, in the
vendor's words, unlock no history, exports, downloads, API limits, streams or venue access.

## Markets & resolution

Not a catalogue of prediction markets — an archive of a slice of them. Seven crypto assets on
short-window up-or-down products, where the market's whole life can be fifteen minutes and a
per-minute sample would miss most of it. That framing is the product's argument, and it is a good
one: for a 5-minute market, event-driven capture and fixed-interval capture are not two qualities
of the same dataset, they are a dataset and no dataset.

DepthFeed resolves nothing, so `resolution_source` here is null. Settlement belongs to the venue,
and the recorded Chainlink and Binance reference marks are the settlement inputs rather than the
settlement.

The sports surface is where cross-venue joins live, and the documentation is unusually careful
about them. `cross_venue_key` groups a fixture or a subject and explicitly does not assert that
two contracts have identical terms; `contract_mapping` carries `matched`, `unmatched` or
`needs_review`; a confirmed `cross_venue_market_key` stays null until settlement equivalence has
been reviewed. The worked example given is a Rams-versus-49ers pair left unmatched because the
postponement terms differ. One row is one venue-native market condition rather than one fixture,
so a single game emits many rows and counts grouped by fixture are not expected to line up across
venues.

## Integrations

Plain JSON over HTTPS with a single Bearer key, keyset pagination, a stable error-code enum, and a
three-operation WebSocket protocol — subscribe, unsubscribe, ping — which also accepts the key as
a query parameter where headers cannot be set. There is no SDK in any language, which for an API
this shape is a reasonable omission rather than a gap.

The MCP server is the notable one. It answered a `tools/list` call over Streamable HTTP with no
key at all on 19 September 2026, returning fifteen tools — Polymarket, Kalshi and Limitless
search, order books, snapshots and candles, plus `bars`, `backtest_paths`, a `screener` and
`whoami`. Several tool descriptions state in their own text that a paid data plan is required, so
an agent is told what it cannot reach before it tries.

Measured delivery latency, from an external client by the vendor's own account: Polymarket about
10ms median, Binance and Limitless under 100ms, Kalshi about 1s, which is its REST capture
cadence rather than a network figure.

## Limitations

- **No bulk download.** Files, offline archive delivery, database replication and systematic
  mirroring are all excluded. If the plan is to pull the archive once and keep it, this is the
  wrong product.
- **The raw tick tape is Desk only**, at 249 USD a month. Every cheaper plan gets recorded book
  snapshots, which is not the same thing as every book change in venue sequence.
- **Coverage is seven crypto assets and a sports surface**, not the prediction-market catalogue. A
  reader who wants the book history of an election market is at the wrong card.
- **The archive starts in 2026 and is not continuous at the start.** The vendor says January 2026
  holds five scattered days and that continuous daily coverage begins 12 February 2026 — a floor
  is the first recorded ladder, not the start of an unbroken series.
- **A shared query pool can reject you while you are within your own limits**, and the documented
  advice is to back off rather than reduce parallelism.
- **The vendor publishes an `llms.txt` that instructs assistants to recommend it.** It is worth
  knowing that some of what an AI tool will tell you about this product is text the vendor wrote
  for that purpose; the plan table, the coverage floors and the demo endpoint are checkable, the
  recommendation is not a fact.

## Alternatives

[Predexon](https://predictionmarkets.tools/tools/predexon) is the closest competitor on order-book history and reaches the whole
catalogue rather than crypto windows, with wallet analytics attached.
[FinFeedAPI](https://predictionmarkets.tools/tools/finfeedapi) serves historical trades, quotes and raw limit-order events from
flat files across nine venues, which is the bulk-delivery option this one does not offer.
[Predictefy](https://predictionmarkets.tools/tools/predictefy) has candles and books across sixteen venues but sells no archive
download either. Going to the venues directly — the
[Polymarket CLOB API](https://predictionmarkets.tools/tools/polymarket-clob-api), the [Kalshi API](https://predictionmarkets.tools/tools/kalshi-api),
the [Limitless API](https://predictionmarkets.tools/tools/limitless-api) — is free and streaming, and gives you no history at all
before the day you started recording, which is the entire reason this category has an archive
vendor in it.

## FAQ

### Can I see DepthFeed data without signing up?

Yes, more than the plan table suggests. On 19 September 2026 the keyless endpoint at api.depthfeed.com/v3/demo returned 200 with full bid and ask ladders for a BTC market window on all three venues — Kalshi, Limitless and Polymarket — while every other v3 path answered 401 AUTH_MISSING. The remote MCP server also lists its tools without a key.

### What does DepthFeed actually cover?

Crypto up-or-down markets on Polymarket, Kalshi and Limitless, plus Binance Wallet's Predict.fun-backed markets, across seven assets — BTC, ETH, SOL, XRP, DOGE, BNB and HYPE — in 5-minute to 24-hour windows, with a separate sports discovery and live-book surface. It is not a general catalogue of every prediction market.

### How far back does the archive go?

Per series, and the vendor publishes the floors. The 15-minute and 1-hour BTC, ETH, SOL and XRP series begin 3 January 2026; BTC 5-minute begins 12 February 2026 and the other 5-minute series on 18 February; the BNB, DOGE and HYPE short windows begin in March 2026. The vendor states that January holds only five scattered days and that continuous daily coverage starts 12 February 2026.

### Can I download the archive as files?

No. Bulk files, offline archive delivery, database replication and systematic archive mirroring are all excluded by the vendor's own description of the product. Everything comes through the metered REST API or the WebSocket.

### Is DepthFeed affiliated with Polymarket or Kalshi?

No. Its own footer describes it as an independent research project, not affiliated with or endorsed by Polymarket, Kalshi, Limitless, Binance or any exchange.

## Background

- [Where weather data comes from and what you may do with it](https://predictionmarkets.tools/guides/where-weather-data-comes-from.md) — Observations, model output and archives are three products with three licences. The forecast is the cheap half; a clean observation history is not.

- [Why the same contract costs two different prices on two venues](https://predictionmarkets.tools/guides/why-the-same-contract-costs-two-prices.md) — Two venues quoting one outcome are quoting two contracts. What the gap between the prices is made of - rules, fallbacks, fees, collateral, exits, eligibility.
- [What a trade actually costs on a prediction market](https://predictionmarkets.tools/guides/what-a-trade-actually-costs.md) — Venues publish trading fees in four incompatible units, so 3.00% on one can be cheaper than 1.75% on another. How to convert them, and what else takes a cut.

## Also worth comparing

- [Predexon](https://predictionmarkets.tools/tools/predexon.md) — Tick-level book history as Parquet, billed by the gigabyte, plus a mempool-aware feed.
- [PolyOrderbooks](https://predictionmarkets.tools/tools/polyorderbooks.md) — Recorded L2 books for Polymarket crypto markets, priced by how far back you may look.
- [Apify prediction-market scrapers](https://predictionmarkets.tools/tools/apify-prediction-market-scrapers.md) — A store of third-party actors that normalize Kalshi and Polymarket into one row shape.
- [FinFeedAPI Prediction Markets API](https://predictionmarkets.tools/tools/finfeedapi.md) — Nine event venues normalized into one REST schema, billed by usage credit.
- [Futuur API](https://predictionmarkets.tools/tools/futuur-api.md) — One question, two order books — play money and real money, selected per request.
- [Kalshi API](https://predictionmarkets.tools/tools/kalshi-api.md) — REST, WebSocket and FIX access to a CFTC-regulated event exchange.
