Get Volatility Regime
GET/v1/cryptodata/volatility/regime
Per-asset realized-volatility regime across the SIGNUM_RGG universe. Each asset is classified into one of ``vol_shock``, ``expanding``, ``compressed``, ``mean_reverting``, or ``normal`` from realized vol (close-to- close, Parkinson, Garman-Klass) on daily klines. Each entry carries 7d/30d vol, the 90d vol percentile, term structure (7d/30d), and a vol-target position-size multiplier (``target_vol / current_vol``, capped). **Backfillable** — replayable from daily klines (unlike the intraday-only liquidity regime). The ``vol.rv_1h`` field is live-only and lands null on historically backfilled days. **``vol_target_multiplier`` is ABSOLUTE**: ``60 / rv_gk_30`` (close-to-close fallback) clamped to ``[0.25, 3.0]`` — not a percentile of the coin's own history. A coin with 30d vol >= 240% pins at 0.25 for as long as that holds (``vol.multiplier_at_floor``, ``vol.multiplier_floor_days``). For a **shock gate use ``vol.rv_z_7 >= 2``** (7d vol two sigmas above its own trailing 90d) or ``vol_pctile_7``; ``vol_shock`` itself is relative (7d GK at/above the 90th percentile of the coin's own 90d). A coin needs ``MIN_BARS`` = 40 daily bars to be classified. Rows whose candle fetch failed this cycle are carried over from the previous build (``stale_cycles`` > 0, max 8 cycles) rather than vanishing. Example screens: `?regime=compressed&sort=days_compressed` (longest dry tinder), `?regime=vol_shock` (acute spikes), `?sort=vol_target_multiplier& order=desc` (assets a vol-targeter would size up). **Tiers:** Free is scoped to BTC only; Pro / Pro Plus return the full universe.
Price
$0.01/ callEdge cache
300s
Uptime 24h
100.00%
p95
997ms
MCP tool
cryptodata_volatility-regime
Parameters
| Name | In | Type | Description |
|---|---|---|---|
| source | query | string (binance_spot | hyperliquid_perp) | |
| regime | query | string (vol_shock | expanding | compressed | mean_reverting | normal) | Filter by volatility regime |
| sort | query | string (symbol | rv_gk_30 | rv_gk_7 | vol_pctile_30 | term_structure_ratio | vol_target_multiplier) = vol_pctile_30 | |
| order | query | string (asc | desc) = desc | |
| limit | query | integer = 250 |
Code
# 1. No key, no payment: the gateway answers 402 with the price
curl -i "https://api.realtimeapi.ai/v1/cryptodata/volatility/regime"
# 2. Pay: retry with a signed x402 payment (any x402 client builds this header)
curl "https://api.realtimeapi.ai/v1/cryptodata/volatility/regime" -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/volatility/regime")).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/volatility/regime").json())curl "https://api.realtimeapi.ai/v1/cryptodata/volatility/regime" -H "X-API-Key: $RTAPI_KEY"Frequently asked questions
How do I get get volatility regime from CryptoDataAPI?
Send GET https://api.realtimeapi.ai/v1/cryptodata/volatility/regime. Pay $0.01 per request with x402, or send an X-API-Key header.
What does GET /volatility/regime 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.