gex_veto Is a Rule, Not a JSON Key
The live board is https://cryptodataapi.com/quant-gamma.
The search is gex_veto gamma flip Hyperliquid. The page puts those words in the title. The tool is get_gamma_exposure. The REST call is GET /api/v1/quant/gex.
I am Sam Deering. I built this so an agent can read dealer positioning. Agents read. They do not trade. We are not a broker.
gex_veto is a rule. It is not a JSON key. When the regime flag reads amplify, dealer gamma is amplifying moves instead of damping them. Agents use that read as a gex_veto: stand down fresh longs until the flag clears.
The gamma flip is a price. Dealer inventory is a size. Confidence is a score. The veto follows the flag.
The Unique Fields
This is dealer positioning on Hyperliquid perps — the page calls it the perpetuals analog of options GEX. Perps have no strikes. It isolates market-maker accounts, then maps inventory, the gamma profile of forced-unwind clusters, and the gamma flip.
The live header on a recent fetch showed 3,564 accounts tracked and 224 classified dealers, a free preview of BTC, ETH and SOL on the page, and a 176-coin universe in the API. The page calls itself a 3-coin teaser.
- Gamma flip. The field is
gamma_flip: the price where market-maker long liquidations below the level cross short liquidations above it. It is capped to ±30% of mark — no in-band crossover meansnull. A dash on the card matches that null. A null flip is not zero. - Amplify versus dampen. The flag is
amplify,dampenortransitional.amplifyis a crowded book plus dense clusters near mark, so forced flow follows through.dampenis balanced and mean-reverting.transitionalsits on the flip line.gex_vetoties toamplifyonly. - MM inventory. The field is
mm_net_delta— aggregate long minus short across classified dealers in that coin. A heavy net-short book means makers lean against price and are exposed if it runs. Inventory is not the veto. - Dealer count. The header count is the classified dealer set; each coin card prints how many dealers sit in that coin. Count is sample size, not the stand-down.
- Confidence. The field is
regime.confidence, 0 to 1, scaling with market-maker account count and gross book so a thin sample is down-weighted. The veto rule itself does not set a cutoff — don't invent one.
The same call also carries gamma_profile, dist_to_flip_pct and distribution_context. Those are context. They are not gex_veto.
What the Board Showed
Fetched from /quant-gamma on 9 Sep 2026. The page says this preview is about 30 minutes delayed; the API is real-time. These figures are a dated read — a later call will differ.
| Coin | Mark | MM net inventory | Gamma flip | Dealers |
|---|---|---|---|---|
| BTC | $78,970.50 | SHORT $56,239,805 | $77,076.85 (−2.40%) | 104 |
| ETH | $2,491.15 | SHORT $189,173,754 | $1,982.31 (−20.43%) | 102 |
| SOL | $103.53 | SHORT $48,155,701 | $78.80 (−23.88%) | 72 |
| HYPE | $85.78 | LONG $46,386,182 | $65.32 (−23.86%) | 96 |
| XRP | $1.42 | SHORT $22,583,273 | $1.05 (−25.88%) | 71 |
| DOGE | $0.09 | SHORT $19,970,324 | — | 40 |
| SUI | $0.81 | SHORT $6,212,347 | $0.62 (−23.49%) | 55 |
| AVAX | $7.90 | SHORT $1,838,547 | — | 36 |
| LINK | $12.23 | SHORT $6,451,019 | — | 40 |
DOGE, AVAX and LINK showed a dash for gamma flip — a missing in-band crossover, not a veto by itself.
The same fetch printed trailing-30-day ranks: BTC was fuel density P89, flip distance P2, MM skew P71; ETH was P60, P54 and P94; SOL was P70, P72 and P49, each over 30.0 days. Percentiles stay null while status is warming (under 2 days). A study of forward returns on the flag is in progress — no measured lifts are published yet.
How to Read It
Read the regime flag first. If it is amplify, the gex_veto is on: stand down fresh longs until the flag clears. That is not the same as flipping short, and it does not mean closing every open long.
If the flag is dampen or transitional, the gex_veto is not on.
Then read gamma_flip as the level, and mm_net_delta as the lean. A coin can have a flip and still not be in amplify. A coin can have a null flip and still show amplify. The stand-down follows the latest flag, not the flip price.
The board also pastes a strategy prompt — fade extremes above the flip, follow momentum below it. That is a test idea, not a second name for gex_veto. Quote the flag for the veto. Quote the flip as the level.
What the Fields Are Built From
This is a behavioral analog, built from the on-chain liquidation price of every classified dealer account at or above $100k.
gamma_profile is a liquidation-density histogram: bins are 0.5% of mark, over ±50%. Tall bars are forced-unwind clusters — it answers how much notional is force-unwound if price reaches a level, not the probability that price reaches that level.
The liquidation map is archived every 5 minutes. gamma_exposure snapshots start 6 Jul 2026. The composite regime flag (amplify/dampen/transitional) went live 27 Jun 2026. Positioning is point-in-time — it is not backfillable.
What gex_veto Is Not
GET /api/v1/quant/gex returns mm_net_delta, gamma_profile, gamma_flip and a composite regime flag. It does not return a key named gex_veto. The MCP tool get_gamma_exposure maps to that same endpoint and does not expose that key either.
It is not the flip price. It is not dealer inventory. It is not dealer count. It is not regime.confidence. It is not a buy signal. It is not listed options GEX. It is not financial advice.
A short stub for this query also names a field called fuel_side. That name does not appear on the live page, the /quant/gex docs, or llms.txt — it is not in this read.
How an Agent Should Call It
get_gamma_exposure is Pro. The remote MCP server is https://cryptodataapi.com/mcp. Do not start with a candle poll — bars cannot tell you whether dealer gamma is amplifying.
Start with list_capabilities. Mint a key with create_free_api_key only if you lack one, then confirm that email — confirming lifts the same key from 100 to 1,000 requests a day and switches Pro on for 24 hours. Then call get_gamma_exposure, which is GET /api/v1/quant/gex?symbol=BTC for one coin.
Read the regime flag. If it is amplify, say the gex_veto is on; if it is dampen or transitional, say it is not. Then report gamma_flip and mm_net_delta as separate fields, then dealer count and regime.confidence if the payload includes them. If gamma_flip is null, do not invent a level. If the payload has no key named gex_veto, do not fake one.
A 403 on /quant/gex is the expected free-tier answer — the body carries required_tier and pricing_url. Read it, don't retry it. A different 403 is HTML from Cloudflare: Python's default urllib User-Agent is refused before the API sees the call, so set a named User-Agent.
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"A sibling Pro view is GET /api/v1/quant/positioning, which splits notional by market_maker, whale, other and all — the market-maker bucket is the dealer book behind /quant/gex.
Live full-universe GEX is Pro. Archived gamma_exposure snapshots are Pro Plus, via GET /api/v1/backtesting/snapshots?data_type=gamma_exposure. Pro is 30 requests a minute and 10,000 a day; a 429 carries Retry-After.
What the Key Costs
The free tier needs no card. A new key starts at 100 requests a day until the email is confirmed, then 1,000 a day.
Pro is $39 a month, or $29 a month billed annually ($348 a year). Pro Plus is $129 a month, or $99 a month billed annually ($1,188 a year). An agent can subscribe with POST /api/v1/payments/agent-subscribe — monthly is Pro, monthly_plus is Pro Plus. Read the amount from the HTTP 402 body.
Checklist
- Open /quant-gamma or call
get_gamma_exposure. - Read the regime flag before you read the flip.
amplifymeans thegex_veto— stand down fresh longs until the flag clears.dampenandtransitionalare not the veto.gamma_flipis the price;mm_net_deltais dealer inventory. Count and confidence say how thin the read is.- If the payload has no key named
gex_veto, do not fake one.
Not financial advice. It is data.
