Important: creating multiple keys does not give you more weekly quota. All keys on an account share the same weekly limit. The point of multiple keys is segmentation — independent rotation, attribution, and revocation — not quota multiplication.
Prerequisites
Adventurer tier or higher. Pioneer and Explorer allow only one API key; Adventurer allows three, Hero allows ten — see subscription tiers.
The MCP configured in at least one client — see setup overview.
A clear idea of which agents or workflows will each get their own key.
Setup steps
Plan the segmentation before creating keys
Each key should correspond to one logical consumer. Common patterns:
- One key per agent: daily-digest, volume-scanner, research-assistant.
- One key per environment: prod-agent, staging-agent, dev-laptop.
- One key per person on a small team.
Avoid names like key-1 or temp — a key without a clear purpose becomes an invisible risk over time.
Create the keys in the Cryptohopper account interface
Follow how to get a Cryptohopper MCP API key for each one. Name them exactly as planned in step 1.
Deploy each key to its intended consumer only
The daily-digest key goes only to the cron script that runs the digest. The volume-scanner key goes only to the scanner's scheduled job. The research-assistant key goes only to your Claude desktop or Claude Code config. Do not paste the same key into multiple places — that is segmentation lost.
Implement per-agent throttling
All keys share the quota, so a misbehaving agent can starve the others. Have each agent track its own weekly calls locally and refuse to continue beyond a set budget. The MCP enforces the account-level limit — you enforce the per-agent split.# Inside each agent's run loop
agent_name = "daily-digest"
weekly_budget = 2000 # call units per week for this agent
current_weekly_usage = load_local_counter(agent_name)
if current_weekly_usage > weekly_budget:
log(f"{agent_name} over budget this week, skipping run")
return
result = run_mcp_workflow()
current_weekly_usage += result.calls_consumed
save_local_counter(agent_name, current_weekly_usage)Set up a rotation schedule
Key rotation is defensive hygiene. A simple starting rule: rotate each key every 90 days, rotating the oldest first so no more than one key changes per month. See API key security best practices.
Maintain a key inventory
A small text file or Notion page listing every key, its purpose, its creation date, and where it's deployed. Update it on every rotation or revocation. When the inventory diverges from reality, audit both sides.
Sample key inventory
Name | Created | Deployed to | Last rotated |
daily-digest | 2026-02-01 | GitHub Actions repo X | 2026-04-01 |
volume-scanner | 2026-02-15 | Home server cron | 2026-04-01 |
research-assistant | 2026-03-10 | Claude desktop (laptop) | never |
Check monthly whether the inventory still matches the Cryptohopper account panel.
Cost profile
Creating, rotating, or revoking a key does not consume quota. There is no per-key cost — keys provide attribution only. See rate limits explained.
Troubleshooting
You hit the tier's key limit
Adventurer allows 3 keys; Hero allows 10. Either upgrade or consolidate — fewer agents, reused keys. Most people don't need more than 3.
One agent suddenly exhausts the weekly quota
Check usage via how to monitor your Cryptohopper MCP spend, identify the culprit using per-key local logs, and either throttle it client-side or revoke its key temporarily.
You rotate a key but a consumer is still using the old one
The old key returns UNAUTHORIZED until you deploy the new one. This is the point of separate keys per consumer — rotating one doesn't break the others. Keep a deployment checklist so rotation is routine, not surprising.
You can't tell which key made which call
The MCP reports usage at the account level. Per-key attribution requires local logging — each consumer logs what it calls. Make logging non-optional for any agent you run unattended.
A team member leaves and you don't know which key was theirs
This is why the inventory matters. Revoke any key associated with a departed team member immediately. If you can't tell, revoke all keys owned by that person's projects and redeploy new ones.
You need to give a key to an external contractor or collaborator
A Cryptohopper MCP key is read-only but does consume your weekly quota. Set a hard budget for their key in your client-side throttling logic and revoke aggressively at the end of the engagement.
You want per-key usage analytics from Cryptohopper directly
The current usage endpoint reports account-level figures only. For per-key attribution, local logging is the available path. If you have many agents, consider building an internal dashboard that aggregates local logs.