Subscription tiers
This page documents the subscription tiers available for the Cryptohopper Market Data MCP.
Tier summary
| Pioneer | Explorer | Adventurer | Hero | |
|---|---|---|---|---|
| Cost | Free | Paid | Paid | Paid |
| Weekly call limit | 6,000 | 30,000 | 150,000 | 1,250,000 |
| Exchanges | 3 | 8 | All supported | All supported |
| Historical data | None | Up to 90 days | Up to 365 days | Up to 3 years |
| Historical cost factor | — | 5× / 20× | 5× / 20× | 1× (flat) |
| API keys allowed | 1 | 1 | 3 | 10 |
All limits refresh every Friday. The weekly call limit and rate limit apply per user account, not per API key.
For current pricing of paid tiers, see the Cryptohopper pricing page.
Weekly call limit
Each tier has a fixed number of calls that can be made per calendar week. Calls are counted per tool invocation. A single tool invocation counts as a baseline unit, subject to the historical cost factor described below.
The weekly counter resets every Friday. The exact reset time is recorded against the user account and is visible through the usage endpoint. See usage and limits.
Requests made after the weekly limit is reached return a QUOTA_EXCEEDED error until the next reset. See error reference.
Exchange access
Exchange access is tier-gated. The Pioneer tier is restricted to three exchanges; Explorer extends this to eight; Adventurer and Hero expose the full list.
See supported exchanges for the full matrix.
Requests targeting an exchange outside the current tier's allow list return an EXCHANGE_NOT_SUPPORTED error.
Historical data
Historical data refers to candle queries with a lookback period greater than the most recent bar.
| Tier | Historical availability |
|---|---|
| Pioneer | Not available. Only the current (real-time) candle is returned. |
| Explorer | Up to 90 days of history. |
| Adventurer | Up to 365 days of history. |
| Hero | Up to 3 years of history. |
Requests exceeding the current tier's historical limit return a HISTORY_LIMIT_EXCEEDED error.
Ticker and orderbook queries are always real-time and are not subject to the historical limit.
Cost factor for historical data
On the Explorer and Adventurer tiers, historical candle queries are charged at a multiplier relative to the baseline per-call unit:
| Lookback depth | Cost multiplier |
|---|---|
| Short history (recent) | 5× |
| Long history (near tier limit) | 20× |
On the Hero tier, all historical queries are charged at 1× regardless of lookback depth.
Ticker and orderbook queries are always charged at 1× on all tiers.
The exact thresholds between "short" and "long" history, and the full cost matrix, are documented in rate limits explained.
API keys
Each tier allows a maximum number of simultaneously active API keys:
| Tier | Max keys |
|---|---|
| Pioneer | 1 |
| Explorer | 1 |
| Adventurer | 3 |
| Hero | 10 |
API keys are generated and revoked through the Cryptohopper account interface.
Per-account quota. Creating additional keys does not increase the weekly call limit. All keys associated with an account share the same weekly quota and rate limit. Keys are used for segmentation and rotation, not quota multiplication. See how to run multiple agents with multiple API keys.
See API key security best practices.
Rate limits
Rate limits apply at the per-account level and are uniform across tiers. Details are documented in rate limits explained.
Upgrading and downgrading
Tier changes take effect at the start of the next weekly cycle. Downgrading to a tier with a lower API key allowance may require revoking keys to fit within the new allowance.
Verifying the active tier
The current tier is returned by the usage endpoint as a tier field. See usage and limits.
Example query through an MCP client:
What is my current Cryptohopper MCP tier and how much of my weekly quota have I used?