Get Regime History
GET/v1/cryptodata/regimes/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.
Price
$0.01/ callEdge cache
300s
Uptime 24h
100.00%
p95
2.29s
Parameters
| Name | In | Type | Description |
|---|---|---|---|
| from | query | string | Window start, inclusive (ISO-8601 or unix ms). Defaults to 30 days ago. |
| to | query | string | Window end, EXCLUSIVE (ISO-8601 or unix ms). Defaults to now. |
| limit | query | integer = 5000 | Max archive samples to scan (~57/day), not transitions returned. |
Code
# 1. No key, no payment: the gateway answers 402 with the price
curl -i "https://api.realtimeapi.ai/v1/cryptodata/regimes/history"
# 2. Pay: retry with a signed x402 payment (any x402 client builds this header)
curl "https://api.realtimeapi.ai/v1/cryptodata/regimes/history" -H "PAYMENT-SIGNATURE: $X402_PAYMENT"// npm i @x402/fetch @x402/core @x402/evm viem
import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { ExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
const client = x402Client.fromConfig({ schemes: [{ network: "eip155:8453", client: new ExactEvmScheme(privateKeyToAccount(PRIVATE_KEY)) }] });
const pay = wrapFetchWithPayment(fetch, client);
const data = await (await pay("https://api.realtimeapi.ai/v1/cryptodata/regimes/history")).json();
console.log(data);# pip install x402 eth-account requests
from eth_account import Account
from x402.clients.requests import x402_requests
session = x402_requests(Account.from_key(PRIVATE_KEY))
print(session.get("https://api.realtimeapi.ai/v1/cryptodata/regimes/history").json())curl "https://api.realtimeapi.ai/v1/cryptodata/regimes/history" -H "X-API-Key: $RTAPI_KEY"Frequently asked questions
How do I get get regime history from CryptoDataAPI?
Send GET https://api.realtimeapi.ai/v1/cryptodata/regimes/history. Pay $0.01 per request with x402, or send an X-API-Key header.
What does GET /regimes/history cost?
$0.01 per successful request in USDC on Base. Failed requests are never charged.
Can I call this endpoint from an MCP client?
Yes. Connect any MCP client to the RealtimeAPI server and use call_feed with this endpoint's URL, or get_quote to check the price first.