Get Technical Regime
GET/v1/cryptodata/indicators/technical
Technical / Structural regime overlay (Regime #14, Pro tier). Per-asset price-structure state across the same universe as SIGNUM_RGG: moving-average position (SMA-50/100/200 + last cross), Bollinger-band squeeze + bandwidth percentile, 20d range position, RSI(14) extremes on daily + 1h timeframes, and `sr` — up to 3 support + 3 resistance levels per side, from swing-high/low pivots on the daily series, nearest to current price first. A level's `strength` is how many pivots clustered into it; `dist_pct` is its signed % distance from mark (negative = support, positive = resistance). Levels further than 30% from mark are dropped as not actionable. ``breadth`` reports compression breadth over the FULL universe regardless of filters: ``{total, in_squeeze, pct_in_squeeze, pct_in_squeeze_pctile_30d, history_days}`` — the percentile ranks today's squeeze share against the last 30 archived daily values (null until 10 days are archived). Filter via `ma_state`, `bb`, `range_zone`, `rsi` (each is optional and AND-combined). Example screener queries: - `?bb=in_squeeze&sort=squeeze_days&order=desc` — assets compressed for longest - `?rsi=oversold&min_days_in_state=2` — sustained oversold candidates - `?ma_state=reclaim_200` — recent 200MA reclaims (last 10 days) - `?range_zone=near_high&ma_state=above_200` — near-range-high + uptrend - `?symbol=BTC,ETH,SOL` — just those assets (alias `coin`); any the universe does not cover are listed in `not_covered` Every series is DAILY (``ma`` carries SMA-20/50/100/200). An unrecognised query parameter (``interval``, say) is a 400, not a silently ignored filter; 4h / 1h ADX is ``/indicators/adx``.
Price
$0.01/ callEdge cache
300s
Uptime 24h
100.00%
p95
2.25s
MCP tool
cryptodata_indicators-technical
Parameters
| Name | In | Type | Description |
|---|---|---|---|
| source | query | string (binance_spot | hyperliquid_perp) | |
| ma_state | query | string (above_200 | below_200 | breakdown_200 | reclaim_200) | Filter by SMA-200 relationship |
| bb | query | string (in_squeeze | expanding) | Filter by Bollinger band state |
| range_zone | query | string (near_low | mid | near_high) | Filter by 20d range position |
| rsi | query | string (overbought | oversold | extreme) | Filter by daily RSI state |
| min_days_in_state | query | integer | Min days in state (squeeze or RSI extreme); requires matching filter |
| sort | query | string (symbol | price | rsi_1d | bb_bandwidth | squeeze_days | dist_from_200) = symbol | |
| order | query | string (asc | desc) = desc | |
| limit | query | integer = 250 | |
| symbol | query | string | Comma list of symbols to return (BTC,ETH,kPEPE); omit for the whole universe. Requested symbols the universe does not cover are listed in `not_covered`. |
| coin | query | string | Alias for `symbol`. Send one or the other. |
Code
# 1. No key, no payment: the gateway answers 402 with the price
curl -i "https://api.realtimeapi.ai/v1/cryptodata/indicators/technical"
# 2. Pay: retry with a signed x402 payment (any x402 client builds this header)
curl "https://api.realtimeapi.ai/v1/cryptodata/indicators/technical" -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/indicators/technical")).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/indicators/technical").json())curl "https://api.realtimeapi.ai/v1/cryptodata/indicators/technical" -H "X-API-Key: $RTAPI_KEY"Frequently asked questions
How do I get get technical regime from CryptoDataAPI?
Send GET https://api.realtimeapi.ai/v1/cryptodata/indicators/technical. Pay $0.01 per request with x402, or send an X-API-Key header.
What does GET /indicators/technical 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.