ZAMAUSDT · historical base rate

One-sided tape: buyers on ZAMAUSDT

Taker buy ratio over the last 15 minutes has run at 0.62 or more: a persistently buyer-heavy tape.

What has happened on ZAMAUSDT when it held

Historically, when One-sided tape: buyers on ZAMAUSDT held (355 occurrences in the scanned window, 333 with a computable 24h horizon), the market reached +5% within 24h in 126 of 333 (37.8) and drew down 10%+ in 15 of 333 (4.5). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

Outcome distribution

WHAT FOLLOWED · ALL 355 MATCHES

101 of 343 (29.4%) reached +1% or more within 1 hour · smallest move size with matches, picked for you

Pick a window and a move size: how often did a move at least that big follow?

WINDOWMOVE SIZE

🔒 Measured after every match, never by keeping winners. 343 of the matches have a complete 1 hour forward; the other 12 are too recent to know.

What are MFE and MAE?

When they happened - one bar per UTC day, all 355 matches

About 11 a day, on 29 of 31 days: spread through the record rather than one event.

Where the next 30 minutes landed - 338 measured, 17 too recent

Forward 30-minute returns across 338 matches: 57% of them finished up.

How to read a distribution

Upside reached · 24hThe most price moved up within 24h of each occurrence: a high-water mark, never a close. 333 with a complete 24h.

Drawdown · 24hThe worst price moved against within 24h of each occurrence: the deepest point, never the close. 333 with a complete 24h.

Versus baseline

Historically, when any eligible ZAMAUSDT minute in the window (baseline) held (36,231 occurrences in the scanned window, 34,556 with a computable 24h horizon), the market reached +5% within 24h in 15,869 of 34,556 (45.9) and drew down 10%+ in 2,391 of 34,556 (6.9). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

The full record

The same setup counted over every recorded day on ZAMAUSDT (2026-05-15 to 2026-08-01), growing daily.

Historically, when One-sided tape: buyers on ZAMAUSDT over the full record held (703 occurrences in the scanned window, 678 with a computable 24h horizon), the market reached +5% within 24h in 253 of 678 (37.3) and drew down 10%+ in 24 of 678 (3.5). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

WHAT FOLLOWED · ALL 703 MATCHES

194 of 688 (28.2%) reached +1% or more within 1 hour · smallest move size with matches, picked for you

Pick a window and a move size: how often did a move at least that big follow?

WINDOWMOVE SIZE

🔒 Measured after every match, never by keeping winners. 688 of the matches have a complete 1 hour forward; the other 15 are too recent to know.

What are MFE and MAE?

When they happened - one bar per UTC day, all 703 matches

About 8.9 a day, on 56 of 79 days: spread through the record rather than one event.

Where the next 30 minutes landed - 681 measured, 22 too recent

Forward 30-minute returns across 681 matches: close to an even split, which is what a coin flip looks like.

How to read a distribution

Check our work: the key that re-runs this exact count (q#059da5b8)

grammar: research_query.v2
normalization: archive_normalization.v1
feature library: feature_defs.v1
dataset revision: ce3b6253b51706f7a4c0e4a553e0dd67fcf76395dd1a8717eccda70dad520d60
query hash: 059da5b8cde888aa5e7bd929113160dc3f54e87609485fdc31fd470648a413b5
scanned window: 2026-07-02T00:00:00.000Z to 2026-08-01T00:00:00.000Z (UTC)

Same key, same bytes. This receipt reruns; it does not retell. When the record grows, the dataset revision changes and says so.

Re-run this yourself, over the API or from an AI agent

This is the exact search definition behind the receipt. Send it to the key-authed research API (or the MCP research tool) and compare the bytes: a cached rerun is free.

{
  "schema_version": "research_query.v2",
  "normalization_version": "archive_normalization.v1",
  "feature_version": "feature_defs.v1",
  "target": "record_occurrences",
  "where": {
    "all": [
      [
        "feature.taker_buy_ratio_15m",
        "gte",
        0.62
      ],
      [
        "identity.symbol",
        "eq",
        "zamausdt"
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-07-02T00:00:00.000Z",
          "2026-08-01T00:00:00.000Z"
        ]
      ]
    ]
  },
  "sort": [
    "times.anchor_time",
    "desc"
  ],
  "page": {
    "limit": 50,
    "cursor": null
  }
}

curl -s https://app.edgedepth.com/api/v1/research/query \
  -H 'authorization: Bearer $EDGEDEPTH_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"schema_version":"research_query.v2","normalization_version":"archive_normalization.v1","feature_version":"feature_defs.v1","target":"record_occurrences","where":{"all":[["feature.taker_buy_ratio_15m","gte",0.62],["identity.symbol","eq","zamausdt"],["times.anchor_time","between",["2026-07-02T00:00:00.000Z","2026-08-01T00:00:00.000Z"]]]},"sort":["times.anchor_time","desc"],"page":{"limit":50,"cursor":null}}'

How to read this

Counts ship with denominators: occurrences across the eligible symbol-buckets scanned. A rate is over the occurrences with a computable horizon (present), never the total.
Absent is absent. When a feature was not warm at a minute, that bucket leaves the denominator and is reported; it is never coerced to zero.
This selects a setup, never its outcome. The grammar forbids filtering on what followed (OUTCOME_IN_PREDICATE), so the distribution below is over every occurrence, not a survivorship-picked subset.

Occurrences are observed examples in a selected archive, not a guarantee. Outcomes are computed forward from each anchor and are descriptive, never a filter and never a prediction. Nothing here is trading advice.

Everything measured on ZAMAUSDT right now: the ZAMAUSDT research page