# Blocktronics > On-chain token intelligence for tokens on Base, Ethereum and Robinhood Chain: holders by position size, cost basis and MVRV, supply concentration, DEX netflow and volume, holder profitability, smart money flows, an A–E grade and today's hourly flows. Every number comes from stored reads of the public Blocktronics data (a 60-day daily window, UTC). Missing data is null, never zero. ## Connect over MCP MCP server (Streamable HTTP): https://blocktronics.xyz/api/mcp/account Setup for Claude, ChatGPT, Claude Code, Cursor, VS Code, Codex and the Grok and OpenAI APIs: https://blocktronics.xyz/mcp ## The REST API Base: https://api.blocktronics.xyz/v1 — GET https://api.blocktronics.xyz/v1/catalog lists every tool, metric and price (free). POST /v1/tools/{tool} runs one tool with its JSON input; POST /v1/query asks several things about up to 5 tokens at once. The API and the MCP serve the same data, at the same prices, with the same key. ## Access and credits - One API key does both: send it as Authorization: Bearer . A person makes keys on their Blocktronics account page and can connect an AI app there by wallet sign-in. - An agent with its own wallet can get a key with no person: POST https://api.blocktronics.xyz/v1/auth/nonce { address }, sign the message with the wallet (a signature, not a transaction), then POST https://api.blocktronics.xyz/v1/auth/key { nonce, signature }. A new account starts with no credits. - Prices in credits: 2 a pull; token_series 2 per token; compare_tokens 2 plus 1 per added token; screen_tokens 2 per 20 rows; a token's launch bundles 5 (get_sections with launch_bundles or all, or the bundles card), as the site's bundle scan; token_signals 1; the full readout 10, then open 24 hours. explain_metric, credit_costs and get_account are free. - Credits are taken when a call starts and given back at once if it fails or is refused. Without a key, or without credits, a paid tool answers with what it needs instead of data. - Top-ups in USDC (USDG on Robinhood Chain): POST https://api.blocktronics.xyz/v1/topup/quote { credits } answers the exact amount to send and from which wallet; GET /v1/topup/{quote_id} follows it. An agent's own account pays from its own wallet. A key on a person's account tops up only if the person allowed it, from the wallet they named, after that wallet signs once: POST /v1/topup/wallet. - The site's own data feeds (/api/token and the like) serve the site's pages; from anywhere else, use the API. Not served yet, by the API, the MCP or the site: predictive analysis (the Outlook and the engine's predictive scoring), history before the stored 60 days, and alerts. They are coming soon. ## Main tools - search_tokens: find a token by symbol, name or contract address - token_overview: a token's A–E grade, its pillars and key figures in one call - token_series: any metric day by day over the 60-day window - today: this UTC day's flows, hour by hour - compare_tokens: up to 12 tokens side by side, with percentiles - screen_tokens: filter and rank every covered token by grade, metrics and signals - token_signals: a token's fired signals and the Blocktronics read; readout: true for the full readout - explain_metric: what a metric means and how to read it - render_chart: any Blocktronics card as a PNG and SVG - build_dashboard: a shareable dashboard link and embed code - build_hub: a branded page for a set of tokens, as one link ## Read on - [MCP setup and every tool](https://blocktronics.xyz/mcp) - [API docs](https://blocktronics.xyz/docs): keys, credits, top-ups and every endpoint - [Learn](https://blocktronics.xyz/learn): each metric, card and rule, and how to read it