What an AI agent gets from CryptoDataAPI MCP that candle AI APIs miss

Start here: https://cryptodataapi.com/ai-agents and https://cryptodataapi.com/mcp. MCP human docs for the same product: https://cryptodataapi.com/ai-agents/mcp-server.

I am Sam Deering. I built CryptoDataAPI so agents can read live Hyperliquid decision data. Agents read. They do not trade. We are not a broker.

This is not a CoinMarketCap war page. One line is enough. Candle AI APIs sell homepage Q&A on price and market cap. We sell live Hyperliquid decision data — whales, GEX, regimes, fills — over MCP.

What candle AI APIs give

Candle AI APIs sell chat on price and market cap.

They answer “what is BTC worth.”

They answer “what is the market cap.”

Many wrap OHLCV, funding, and open interest into a homepage Q&A loop.

That is commodity context.

It cannot classify Hyperliquid ≥$100k whales.

It cannot publish dealer gamma or a gamma flip.

It cannot name the short-horizon HMM regime with calibrated probability buckets.

It cannot tell an agent who is forced to trade next.

Candles are already free on our spine. The free tier serves /api/v1/market-data/klines and /api/v1/hyperliquid/candles — any authenticated key, free tier included. Fetch bars when a strategy needs bars. Do not open with a candle poll to discover what this API is. Live agent docs say the same: do not open with OHLCV.

What CryptoDataAPI MCP gives

Point any MCP client at https://cryptodataapi.com/mcp.

The server exposes 26 curated, read-only tools. Logic runs on our side. One API key. No per-endpoint glue.

The wedge is the Hyperliquid decision layer. Three Pro tools carry it:

1. get_whale_activity

REST: GET /api/v1/quant/whales.

Live board: https://cryptodataapi.com/quant-whales

It rolls the Hyperliquid ≥$100k account universe into one read: net bias, per-coin conviction, and directional net with market-maker liquidity excluded. Scope is HL perps. Pro.

2. get_gamma_exposure

REST: GET /api/v1/quant/gex.

Live board: https://cryptodataapi.com/quant-gamma

It is the perp analog of dealer GEX: MM inventory, gamma profile, and gamma flip. Agents use amplify versus dampen as a stand-down read. Pro.

3. get_market_regime

REST: GET /api/v1/quant/market.

Live board: https://cryptodataapi.com/market-regimes

It returns the short-horizon HMM regime across six states with calibrated probability buckets. Gate strategy choice on the regime. Pro.

Liquidations / fills path (truthful split).

ETF flows.

Event calendar.

Lead with whales, GEX, and regimes. Treat fills, ETF flows, and calendar as supporting surfaces.

How to connect MCP

Exact copy from the live MCP server page.

Remote HTTP (recommended — browser login, no key pasted):

claude mcp add --transport http cryptodataapi \
  https://cryptodataapi.com/mcp

The first tool call opens a browser to sign in and authorize. Signing in creates a free-tier account automatically if you are new.

Local stdio bridge (when the client only speaks stdio):

export CRYPTODATA_API_KEY="cdk_live_yourkey"
claude mcp add cryptodataapi -- npx -y cryptodataapi-mcp

Cursor / Claude Desktop style config uses the same package: npx with args ["-y", "cryptodataapi-mcp"] and env CRYPTODATA_API_KEY.

Official registry id: com.cryptodataapi/mcp. Remote URL: https://cryptodataapi.com/mcp.

Free key and the 24h Pro cliff

Mint a free key with a real email:

curl -X POST https://cryptodataapi.com/api/v1/auth/keys \
  -H "Content-Type: application/json" \
  -d '{"email":"[email protected]"}'

Confirm that email on the same key.

Confirming lifts the key from 100 to 1,000 requests/day.

Confirming also switches Pro on for 24 hours on that same key.

get_market_regime, get_gamma_exposure, and get_whale_activity are Pro tools. A 403 before Pro is the expected free-tier answer. Leave the 403 as-is. Read the body. Do not invent tools or fields. Confirm email for the free Pro gate, or see https://cryptodataapi.com/pricing.

If you drop to raw REST from Python's urllib, set a named User-Agent. The CDN returns an HTML 403 (Cloudflare 1010) on the default Python-urllib/3.x signature before the API runs. requests, httpx, curl, and Node fetch need no change. MCP tool calls handle this for you.

What this is not

This is not a CoinMarketCap war page or a feature-by-feature competitor table.

This is not candles-first onboarding.

This is not Discord.

This is not a broker. Agents read. They do not place orders here.

This is not a rewrite of the Hyperliquid fill-tape sibling post (in the works, no live URL yet). That draft sells per-event fills versus aggregate totals. This piece sells the MCP wedge versus candle AI APIs. Fills appear once above as path truth: MCP get_liquidations versus REST hl-liquidations.

For agents: tool order

Use the live MCP “first four calls” order.

  1. list_capabilities — no key. What exists and what each tier unlocks.
  2. create_free_api_key — only if you lack a key. Ask the human for a real email.
  3. get_daily_snapshot — whole-market cached overview. Replaces ~10 calls.
  4. get_market_regime or get_gamma_exposure — Pro decision layer. Then call get_whale_activity.

Example after MCP is connected:

Call get_market_regime. Then get_gamma_exposure for BTC. Then get_whale_activity. Summarize regime state, amplify/dampen, and whale net bias. Do not trade. Do not invent fields. If you get a 403, say so and ask me to confirm the key email for 24h Pro.

Optional later: get_etf_flows for flow context. get_liquidations for live aggregates. REST hl-liquidations only when you need per-event fills.

Do not open with OHLCV.

Docs