Token Metrics for AI agents
Token Metrics provides AI-driven cryptocurrency market data and trading signals, used by developers building trading bots, dashboards, and portfolio tools. 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 Token Metrics.
Get the price of a token
Look up a cryptocurrency's current price, a read-only market check.
Get trading signals for a token
Pull the current buy or sell signal generated for a specific token.
List top tokens by market cap
Read the current ranking of tokens by market capitalization.
5 Token Metrics actions, graded by risk.
Every Token Metrics action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
5Look things up. Allowed by default.
- token_metrics.get_priceGet Price
- token_metrics.get_tokensGet Tokens
- token_metrics.get_trading_signalsGet Trading Signals
- token_metrics.get_technical_indicatorsGet Technical Indicators
- token_metrics.get_top_market_cap_tokensGet Top Market Cap Tokens
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.
Token Metrics in three steps.
- 01Your users connect Token MetricsThey add their Token Metrics 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 Token Metrics through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('token_metrics', { 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 Token Metrics connects.
Users add their Token Metrics 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 Token Metrics 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 Token Metrics from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Token Metrics and Arc0, answered.
Can I use Token Metrics with Claude, ChatGPT or Cursor?
Yes. Connect Token Metrics 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 Token Metrics actions you allow.
How do users connect Token Metrics?
Users add their Token Metrics 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 Token Metrics actions can my agent take?
5 in total: 5 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Token Metrics?
Yes. Allow read actions and deny writes in the Token Metrics policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Token Metrics too?
Yes. The same Token Metrics connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Token Metrics into your agent.
Your users connect Token Metrics once, under your brand. Your agent gets 5 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan