Research is a work in progress. Estimated release: 1 December 2026. Our goal is to make it a search engine for trading setups in recorded crypto markets.
Record coverage
Every tier searches the whole record. Monthly allowance and replay reach differ by tier.
Binance USDT-M record
Recording is ongoing. Dates are UTC; Binance live readings update throughout the day, while coils, bottoms and newer depth features currently have shorter searchable histories.
By venue
Binance USDT-M
Searchable
- Published range (UTC)
- 2025-07-15 to 2026-10-17
- Days
- 459
- Instruments
- 661
- Without excluded dates
- 368 instruments
- With excluded dates
- 293 instruments
Hyperliquid
Searchable via API/MCP
- Published range (UTC)
- 2026-07-22 to 2026-10-16
- Days
- 87
- Instruments
- 178
- Without excluded dates
- 175 instruments
- With excluded dates
- 3 instruments
Bybit
Research coming soon
Live terminal and replay available.
An excluded date is a day skipped for that instrument because required source data was missing or unreadable. Its other dates remain searchable.
These counts describe recorded exclusions. Even without exclusions, individual features or minutes can still be missing.
Cross-exchange research
Cross-exchange research is coming soon. Today, you can run separate studies on Binance and Hyperliquid over overlapping dates.
Hyperliquid uses exact API/MCP queries. Feature coverage varies; Binance account-positioning readings have no Hyperliquid equivalent.
Replay by tier
Binance order-book replay begins 2026-05-15. Replay windows depend on the venue’s recorded history and your tier.
| Tier | Tick replay reaches |
|---|---|
| Free | BTCUSDT, last 72h |
| Pro | 90 days |
| Research | The full recorded order book |
How coverage is counted
These figures are read from the research engine's instrument manifest at page load, not from remembered marketing copy.
A record scan runs over the whole coverage range above. No tier narrows how far back a search reaches; tiers differ in monthly search allowance and in replay depth.
On Binance USDT-M, Research extends replay access to the recorded order book, which begins 15 May 2026. Days before it are searchable (trades, candles, liquidations, open interest, funding) but hold no book, so they cannot be opened in the terminal on any tier. Free and Pro keep shorter replay windows.
- Top-level dataset_revision and feature_version describe Binance for compatibility. Each venue carries its own revision, feature version and engine notes.
- Venue ranges are the widest observed bounds and can contain gaps. Present partitions do not prove that every feature is available; check the exact query and dates.
- Hyperliquid exact API/MCP queries use identity.exchange = hl and recorded instrument IDs. Guided web research, replay links from research results and live monitoring are not supported for Hyperliquid.
- Bybit live terminal and recorded replay are available. Bybit historical research and combined cross-exchange queries are coming soon; they are not supported by the current query API.
- Binance live readings are published throughout the day. Coils, bottoms and newer depth features still depend on nightly extraction and are not yet included in the recent live record; their searchable history can stop before the overall range.
- coverage_to is EXCLUSIVE: the last included instant is immediately before it. The latest UTC day may be incomplete; this is not an end to recording.
- instruments_present and instruments_partial count instruments, not days: those without recorded excluded dates and those with at least one. A date is excluded for an instrument when required source data is missing or unreadable. Its other dates remain searchable; exclusions are reported in scan results. Neither count guarantees complete minute or feature coverage.
- Stocks, traditional indices, FX, commodities, gold-backed tokens and dated delivery contracts have been retired. Saved results remain historical; new studies and replay on these markets are unavailable.
- This document describes the research-queryable record. It is not an archive-completeness or data-quality statement and makes no claim about collection incidents.