Introduction

hodlflow answers fund-flow questions about onchain addresses in seconds:

Where did the money go? Follow funds from an address across several hops, with the share of the original funds at every step (trace).
Who does this address deal with? Rank its counterparties by volume in either direction (topk).
What happened recently? List its latest transfers (neighbors).
Did the funds reach an exchange? Find the nearest labelled exchange, service or mixer (reach).

Every answer is JSON with a _meta block you can cite: the request id, the last block covered and the label snapshot used.

Three ways in

Scope

The browser workspace. Expand a wallet, follow the money hop by hop and keep notes. Sign in with your enrolled e-mail at scope.hodlflow.app.

HTTP API

Plain HTTPS with a personal API key, for scripts, notebooks and case tools. Start with the Quickstart.

MCP

Add one URL to Claude, ChatGPT or another MCP client and ask in plain language. See Connect via MCP.

The API and MCP run the same commands with the same options and draw on the same daily budget.

Supported networks

Network	What is covered	Refresh
Bitcoin	Every transaction from the genesis block, with wallet clusters	Daily
Ethereum	ETH and the whitelisted ERC-20 tokens, from the genesis block	Daily
Tron	TRC20 transfers of USDT, USDD, USDDOLD and jUSDT, and TRX transfers of 1 TRX or more, from 2018	Daily
Zcash	Transparent transactions from 2016-10-28, with wallet clusters; the shielded pools appear as three nodes	Daily

More networks are on the way. Each answer reports the last block it covers in _meta.dataset.max_block; transfers after that block are not in the answer yet.

Next steps

QuickstartMake an API key and run your first query.

Connect via MCPUse hodlflow from Claude, ChatGPT or a local MCP client.

Reading resultsCompleteness flags, amounts and what to cite.

API ReferenceEndpoints, commands, options and errors.