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
EL

elizaOS

Platform integration

Give your elizaOS agent live crypto market data — prices, funding, open interest, liquidations, market regimes, Fear & Greed, dealer gamma and whale activity — so a trading or research character can reason over real markets.

elizaOS speaks MCP through its MCP plugin, so our two-part model applies: the MCP server provides live tools, configured under settings.mcp.servers in your character file. Because our auth is a keyed header, the reliable path is the stdio bridge (cryptodataapi-mcp), which carries the key in an env var.

Vendor · elizaOS MCP · stdio + sse / streamable-http Config · character file → settings.mcp.servers Agent docs →
1

Add the MCP plugin

Install the MCP plugin into your elizaOS project and add it to the character's plugins array. The maintained package is @fleek-platform/eliza-plugin-mcp (confirm the current package name against the plugin repo, since the elizaOS plugin ecosystem moves quickly).

Terminal
npm install @fleek-platform/eliza-plugin-mcp
2

Configure the server in your character

Add cryptodataapi under settings.mcp.servers. Use the stdio form so the key rides in CRYPTODATA_API_KEY (needs Node.js) — this is the dependable way to authenticate. Replace cdk_live_YOUR_KEY with your key; a free one comes from cryptodataapi.com/login.

The plugin also supports remote server types (sse, and newer builds streamable-http), but the documented remote config doesn't expose a custom-header field for auth — so for a keyed header like ours, prefer stdio unless your plugin version documents remote headers.

character.json
{
  "name": "MarketAnalyst",
  "plugins": ["@fleek-platform/eliza-plugin-mcp"],
  "settings": {
    "mcp": {
      "servers": {
        "cryptodataapi": {
          "type": "stdio",
          "name": "CryptoDataAPI",
          "command": "npx",
          "args": ["-y", "cryptodataapi-mcp"],
          "env": { "CRYPTODATA_API_KEY": "cdk_live_YOUR_KEY" }
        }
      }
    }
  }
}
3

REST fallback + keyless bootstrap

If you'd rather not run a subprocess, write a small custom action that calls our REST API with the X-API-Key header (add ?format=markdown for clean text). And if the agent starts without a key, it can call the create_free_api_key MCP tool (no key required) to mint a free one from an email, then use it on subsequent calls.

Start the agent and message the character — see the example prompts below.

Example prompts

“What's the current crypto market regime and which strategy baskets fit it?”

“Compare BTC funding rates across exchanges and tell me if positioning is crowded.”

“Which coins have the highest liquidation risk right now?”

“Give me a one-line risk-on / risk-off read on the market.”

“Is dealer gamma amplifying or dampening BTC moves today?”

FAQ

Does it cost anything?

No. elizaOS is open-source and self-hosted, and the Free API tier (no card) covers market health, regimes, Fear & Greed, macro, flows, coin profiles and full-universe Hyperliquid funding + open interest. Per-coin quant, gamma and whale signals need Pro.

Why stdio instead of a remote server?

Our tools authenticate with an X-API-Key header. The elizaOS MCP plugin's documented remote configs (sse / streamable-http) don't clearly expose a custom-header field, whereas the stdio transport passes the key via env reliably. If your plugin build documents remote headers, you can use the remote form instead.

The agent can't reach the tools — what now?

Confirm the plugin is in the character's plugins array and Node.js is installed (the bridge runs via npx). Check the elizaOS logs for the MCP server's startup line. If a tool returns 401, fix CRYPTODATA_API_KEY, or have the agent call create_free_api_key to mint one.

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.