# elizaOS — CryptoDataAPI

> Give your elizaOS agent live crypto data: add the CryptoDataAPI MCP server via the elizaOS MCP plugin (stdio bridge) or a REST action. Free tier, no card.

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](/ai-agents/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
- **Agent docs:** https://github.com/fleek-platform/eliza-plugin-mcp
- **Config:** `character file → settings.mcp.servers`
- **MCP transports:** stdio, sse / streamable-http

## Step 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](https://github.com/fleek-platform/eliza-plugin-mcp), since the elizaOS plugin ecosystem moves quickly).

**Terminal:**
```bash
npm install @fleek-platform/eliza-plugin-mcp
```

## Step 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](https://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:**
```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" }
        }
      }
    }
  }
}
```

## Step 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](/pricing).

### 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.

## Related

- [MCP Server](https://cryptodataapi.com/ai-agents/mcp-server)
- [Agent Skill](https://cryptodataapi.com/ai-agents/agent-skill)
- [LangChain setup](https://cryptodataapi.com/ai-agents/langchain)
- [OpenClaw setup](https://cryptodataapi.com/ai-agents/openclaw)
- [REST API docs](https://cryptodataapi.com/api/docs)

---

Canonical: https://cryptodataapi.com/ai-agents/elizaos
Machine-readable API map: https://cryptodataapi.com/llms.txt
Agent skill repo: https://github.com/Crypto-Data-API/cryptodataapi-skills (`npx skills add Crypto-Data-API/cryptodataapi-skills -g -y`)
Free API key (no signup): POST https://cryptodataapi.com/api/v1/auth/keys {"email":"you@example.com"}