Maintained by Zerion.
zerion-ai is the public, self-contained repo for using Zerion from AI agents and developer tools.
It packages two first-class integration paths:
- Hosted MCP for Cursor, Claude, and other MCP-native agent environments
zerion-clifor OpenClaw-like and command-based agent runtimes
It also ships one flagship workflow:
wallet-analysisas a reusable skill/playbook for portfolio, positions, transactions, and PnL analysis
Start here: Get your API key
Useful current docs:
As of March 8, 2026, Zerion's public authentication docs describe:
- API auth via HTTP Basic Auth
- dev keys beginning with
zk_dev_ - current dev-key limits of 120 requests/minute and 5k requests/day
Use this if your agent runtime already supports MCP.
Start here:
Use this if your framework models tools as shell commands returning JSON.
npm install -g zerion-cli
zerion-cli wallet analyze 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045Start here:
-
Export your API key:
export ZERION_API_KEY="zk_dev_..."
-
Add the hosted Zerion MCP config from examples/cursor/mcp.json or examples/claude/mcp.json
-
Ask:
Analyze the wallet 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045. Summarize total portfolio value, top positions, recent transactions, and PnL.
npm install -g zerion-cli
export ZERION_API_KEY="zk_dev_..."
zerion-cli wallet analyze 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045Example output:
{
"wallet": {
"query": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
},
"portfolio": {
"total": 450000,
"currency": "usd"
},
"positions": {
"count": 42
},
"transactions": {
"sampled": 10
},
"pnl": {
"available": true
}
}This repo uses the same public wallets across examples:
vitalik.eth/0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045- ENS DAO treasury /
0xFe89Cc7Abb2C4183683Ab71653c4cCd1b9cC194e - Aave collector /
0x25F2226B597E8F9514B3F68F00F494CF4F286491
mcp/: hosted Zerion MCP setup plus the wallet-analysis tool catalog this repo relies onskills/wallet-analysis/: the flagship read-only skillcli/:zerion-cliJSON-first CLIexamples/: Cursor, Claude, OpenAI Agents SDK, raw HTTP, and OpenClaw setups
Both the MCP and CLI surfaces should handle:
- missing or invalid API key
- invalid wallet address
- unsupported chain filter
- empty wallets / no positions
- rate limits (
429) - upstream timeout or temporary unavailability
See mcp/README.md and cli/README.md for the concrete behavior used in this repo.