How should a Web3 project screen user deposit addresses for AML risk?
Add an automated gate at the deposit entry: when a deposit lands (or a deposit address is registered), call a screening API; flag sanctions, mixer or stolen-fund matches for human review and let the rest through. Wash existing addresses with a batch endpoint. OceanAlt offers free single lookups (/api/risk) and pay-per-call batch screening (batch_screen), with evidence on every flag so you can explain to a user why their deposit was held.
Three implementation details
Screening the funds' origin matters more than the address itself: deposit addresses are often freshly generated and match nothing; the signal is whether their one-hop upstream touched listed addresses. OceanAlt verdicts include one-hop taint analysis (depth varies by chain, published per chain).
Interventions must be explainable: both regulators and users will ask on what grounds. Choose a tool that shows evidence sources, not just a number.
Plan the false-positive path up front: what happens when a legitimate user is flagged? OceanAlt's public appeal page can be handed straight to the user.
Where to start: free address check · API docs · watch an address
Boundary of everything above: a screening "clear" only means no match in the data held, never a safety guarantee; this page is not legal or compliance advice.