Get Regimes

GET/v1/cryptodata/regimes

The 10-state long-horizon regime model + the current detected regime. ``regimes`` is the stable taxonomy (id, machine ``regime`` id, display name, description, typical duration and directional bias). ``current`` is the live classification with a ``rationale``, the inspectable ``signals`` that drove it, and — where applicable — an internal ``stage`` (Distribution) or ``euphoria_score`` (Speculative Euphoria). **Committed vs live.** ``current.regime``/``id``/``name``/``rationale`` are the COMMITTED regime: an anti-churn dwell gate holds it until a new candidate is the raw classification for ``pending.needed`` consecutive refreshes. But ``signals`` are always read fresh, so mid-turn they can stop supporting the committed regime — that is expected, not stale data. ``current.raw`` gives the live ungated classification and ``raw.matches_committed`` tells you the two disagree; ``current.pending`` shows how far the successor has confirmed. **Stability.** ``pending`` is null whenever the live read already agrees with the committed regime — correct, but it means a consumer watching for a turn sees a field that blinks in and out. ``current.stability`` is always present and always numeric: ``raw_agreement`` decays as conditions drift, ``confirmations_against``/``needed`` track a successor, and ``locked_for_s`` is the HARD number — how long the dwell floor mechanically guarantees the committed regime survives. ``current.thresholds`` gives the distance from every numeric cutoff in the cascade to flipping, so hysteresis can be built on published boundaries instead of guesses. ``typical_duration`` describes the real-world cycle phase, NOT a guaranteed dwell — but the dwell floor is now SCALED to it: a "Weeks-Months" state (#2/#4/#6/#8) must be held 48h before anything may replace it, "Weeks" 24h, "Days-Weeks" 12h, and #1 Structural Shock only 2h because it is an emergency override. Read the live value from ``stability.dwell_floor_s``. ``/regimes/history`` returns the committed transition sequence.

# 1. No key, no payment: the gateway answers 402 with the price
curl -i "https://api.realtimeapi.ai/v1/cryptodata/regimes"

# 2. Pay: retry with a signed x402 payment (any x402 client builds this header)
curl "https://api.realtimeapi.ai/v1/cryptodata/regimes" -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")).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").json())

curl "https://api.realtimeapi.ai/v1/cryptodata/regimes" -H "X-API-Key: $RTAPI_KEY"