KEYINSIGHT
I fed three OFAC-sanctioned wallets to three sanctions-screening APIs. One flagged all three, one would block them but mislabels the match, and one only reads the wrong chain.
Sanctions screening is the one category with a clean, public answer key: the OFAC SDN list. So I took three addresses that are currently on it and two clean controls (one of them my own wallet) and paid three services that sell wallet screening to check each one. Nobody let a sanctioned wallet through, which is the good news. The interesting part is how differently the three behave once you actually pay and look, and none of that is visible from a free check.
- One is exactly right. lionx402.com flagged all three sanctioned addresses and cleared both clean ones, no false positives, no misses. It advertises an OFAC SDN wallet screen and it delivers one. If you want a single takeaway, it is that a correct sanctions screen at a fraction of a cent does exist in this market.
- One would protect you but you cannot trust its own sanctions field. api.anchor-x402.com marked all three sanctioned wallets critical with a recommendation to block, and cleared both clean ones, so an agent using it would refuse every bad address. But its dedicated sanctions_match field, the boolean that is supposed to say is this an OFAC hit, came back false on one of the three, and its sanctioned_lists array was empty even when it said true, so it never names the list. It also advertises a tenth of a cent and then charges two cents, a twentyfold overcharge our per-call cap refused before we raised it.
- One cannot answer the question at all, and says so. trust-agent.io reads only Base and returned a clean unsupported_chain error for every Ethereum-mainnet address, which is honest but means it is the wrong tool for screening an OFAC name that lives on mainnet. A free probe would rate it fast and cheap and tell you none of this. The only way to learn which chains a screener covers, whether its match field is reliable, or what it really charges, is to pay it and check the answer against the actual list.
Receipts and detailclick to expand
What I sentto grade against the one public answer key sanctions has, the OFAC SDN list, by feeding each service addresses that are currently on it plus clean controls, rather than judging one screener against another
ground truth: OFAC SDN list (ETH digital-currency-address entries), from the maintained
public mirror of Treasury's list, current as of 2026-08-08 (Tornado Cash correctly absent,
it was delisted in 2025). 3 sanctioned addresses + 2 clean controls.
lionx402.com /api/x402/sanctions-screen-json
sanctioned x3 -> flagged | clean x2 -> clear correct on all five
api.anchor-x402.com /v1/screen
sanctioned x3 -> risk critical, recommendation block (would refuse all three)
but sanctions_match: false on 1 of 3, and sanctioned_lists: [] on every response
clean x2 -> risk low, no flags correct
advertised $0.001, charged $0.02 live (20x); cap refused it until raised
trust-agent.io /v1/verify/quick
every address -> error unsupported_chain: reads base only, not ethereum
raw responses archived, so every cell above is re-checkable. total ~$0.10.- Screeners tested
- 3
- OFAC-sanctioned wallets fed
- 3
- Clean controls
- 2
- lionx402
- 3/3 flagged, 2/2 cleared
- anchor: blocks all 3, but sanctions_match
- wrong on 1/3
- anchor overcharge
- 20x ($0.001 to $0.02)
- trust-agent
- Base only, refuses ETH
- Whole test cost
- ~$0.10
Receipts: Three wallet-screening services paid to screen three addresses currently on the OFAC SDN list plus two clean controls. Raw responses archived so every verdict is re-checkable. Total about ten cents, reconciled on-chain.