We're building the most comprehensive crypto data API we can, and it's still growing — there's always a coin, a field or an endpoint we haven't got to yet.
Please tell us about any data you think Crypto Data API should nail but doesn't. We're data nerds who love to geek out about market data, trading bots, AI agents, or how to make your trading stack work in general. Prefer a form? Send feedback.
— Sam and the CDA team
Join us on DiscordA forward calendar of dated catalysts — token unlocks, macro prints (FOMC/CPI/NFP/PCE/PPI), stablecoin depegs and mint/burn steps — each scored with a directional bias (long, short, neutral or risk flag) and a 0–1 magnitude. They roll up into the market-wide Event Risk verdict shown at right.
A macro print is always shown with a risk flag bias, not long or short — the direction of a surprise CPI or NFP print is unknown ahead of time, so it raises event risk without a directional lean. Depegs and mint/burn steps are observed, not scheduled, so they can carry a "days ago" date rather than a countdown.
curl -H "X-API-Key: cdk_live_yourkey" \ "https://cryptodataapi.com/api/v1/event/regime?window_days=7"
curl -H "X-API-Key: cdk_live_yourkey" \ "https://cryptodataapi.com/api/v1/event/calendar?window_days=30&type=unlock"
/event/regime returns the calendar plus the market-wide Event Risk score; /event/calendar is the filterable form (by type, symbol, bias, min_magnitude, up to 30 days out). Both are open to any valid key — free tier included, no Pro gate on the calendar itself. The per-symbol overlay (/event/regime/{symbol}) and forced refresh are Pro / Pro Plus. See the event regime docs.
An event calendar is forward-looking, which makes it impossible to reconstruct honestly after the fact — vesting schedules get revised, and prints roll off the board once they happen. So the whole event board is snapshotted daily: what was dated, how big it scored, and what the Event Risk composite read — as published on each day. That point-in-time record is what an event study actually needs.
curl -H "X-API-Key: cdk_live_yourkey" \ "https://cryptodataapi.com/api/v1/backtesting/snapshots?data_type=token_unlocks&start=2026-08-20"
Snapshot series start the day they shipped and grow forward — a schedule that was never recorded cannot be recovered later. The live /event/calendar stays the right call for "what is coming"; the archive answers "what did we know, and when".
Working guides and live data pages that pair with this one — each maps a question an agent actually asks to the exact call that answers it.
Dilution overhang and the forward unlock cliff calendar by coin.
How the event-regime verdict on this page is scored, and how to query it.
Pull dated unlocks from the API, cliff by cliff.
Every >=$100k account's positioning, net bias and per-coin conviction.
The committed long-horizon cycle regime and the 14 regime baskets.
This calendar is 0.008 USDC per call over x402 with no key, or free with any key.
Pro unlocks every coin on the quant surfaces — whale positioning, dealer gamma (GEX), short-horizon regime probabilities, L2 order-book depth and full-universe funding — on the same key you already hold.
AI agents: subscribe key-in-hand with no browser and no card —
POST /api/v1/payments/agent-subscribe
(x402 gasless USDC on Base, Ethereum or Solana; call it once for the 402 payment instructions, sign, call again).