RECORDED BINANCE MARKETS
862
Research · Order flow · Replay
See the move.
Test the idea.
Study the buildup to a move. Test the setup against recorded history. Then inspect the order flow and replay the moments that matter.
Binance USDT-M perpetuals, from majors to smaller markets.
Historical coverage varies by market and stream.
SEARCHABLE RECORD
421 DAYS
SEARCH GRID
1 MINUTE
REPLAY EVIDENCE
TICK LEVEL
THE PRODUCT, WITHOUT THE SALES FOG
Six boundaries that define EdgeDepth.
The left column is what the product does today. The right column names the nearby product it refuses to pretend to be.
| Capability | EDGEDEPTH | NOT EDGEDEPTH |
|---|---|---|
| Purpose | Research the market that was actually recorded. State a condition, count every occurrence, measure what followed and decide whether the evidence deserves more work. | Not a signals room, prediction service or promise that a historical pattern will repeat. |
| The record | The recording is already there. Binance USDT-M, Hyperliquid and Bybit perpetuals captured continuously across trades, books, liquidations, funding, open interest and positioning. | Not a local recorder that begins building history only after you install it or press record. |
| Search | Plain words become fixed, inspectable conditions. 58 versioned measurements on a one-minute grid, searched across 862 Binance USDT-M crypto and TradFi perpetuals. | Not tick-level search, an opaque similarity score or a model inventing a measurement the record does not contain. |
| Answer | Every rate carries its count and its reference population. The result shows how many occurrences matched, how many outcomes were measurable, what followed and the exact scope searched. | Not a percentage detached from its denominator, a hand-picked example or a single average hiding the distribution. |
| Evidence | Open the exact occurrence in replay. Move from the population to the recorded trades and reconstructed order book at any representative or contradictory match. | Not a chart screenshot or an anecdote that cannot be checked against the underlying tape. |
| Control | The method is reproducible and the account is read-only. Versioned definitions and result IDs make the work repeatable through the site, REST API or MCP. No exchange keys are requested. | Not execution, custody, auto-trading, or a result that changes because a person or AI prefers a different answer. |
ONE WORKFLOW
From a question to evidence you can inspect.
The product is one loop over one recorded market, not a collection of unrelated tools.
- >Describe a market condition in plain words
- >Confirm the exact definition and scope
- >Count every occurrence and what followed
- >Open representative and contradictory evidence in replay
- >Re-test, practise or alert on the same definition
ACCESS LADDER
Watch now. Rewind history. Interrogate the full record.
Each paid step removes a concrete limit rather than replacing the product.
- >Free: use basic live charts, DOM and tape, replay the Free day and run 10 research credits a month
- >Pro: use advanced live order flow, replay 90 days across all recorded pairs and run 50 research credits a month
- >Research: search the full verified research record and replay the recorded order book (from 15 May 2026) with 300 research credits a month
THE PRECISE VERSION
Exact claims for people and machines quoting this page.
- Markets searchable today: 862 Binance USDT-M crypto and TradFi perpetuals, including perpetuals tracking Nvidia, Tesla, AMD, QQQ, gold, silver and oil. TradFi references are USDT-settled perpetuals tracking those markets, not primary-exchange feeds.
- Hyperliquid: Hyperliquid historical data has been backfilled and recorded Hyperliquid replay covers about six weeks so far. Hyperliquid historical research is not yet publicly available; derived data and coverage must be validated before release.
- Cross-exchange: Cross-exchange research is in the works, and results will always say which venue they came from before any Binance-to-Hyperliquid comparison is allowed.
- Measurements: 58 fixed features per market per minute, spanning price action, order-book shape, flow, liquidations, open interest, funding and positioning. The list is closed and versioned; a question outside it is refused with a named error, not approximated.
- Every result carries: the count, how many chances it had, forward outcomes over the completed matches at the horizons available in that result, missing-outcome counts, and the definition and data revision used.
- Replay: recorded trades and order-book updates within the rolling 90 days Pro window, subject to market and stream coverage. Archived events are preserved; access depends on the event and plan.
- Access: directly on the site, over REST, or through the MCP server. Free accounts receive 10 research credits a month, over the whole searchable record.
Ask the record something measurable.
PLAIN WORDS · EXACT DEFINITION · EVERY MATCH
FAQ
EdgeDepth, stated plainly.
Is EdgeDepth tick-level?
Search and replay answer differently, on purpose. Search works on a one-minute grid: every minute of every covered market is measured 58 fixed ways, and those measurements are what you search. Replay shows recorded trades and reconstructed order-book updates. Depth is sampled; available history varies by market and stream.
Which markets can I search?
862 Binance USDT-M crypto and TradFi perpetuals, including perpetuals tracking Nvidia, Tesla, AMD, QQQ, gold, silver and oil. Hyperliquid historical data has been backfilled and recorded Hyperliquid replay covers about six weeks so far. Hyperliquid historical research is not yet publicly available; derived data and coverage must be validated before release. Cross-exchange research is in the works, and results will always say which venue they came from before any Binance-to-Hyperliquid comparison is allowed.
Can EdgeDepth trade for me?
No. EdgeDepth never connects to an exchange account, never asks for exchange keys, and never executes, transfers or holds anything. It is read-only by design: it measures what happened, and the decision stays yours.
How is this different from a backtester?
A backtester scores a strategy you already wrote. EdgeDepth counts every time a stated condition happened and reports what followed over all of it: the count, how many chances it had, and the full spread of forward outcomes rather than a single average. It also refuses the step that quietly breaks most backtests: you cannot filter to the matches that later went up.
Why does every result have an ID?
Keep the query ID, definition, data revision and original result together. They identify what was tested. A new run against a later revision can differ; a query ID alone does not freeze the answer.
MORE COMPARISONS