Trace fund flow across hops
When a risk score isn't enough, trace the money. Fund-flow tracing follows value across hops; the counterparty graph shows who an address transacts with and which entity cluster they belong to.
- A live API key
- The address you want to investigate
1Request a fund-flow trace
Give an address and a hop depth. The trace follows inbound or outbound value and flags any path that touches a flagged category. This is a C4 primitive — the heaviest tier.
curl "https://api.1st-node.com/v1/intel/eth/0x9a..f2/flow?dir=in&hops=3" \ -H "Authorization: Bearer sk_live_..."
2Read the counterparty graph
Pull the address's direct counterparties and their cluster labels to understand who it deals with and whether they belong to a known entity.
curl https://api.1st-node.com/v1/intel/eth/0x9a..f2/graph \ -H "Authorization: Bearer sk_live_..."
3Attach findings to your case
Store the traced paths and cluster labels with your investigation so the conclusion is reproducible and defensible.
Frequently asked
How deep can a trace go?
You set the hop depth. Deeper traces touch more of the graph and therefore cost more credits.
How is this different from a risk score?
A risk score summarizes exposure into one number; a trace shows the actual paths and counterparties behind it.
Keep reading
Top up, get a key, ship.
Self-serve. Pay in crypto or card. Metered by credits — heavy primitives cost more, simple ones are cheap.
Get API key