Docs navigation

Tiers & quotas

Blockchain Academics ships one product, the Crypto Brain with its 105 tools, across five access tiers: Free, Starter, Pro, Team and Enterprise. Every tier calls the same endpoints and gets the same envelope. What changes is the call quota, the rate limit and which tools answer with data instead of HTTP 402.

Quick reference

TierTools that answerAgent-backed tools
Free52No
Starter76No
Pro103Yes, except the Team ones
Team105Yes
Enterprise105Yes

Every tier has a daily cap and a per-second rate limit, and both grow with the plan. The monthly figure on Pricing is a guide and is not enforced on its own: the daily cap, a thirtieth of it plus 30%, is what stops a key. Nothing is billed past the plan price and no usage email is sent. The free tier has no card and no time limit. A key can have 3 agent jobs queued or running at a time on any plan. as_of queries (get_as_of_snapshot) work on every tier, the demo key included.

Tool gating

Gating happens per tool: a call to a tool above your plan returns HTTP 402 rather than a thinner payload. The minimum tier per category, read from the same catalog the tool reference is built from:

CategoryToolsMinimum tierGated above the minimum
Content & corpus7FreeNone
Market data4Freeget_ohlc (Starter), get_pair_data (Starter)
On-chain4Freeget_wallet_profile (Starter), get_tx (Starter), get_token_holders (Pro)
Sentiment + crypto Twitter6Freeget_social_pulse (Pro), get_ct_pulse (Pro), get_x_signals (Pro), get_kol_consensus (Pro)
Proprietary indicators6Starterget_coverage_index (Pro), get_narrative_strength (Pro), get_sentiment_velocity (Pro), get_editorial_premium (Pro), get_kol_influence (Pro)
Agent-backed generation (async)6Progenerate_tokenomics_model (Team), translate_contract (Team)
Directories16Freelist_yields (Starter), list_trading_bots (Starter), list_vcs (Starter), list_marketing_templates (Starter), get_marketing_template (Starter), build_custom_indicator (Pro)
Fundamentals6Starterget_tokenomics (Pro), get_team_info (Pro), compare_protocols (Pro), check_rugpull_risk (Pro)
Chain-specific4Freeget_bitcoin_l2_status (Starter)
Microstructure5ProNone
Narrative / meta5Freetrack_narrative (Starter), get_rwa_tokens (Starter)
Regulatory4Starterget_mica_status (Pro)
Security4Freescan_contract (Starter)
Memes / degen4Freecheck_memecoin_risk (Pro), get_degen_leaderboard (Pro)
Compute / AI crypto2Freeget_ai_crypto_metrics (Starter)
Services (revenue)3FreeNone
History time-series4FreeNone
Corpus meta7FreeNone
Memos / theses / social / currencies8Freelist_memos (Starter), get_memo (Starter), list_theses (Starter), get_thesis (Starter)

The 402 body names the tier the tool needs:

json
{
  "detail": "This endpoint requires the 'pro' tier or higher (current: 'free'). Upgrade at https://blockchainacademics.com/crypto-api/pricing"
}

Over MCP it arrives as an error that carries the same sentence (BCA_UPSTREAM from the TypeScript server, BCA_BAD_REQUEST from the Python server); agents read it and surface the upgrade path. BCA_TIER_LOCKED (HTTP 403) is a different answer: the shared demo key calling a tool outside the 17 it opens. See Demo tier.

Attribution by tier

TierAttribution rule
Freecite_url surfaced verbatim. Stripping it breaches the Terms.
StarterSame as Free.
Procite_url recommended. You may leave it out of your agent's output.
TeamSame as Pro.
EnterpriseFull white-label; cite_url may be replaced with a contract-approved scheme.

Every tier receives the same attribution on every response; no parameter removes it. A plan changes what your license lets you do with the citation downstream, not what the API sends. See Attribution & licensing for what "verbatim" means in practice.

Getting a key

  1. Sign up at blockchainacademics.com/crypto-api/signup: continue with GitHub or Google, or enter your email. Free, no card.
  2. Click Reveal my API key (on the dashboard after a GitHub or Google sign-in, or on the page your confirmation email opens): the key (bca_…) is shown once, in your browser. Lost it? Rotate it from your dashboard.
  3. Drop it into BCA_API_KEY in your MCP config or shell.
  4. For a paid plan, pick one on Pricing. If the email you pay with already has a free key, that key moves up to the plan and keeps working. A new email gets a new key: sign in to the dashboard with GitHub, Google or the one-time link in the "key is ready" email, and the dashboard shows the key once.

Rate-limit response

Over-limit calls return HTTP 429 with a detail sentence that names the limit:

json
{
  "detail": "Rate limit exceeded: 2 requests/second for free tier"
}

The daily cap answers the same way, with Daily limit exceeded. A key's 429 carries no Retry-After header: wait a second for the per-second limit, or until midnight UTC for the daily cap. The demo key's 429s do carry Retry-After. Over MCP a 429 is a BCA_RATE_LIMIT error. Custom clients: back off and retry, or upgrade.

Next