web3-dev
Web3 Dev — Blockscout PRO API
This skill teaches the agent how to build software (apps, scripts, CLIs, bots, mobile/desktop clients) that reads blockchain data through the Blockscout PRO API — a single HTTP API covering 100+ EVM chains (94+ L2s and scaling projects). One API key works on every supported chain; switch chains by changing the chain_id path parameter on the call.
The PRO API returns explorer-enriched data: indexed, decoded, and structured — token metadata, proxy implementations, internal transactions, contract context, and so on. Use it for dApps and wallets, AI agents and bots, analytics platforms, and operational tooling.
For data the explorer has not pre-indexed — most importantly live or historical contract state at a specific block (e.g. balanceOf(addr) against a token contract at block N, totalSupply() at a past block, any view-function call, contract storage reads) — the PRO API also exposes eth_call through its JSON-RPC gateway. See Reading contract state. The same Bearer-token auth covers both surfaces; you do not need a separate RPC endpoint for historical contract reads.
The bundled files in references/ are the single source of truth for which endpoints exist and how to call them:
| File | Purpose |
|---|---|
references/pro-api-index.md |
One-line summary of every endpoint, grouped by OpenAPI tag. Always start here. |
references/pro-api.json |
Full OpenAPI v3 specification (~24,000 lines). Do not read whole — query it with oastools. |
Do not classify endpoints into your own "families" or steer the user toward a subset. Every endpoint listed in the index is callable, and every endpoint uses the same authentication scheme described below.
API key — mandatory pre-flight
More from blockscout/agent-skills
blockscout-analysis
MANDATORY — invoke this skill BEFORE making any Blockscout MCP tool calls or writing any blockchain data scripts, even when the Blockscout MCP server is already configured. Provides architectural rules, execution-strategy decisions, MCP REST API conventions for scripts, endpoint reference files, response transformation requirements, and output conventions that are not available from MCP tool descriptions alone. Use when the user asks about on-chain data, blockchain analysis, wallet balances, token transfers, contract interactions, on-chain metrics, wants to use the Blockscout API, or needs to build software that retrieves blockchain data via Blockscout. Covers all EVM chains.
25upgrade-blockscout-api
Upgrade the blockscout-analysis skill's API reference files to the latest Blockscout backend and Stats service releases. Run when a new Blockscout version is issued to refresh swagger data, regenerate endpoint documentation, patch MCP-sourced and JSON-RPC endpoints, and remove MCP-duplicated entries.
4bump-skill-version
Bump the blockscout-analysis skill version number across all files. Use after the API reference files have been updated and you are ready to tag a new release. Pass the new version as an argument (e.g., '0.4.0').
1