Skip to main content
Etherscan Flow is an agent skill that turns your agent into an onchain investigator for tracing, verifying, and visualizing onchain money flows. Give it a transaction hash, an address, a resolvable entity, a draft case, or a source URL, and it queries live Etherscan API data and returns a single import-ready Flow Case file of nodes and edges. Every address, amount, and transaction hash is grounded in a real API response.
An Etherscan Flow Case visualized on the canvas: wallet and contract nodes connected by labeled fund-flow edges
It runs in two modes, plus a document-import path:
  • Strict trace: start from a transaction hash or address and follow the money.
  • Business/entity profile: start from a DAO, protocol, or business, resolve it to verified addresses, then summarize income, spending, and totals.
  • Document import: paste a draft case, notes, or a link you typed, and it verifies every address and claim against the live API.
Where the general Etherscan Orchestrator routes a task to the right Etherscan interface, Etherscan Flow owns a full multi-step investigation workflow on top of the API.

Get started

1

Install the skill

Add the skill with the skills.sh CLI. -g installs it globally (user-level, so it is available in every project) and -a '*' installs it for every agent you have set up (Claude Code, Codex, and others):
Or clone the repo and move the folder into your agent’s skills directory, ~/.claude/skills/ or ~/.codex/skills/:
2

Run your first trace

Describe the case in plain language.
The agent pulls live transactions, follows the money hop by hop, and returns an import-ready Flow Case.

Provide an API key

Etherscan Flow calls the Etherscan API, which needs an API key. The skill resolves one in this order, first usable match wins:
  1. The Etherscan CLI config
  2. The Etherscan MCP connection
  3. An inline apikey= in your request
  4. The ETHERSCAN_API_KEY environment variable
  5. A local key file
Resolving through the CLI or MCP keeps the key out of the chat transcript.

Example Usage

Paste a hash or address and ask to investigate:
Or profile a DAO, protocol, or business from a verified scope:
Or import a draft, notes, or any link and have every claim verified onchain:

Run without approving every call

A single trace can make many API calls (up to 100), so your agent may prompt you to approve each one. That prompt comes from your agent’s own permission system, not from Etherscan Flow. You can safely approve them all at once: every call is a read-only GET to a single host, api.etherscan.io, so nothing is written or spent. To set that up in Claude Code, Codex, or Claude.ai, see Stop it asking permission for every call.

Output

You get a single Flow Case JSON file. Open etherscan.io/flow, choose Import, and paste it: the schema maps one to one, with no reformatting.
Roles, labels, and notes in a case are an agent’s inference over public Etherscan data, not Etherscan verdicts, accusations, or legal findings.