Demo tier
npx -y @blockchainacademics/mcp (or uvx bca-mcp) just works. No signup, no BCA_API_KEY, no copy-paste from a dashboard. The package ships with a public demo key baked in.
What you get
17 tools work without a key, with real data and real citations:
| Tool | What it does |
|---|---|
get_price | Spot price, 24h change, market cap and 24h volume for up to 50 tokens |
get_trending | Trending coins by mentions over 1h, 6h, 24h or 7d |
get_fear_greed | Crypto Fear & Greed index: daily readings for up to 365 days |
get_market_overview | Top tokens by market cap, with the 1h, 24h and 7d change |
search_news | Full-text search across 3,800+ editorial articles |
get_article | One article in full by slug: text, author, source, topics and tickers |
get_sentiment | Sentiment bucket for an entity over 1d, 7d, 30d or 90d |
get_entity | Project, chain or person dossier by slug (the ticker form needs a key) |
get_explainer | BCA Academy material: 38 lessons in 8 courses |
get_recent_stories | The last 24 hours of coverage, clustered into stories |
get_topic | One topic: live article count, child topics and recent articles |
search_grants | Live grant programs with amounts, deadlines and apply links |
get_grant | One grant program in full |
list_jobs | Live crypto jobs from the companies' own job boards |
get_job | One crypto job in full |
search_academy | Full-text search across the academy lessons |
get_as_of_snapshot | The article corpus as it stood at a past date |
Every response carries meta.tier: "demo" and meta.upgrade_url so your agent knows when it's on the demo path.
What you don't get
- Every other tool (agent-backed research, on-chain dossiers, proprietary indicators, KOL influence and so on), and
get_entityby ticker, returns HTTP 403 withX-BCA-Error-Code: BCA_TIER_LOCKEDand a signup link in the error body. Over MCP that is aBCA_TIER_LOCKEDerror. - Per-user quotas. The demo bucket is shared globally; heavy days can hit the cap.
Rate limits
- 100 calls per day, shared across all demo users globally.
- 20 calls per IP per day so one heavy user can't drain the bucket for everyone.
- 1 request per second, shared by every demo caller.
When you hit any of these caps you get HTTP 429 with a Retry-After header and the signup URL in the error body. The agent can surface that to the user.
Upgrade in 30 seconds
Get a free key at blockchainacademics.com/crypto-api/signup. The free tier is 2,000 calls a month on your own quota, no shared bucket, and opens the 52 tools marked Free in the tool reference; Starter, Pro and Team open the rest. Plans are on Pricing.
Once you have a key, drop it into your client config:
{
"mcpServers": {
"blockchainacademics": {
"command": "npx",
"args": ["-y", "@blockchainacademics/mcp"],
"env": { "BCA_API_KEY": "bca_..." }
}
}
}{
"mcpServers": {
"blockchainacademics": {
"command": "npx",
"args": ["-y", "@blockchainacademics/mcp"],
"env": { "BCA_API_KEY": "bca_..." }
}
}
}export BCA_API_KEY=bca_...
npx -y @blockchainacademics/mcpHow it works under the hood
The npm and PyPI packages embed a single public key (bca_demo_…) as a build-time constant. When BCA_API_KEY is unset, the client falls back to that value and sends it as X-API-Key. The backend recognises the literal string via constant-time compare, synthesises an in-memory APIKey row with tier: "demo" (no DB lookup), applies the three demo caps above (per second, per IP per day and the shared daily bucket), checks the request path against the demo allowlist (17 tools), and dispatches.
On stdio startup the server emits a one-time banner to stderr so the MCP host log shows the demo mode is active:
[bca-mcp] Running in DEMO mode: 17 tools work without a key, under a shared daily cap.
[bca-mcp] A free key opens 52 tools and paid plans open the rest: https://blockchainacademics.com/crypto-api/signup?ref=mcp-first-run
[bca-mcp] Set: export BCA_API_KEY=bca_... (or add to your client config)Stderr is safe because stdout is owned by the MCP stdio transport. The banner appears once per server boot, never per tool call.