coinlobster-api

# Building on CoinLobster Integration guide for coding agents: pick the right surface, then the right tier. ## Pick the surface | You are building | Use | | --- | --- | | An AI agent / MCP client | Hosted MCP: `https://coinlobster.com/mcp` (streamable HTTP, keyless, no install), or the `coinlobster-mcp` npm package for a local stdio proxy to the same server. | | A Claude/ChatGPT connector | `https://coinlobster.com/mcp/connector` (OAuth; user signs in). Depth follows the developer plan on that account. | | A bot, dashboard or backend | REST: keyless `/api/public/*` to prototype, keyed `/api/ai/v1/*` for full data | | Quick agent-readable context | `https://coinlobster.com/llms.txt`, `/crypto-whales.md`, `/radar.md` | Full REST catalog + field meanings: [references/endpoints.md](references/endpoints.md). OpenAPI: `https://coinlobster.com/openapi.json` ## Free vs keyed - **Keyless** (no signup): BTC/USD + every $1M+ trade real-time, other pairs 15-min delayed, DEX swaps $250K+, radar with magnitudes on the free pair (BTC) only. Rate limits differ by surface: REST `/api/public/*` allows 60 requests/min per IP (the 61st returns 429). The MCP is limited on its own layered per-IP and per-tool budget; read `Retry-After` on a 429 instead of assuming a rate. - **Free key** (a one-off 1,000-credit grant at https://coinlobster.com/developers, no card): unlocks the metered REST endpoints at `/api/ai/v1/*` (10 to 50 credits per call, so roughly 20 to 100 calls in total, history to 4...