CoinMarketCal for AI agents
CoinMarketCal tracks upcoming crypto events like listings and announcements, giving traders a calendar of developments that could move the market. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in CoinMarketCal.
Check upcoming events for a coin
List upcoming events for a specific coin before deciding whether to watch it closely.
Browse events by category
List cryptocurrency events filtered by category, such as exchange listings or mainnet launches.
Look up supported coins
List supported coins before confirming a specific token has upcoming calendar coverage.
3 CoinMarketCal actions, graded by risk.
Every CoinMarketCal action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
3Look things up. Allowed by default.
- coinmarketcal.list_coinsList Coins
- coinmarketcal.list_eventsList Cryptocurrency Events
- coinmarketcal.list_event_categoriesList Event Categories
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
CoinMarketCal in three steps.
- 01Your users connect CoinMarketCalThey add their CoinMarketCal api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls CoinMarketCal through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('coinmarketcal', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How CoinMarketCal connects.
Users add their CoinMarketCal api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same CoinMarketCal connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use CoinMarketCal from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
CoinMarketCal and Arc0, answered.
Can I use CoinMarketCal with Claude, ChatGPT or Cursor?
Yes. Connect CoinMarketCal to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the CoinMarketCal actions you allow.
How do users connect CoinMarketCal?
Users add their CoinMarketCal api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which CoinMarketCal actions can my agent take?
3 in total: 3 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in CoinMarketCal?
Yes. Allow read actions and deny writes in the CoinMarketCal policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call CoinMarketCal too?
Yes. The same CoinMarketCal connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug CoinMarketCal into your agent.
Your users connect CoinMarketCal once, under your brand. Your agent gets 3 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan