For Remittance agents
Remittance agents screen sender and receiver names, payout wallets, and destination countries against OFAC on every transfer.
Try the free checker Get an API keyBy ·
Answer: Remittance agents screen counterparties against the OFAC SDN list (19,218 names, 947 crypto wallets, 16 embargoed jurisdictions) via a single API call before every payment. A "clean": true response means proceed; "clean": false means halt. The check runs in under 100ms and the free tier covers 5 checks/day with no API key.
Remittance agents that send cross-border transfers are the textbook OFAC use case - high volume, many jurisdictions, strict screening duties. agentmail screens sender and receiver names, payout wallets, and destination countries on every transfer before it is queued.
Money transmitters are expected to screen every party on both ends; an autonomous remittance agent that skips this transfers the violation - and the penalty - to its operator. Building the check into the send flow makes compliance automatic, not a post-transaction report.
Integrate via MCP, HTTP, or CLI alongside your existing rail. 5 checks/day to validate, paid plans for production volume.
curl "https://sanctionsai.dev/sanctions?wallet=0x098B716B8Aaf21512996dC57EB0615e2383E2f96"Real OFAC data. Free tier: 5 checks/day, no API key.
MCP, HTTP, and CLI. Self-host free, or use the hosted API.
See pricing