What It Is

The live board is https://cryptodataapi.com/quant-gamma. The search is distribution_context. The page prints that block under “Today's reading, in context.” The MCP tool is get_gamma_exposure. The REST call is GET /api/v1/quant/gex?symbol=BTC.

I am Sam Deering. I built this so an agent can rank today's dealer read against the coin's own history. Agents read. They do not trade. We are not a broker.

Every /quant/gex coin carries a distribution_context block.

The page says a raw density number means little on its own. A percentile of the last 30 days is the actionable form. The block ranks the coin against its own trailing history. It is archived point in time inside the gamma_exposure snapshots.

The API docs for GET /api/v1/quant/gex name the same block. They say it ranks near-mark cluster density, absolute distance to flip, normalized market-maker skew (mm_net_delta / mm_gross), regime score, and funding rate. They say honesty fields ride with it: history_days, sample_count, and status. Every *_pctile stays null while status is warming (under 2 days of hourly samples). meta.distribution_legend documents each field.

The exact field names, per that legend: near_density_pctile, abs_dist_to_flip_pctile, mm_skew_pctile, regime_score_pctile, and funding_rate_pctile.

The page preview prints three of those ranks as labels: fuel density, flip distance, and MM skew. It also prints how many days of history exist. Read those labels as the board's reading. Do not invent extra JSON keys the live body has not shown you.

This block is history context. It is not the flip price. It is not the amplify stand-down.

Where to See It

Open https://cryptodataapi.com/quant-gamma. Scroll to “GEX probability distribution” / “Today's reading, in context.”

The human page is a free launch preview. The page says the preview is about 30 minutes delayed. The API is real-time.

The REST path is Pro:

curl -H "X-API-Key: cdk_live_your_key" \
  -H "User-Agent: cryptodataapi-python/1.0" \
  "https://cryptodataapi.com/api/v1/quant/gex?symbol=BTC"

The MCP tool that maps to that path is get_gamma_exposure. That name is on https://cryptodataapi.com/ai-agents/mcp-server.

The archive call is GET /api/v1/backtesting/snapshots?data_type=gamma_exposure. The page dates gamma_exposure snapshots to 6 Jul 2026. The regime layer starts 26 Jun 2026. Positioning is point in time. None of that history is backfillable. The dataset is forward-only and grows every week.

How to Read It

Read history_days first. Then read status. If status is warming, expect every *_pctile to be null. Say how much history exists and stop. Do not invent a percentile.

When the history is warm, read the ranks the page prints:

  1. Fuel density — near-mark cluster density versus the coin's own last 30 days.
  2. Flip distance — absolute distance to the gamma flip versus that same window.
  3. MM skew — normalized dealer skew versus that same window.

The docs also rank regime score and funding rate inside the same block. The free preview cards on this fetch printed fuel density, flip distance, MM skew, and the day count. They did not print regime-score or funding-rate percentiles on the HTML cards. Do not invent those card values.

A high fuel-density percentile means today's near-mark forced-flow fuel is high versus this coin's recent self. A low flip-distance percentile means mark is unusually close to the flip versus recent self. A skew percentile ranks how one-sided the dealer book is versus recent self.

Do not treat a percentile as a price target. The page says the gamma profile is a distribution of forced flow by price level. It answers how much notional is force-unwound if price reaches a level. It does not answer the probability that price reaches that level. Perps have no strikes. There is no implied-distribution shortcut.

The same section describes a second study: conditional forward distributions. Does amplify precede fatter-tailed moves? The page says that test measures forward return, realized vol, and tail distributions, conditioned on the regime flag, pooled across the full perp universe, against a volatility-matched null. The page marks that study as in progress. Measured lifts, confidence intervals, and sample sizes are not published yet. Do not quote it as a measured edge.

What It Is Not

This is not gex_veto. gex_veto is the amplify stand-down. When the regime flag reads amplify, agents stand down fresh longs until the flag clears. That rule is a sibling post: it is not this one. gex_veto is not a JSON key. Do not invent a boolean.

This is not the gamma_flip price alone. gamma_flip is the price where MM long-liquidation-below crosses short-liquidation-above — the inflection. The docs cap it to ±30% of mark. No in-band crossover means null.

This is not gamma_profile. That histogram uses 0.5%-of-mark bins over ±50%. Tall bars are forced-unwind clusters.

This is not the HMM market-regime object on /quant/market. That engine is a different head. Do not collapse percentile ranks into HMM posteriors.

This is not candles. Bars cannot tell you where today's dealer density sits in the coin's own 30-day history.

The free preview is BTC, ETH, and SOL. The API universe is 176 coins. A locked coin on the public board is not a missing field. The page locks the rest of the universe behind Pro.

What the Board Showed

Fetched from https://cryptodataapi.com/quant-gamma on 10 Sep 2026, morning Brisbane time (AEST, UTC+10). The page says this preview is about 30 minutes delayed. The API is real-time. These figures are a snapshot of that one page load — a later call will differ.

Header on this fetch: 3,522 accounts tracked. 223 classified dealers. Free preview BTC · ETH · SOL. 176-coin universe in the API.

Trailing-30-day ranks the page printed under distribution_context:

CoinFuel densityFlip distanceMM skewHistory
BTCP79P1P9030.0d
ETHP99P91P9430.0d
SOLP71P16P5630.0d

All three coins showed 30.0 days. That is past the warming window. Percentiles are readable.

For orientation only, the same fetch showed BTC mark $77,944.50, gamma flip $77,119.45 (−1.06%), and MM net inventory SHORT $13,228,522 across 107 dealers on the BTC card. Those card fields are not the distribution_context block. They sit beside it. Read the ranks for history context. Read the flip and the regime flag as separate fields.

ETH on the same fetch was fuel density P99 with flip distance P91. Near-mark fuel was extreme versus ETH's own month. Distance to flip was also high versus that month. Do not collapse those two ranks into one story.

SOL was fuel density P71, flip distance P16, MM skew P56. Mid fuel. Close to its own recent flip-distance distribution. Skew near the middle of its month.

One Concrete Live Example

Call GET /api/v1/quant/gex?symbol=BTC.

Read the BTC coin's distribution_context block.

  1. Read history_days. On the page preview it was 30.0.
  2. Read status. If it is warming, stop.
  3. Read the fuel-density rank. On this fetch the page printed P79.
  4. Read the flip-distance rank. On this fetch the page printed P1.
  5. Read the MM-skew rank. On this fetch the page printed P90.
  6. Then read gamma_flip and the regime flag as separate fields. Do not treat P79 as a price. Do not treat P1 flip distance as a stand-down. The stand-down is the amplify rule on the sibling post.

I called the REST path in this session with a named User-Agent and no key. HTTP 401. Body error: api_key_required. Message pointed at POST /api/v1/auth/keys. I did not invent a payload. I did not copy a percentile out of the 401.

A second call with an invalid X-API-Key also returned HTTP 401. Body error: invalid_api_key. That is still not a Pro payload.

For Agents: MCP Tool Order

Call get_gamma_exposure when the user asks for distribution_context.

Do not open get_order_book for this query. The book is a different page.

Do not open with a candle poll. The MCP page says bars cannot tell you what regime you are in. They also cannot tell you a 30-day fuel-density rank.

Tool order:

  1. list_capabilities — no key needed.
  2. create_free_api_key — only if you lack a key. Use a real email.
  3. Confirm that email. Confirming lifts the same key from 100 to 1,000 requests a day and switches Pro on for 24 hours.
  4. get_gamma_exposure — Pro. Maps to GET /api/v1/quant/gex.
  5. Read distribution_context on the coin. Read history_days and status before any percentile.
  6. If percentiles are null, report the honesty fields and stop.
  7. If percentiles exist, report the ranks. Then report gamma_flip and the regime flag as separate fields.

A 403 on that tool is the expected free-tier gate. The MCP page says that gate is expected on Free. Read the body. Do not retry it. The docs say a JSON 403 carries required_tier and pricing_url. A different 403 is HTML from the CDN. Python's built-in urllib is refused before the API sees the call. Set a User-Agent that names your client.

Backtesting snapshots are not on the MCP tool list. Use REST for GET /api/v1/backtesting/snapshots?data_type=gamma_exposure. That path is Pro Plus.

REST

curl -H "X-API-Key: cdk_live_your_key" \
  -H "User-Agent: cryptodataapi-python/1.0" \
  "https://cryptodataapi.com/api/v1/quant/gex?symbol=BTC"

Omit symbol for the full universe on Pro. The page says 176 coins in the API. The free HTML preview is three coins.

Archive:

curl -H "X-API-Key: cdk_live_your_key" \
  -H "User-Agent: cryptodataapi-python/1.0" \
  "https://cryptodataapi.com/api/v1/backtesting/snapshots?data_type=gamma_exposure&start=2026-07-06&limit=1000"

The page says the archived map includes the full gamma profile per coin: flip level, distribution context, and regime flag.