MKT CAP$2.23T-0.3%
24H VOL$71.6B
BTC DOM57.7%
HEALTH34BEARISH
SHORT-TERM50NEUTRAL
LONG-TERM19BEARISH
OI$47.0B-0.5%
24H LIQ$148M
LONG/SHORT58.8% / 41.2%
REGIME (LT)ESTABLISHED BEAR MARKET
REGIME (ST)SQUEEZE
HL OI$7.3B
WHALESSHORT 46.3%
MKT CAP$2.23T-0.3%
24H VOL$71.6B
BTC DOM57.7%
HEALTH34BEARISH
SHORT-TERM50NEUTRAL
LONG-TERM19BEARISH
OI$47.0B-0.5%
24H LIQ$148M
LONG/SHORT58.8% / 41.2%
REGIME (LT)ESTABLISHED BEAR MARKET
REGIME (ST)SQUEEZE
HL OI$7.3B
WHALESSHORT 46.3%
Plug real-time crypto data into your AI agent — one command: Get your free API key →
Get API KeyLogin
N8

n8n

Platform integration

Bring live crypto market data into n8n workflows — prices, funding, open interest, liquidations, market regimes, Fear & Greed, dealer gamma and whale activity — to power alerts, dashboards and AI-agent automations.

Two ways in: give an n8n AI Agent our MCP tools through the MCP Client Tool node (so the agent decides what to fetch), or call any endpoint deterministically with a plain HTTP Request node. Both authenticate with an X-API-Key header. The MCP server is documented on the MCP Server page.

Vendor · n8n MCP · http (streamable) Config · MCP Client Tool node → Endpoint + Header Auth credential Agent docs →
1

Connect via the MCP Client Tool node

Add an AI Agent node, then attach an MCP Client Tool sub-node. Set the transport to HTTP Streamable (SSE is deprecated; you need n8n 1.104+) and the endpoint to https://cryptodataapi.com/mcp.

For auth, create a Header Auth credential with name X-API-Key and value cdk_live_YOUR_KEY (the node also supports Bearer and multi-header credentials). The agent can now call any of our MCP tools as part of a workflow.

MCP Client Tool node
Transport:  HTTP Streamable
Endpoint:   https://cryptodataapi.com/mcp
Auth:       Header Auth credential
  Header name:  X-API-Key
  Header value: cdk_live_YOUR_KEY
2

Or call the REST API with an HTTP Request node

For deterministic pulls (no agent), use an HTTP Request node against any of our 180+ endpoints. Send your key as the X-API-Key header. Add ?format=markdown to many endpoints to get clean, LLM-ready text you can drop straight into a message node.

Example: fetch the whole-market snapshot to feed a scheduled report.

HTTP Request node
Method:  GET
URL:     https://cryptodataapi.com/api/v1/daily
Header:  X-API-Key: cdk_live_YOUR_KEY
3

Build an automation

A common pattern: a Schedule trigger every 15 minutes → HTTP Request to /api/v1/regimes (or the get_cycle_regime MCP tool) → an If node that checks whether the regime changed since the last run → a Slack or Telegram node that posts the alert. Mind the rate limits (Free 5/min) and the Cache-Control cadence — polling every 1–30 minutes is plenty.

Example prompts

“When the market regime flips, post a summary to our #trading Slack channel.”

“Every morning at 8am, send a Telegram message with the daily market snapshot.”

“If BTC funding turns sharply positive, alert me — it may signal crowded longs.”

“Log the Fear & Greed index to a Google Sheet every hour.”

“Watch for a spike in liquidations and DM me the top affected coins.”

FAQ

Does it cost anything?

No. The Free API tier (no card) covers market health, regimes, Fear & Greed, macro, flows, coin profiles and full-universe Hyperliquid funding + open interest — plenty for most alerts. Per-coin quant, gamma and whale signals need Pro.

MCP node or HTTP node — which should I use?

Use the MCP Client Tool node when an n8n AI Agent should decide which data to pull. Use the HTTP Request node for fixed, scheduled pulls where you already know the endpoint — it's simpler and fully deterministic.

The MCP node won't connect.

Confirm you're on n8n 1.104+ (older versions only have the deprecated SSE transport), that the transport is set to HTTP Streamable, and that the Header Auth credential sends X-API-Key with a valid cdk_live_ key. A 429 means you've hit the rate limit — slow the schedule down.

Was this page helpful?

Missing an agent, a config that changed, or a step that didn't work? Tell us and we'll fix it.