Get Regime History
Committed long-horizon regime transitions over a window (Pro Plus).
/regimes publishes only what is committed right now, so the sequence that produced it could not be reconstructed from this API at all. Each entry here is one committed run: which regime, the exact instant it committed, when the next one replaced it, and how long it held.
committed_at is exact. It comes from the in_regime_since stamped at commit time and carried in every archived sample — not from the ~25-min sample that first observed the change. And because every committed regime is now protected by a minimum-dwell floor of at least 2h, no transition can hide between two samples.
Coverage starts 2026-08-07 and cannot be backfilled. The published regime is a stateful commit through the anti-churn dwell gate, not a pure function of the archived signals — replaying older inputs would produce a sequence that was never actually served. coverage_start reports the true start.
Not to be confused with /quant/regimes/history, which is the short-horizon 6-state HMM's hourly probability Parquet. This is the 10-state cycle model.
Request
- Base URL: https://cryptodataapi.com
- URL: https://cryptodataapi.com/api/v1/regimes/history
- Auth: API key in header X-API-Key
Query parameters
Window start, inclusive (ISO-8601 or unix ms). Defaults to 30 days ago.
Window end, EXCLUSIVE (ISO-8601 or unix ms). Defaults to now.
Max archive samples to scan (~57/day), not transitions returned.
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.