Get Adx
GET/v1/cryptodata/indicators/adx
ADX(14) + DMI per asset on daily, 4h or 1h bars (Pro tier). The same Wilder ADX/+DI/-DI the SIGNUM trend radar colours from, served as numbers per interval: ``interval=1d`` matches ``/indicators/signum-rgg`` ``adx``, ``4h`` its ``h4_adx`` (completed bars on the UTC 00/04/08/12/16/20 grid of ``/hyperliquid/candles?interval=4h``) and ``1h`` its ``intraday_adx``. Recomputed hourly (:05 UTC) for the whole universe, so a universe-wide read costs nothing. Per row: ``adx``, ``plus_di``, ``minus_di``; ``direction`` (+DI vs -DI); ``strength`` against SIGNUM's bands (``strong`` >= 25, ``weak`` < 20); ``color`` (the SIGNUM state on that interval); ``bar_open`` and ``final``. A row whose interval read is unavailable (too few bars, or a stale intraday series) carries nulls and sorts last. ``history=N`` attaches the last N completed bars per row. For 4h and 1h that is a live candle pull per symbol (memoised 30 minutes), so it needs ``coin`` with at most 5 symbols. An unrecognised query parameter is a 400. Example gates: ``?coin=BTC&interval=4h`` -> ``items[0].adx > 25``; ``?interval=1d&min_adx=25&source=hyperliquid_perp`` -> every trending HL perp.
Price
$0.01/ callEdge cache
300s
Uptime 24h
100.00%
p95
1.31s
MCP tool
cryptodata_indicators-adx
Parameters
| Name | In | Type | Description |
|---|---|---|---|
| coin | query | string | Comma list of symbols (BTC,ETH,kPEPE); omit for the whole universe. Symbols the universe does not cover are listed in `not_covered`. |
| symbol | query | string | Alias for `coin`. Send one or the other. |
| interval | query | string (1d | 4h | 1h) = 1d | Bar width: 1d and 4h read COMPLETED bars; 1h includes the bar forming at the hourly sweep (`final: false`) |
| source | query | string (binance_spot | hyperliquid_perp) | |
| min_adx | query | number | Only rows with adx >= this |
| history | query | integer = 0 | Attach the last N completed bars per row (1d: up to 60; 4h: up to 90; 1h: up to 500). 4h/1h history needs `coin` with at most 5 symbols. |
| sort | query | string (adx | symbol) = adx | |
| order | query | string (asc | desc) = desc | |
| limit | query | integer = 250 | |
| offset | query | integer = 0 |
Code
# 1. No key, no payment: the gateway answers 402 with the price
curl -i "https://api.realtimeapi.ai/v1/cryptodata/indicators/adx"
# 2. Pay: retry with a signed x402 payment (any x402 client builds this header)
curl "https://api.realtimeapi.ai/v1/cryptodata/indicators/adx" -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/adx")).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/adx").json())curl "https://api.realtimeapi.ai/v1/cryptodata/indicators/adx" -H "X-API-Key: $RTAPI_KEY"Frequently asked questions
How do I get get adx from CryptoDataAPI?
Send GET https://api.realtimeapi.ai/v1/cryptodata/indicators/adx. Pay $0.01 per request with x402, or send an X-API-Key header.
What does GET /indicators/adx 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.