Detect mixer exposure
Mixer exposure measures how close an address sits to a tumbling service. The risk endpoint surfaces a mixer category with a hop count; a fund-flow trace confirms the path. Store both so the proximity finding is defensible.
- A live API key with AML scope.
- The address and chain you want to evaluate.
1Check the exposure array
Request the risk score and inspect the exposure array for a mixer category. The hops field tells you how many transaction steps separate the address from the mixer. This is a C3 call.
curl https://api.1st-node.com/v1/aml/eth/0x7c3d.../risk \
-H "Authorization: Bearer sk_live_..."
> { "score": 81, "risk_level": "high", "confidence": 0.9, "exposure": [{ "category": "mixer", "hops": 1 }] }2Confirm the path with a fund-flow trace
When exposure shows a low hop count, trace the inbound flow to see the actual path to the mixer. Fund-flow tracing is a C4 call, so reserve it for confirmation rather than blanket screening.
curl "https://api.1st-node.com/v1/intel/eth/0x7c3d.../flow?dir=in&hops=3" \ -H "Authorization: Bearer sk_live_..."
3Grade by hop distance
Direct exposure at hop 1 is materially different from hop 3. Apply stricter handling to shorter distances and record the hop count that drove the grading.
Frequently asked
Why not always run the fund-flow trace?
Fund-flow tracing is the heaviest C4 call. Use the C3 risk score to detect mixer exposure first, then trace only when a low hop count warrants confirmation.
Does hop distance change the risk?
Yes. Hop 1 is direct interaction; higher hops mean intermediaries between the address and the mixer. Grade handling accordingly.
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