For Payments agents

OFAC Sanctions Screening for Payment AI Agents

Payment routing agents screen every party on the route - sender, receiver, intermediary - against OFAC before authorizing funds.

Try the free checker  Get an API key

By ·

Answer: Payments 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.

Why do Payments agents need OFAC sanctions screening?

Payment routing agents sit between senders and receivers, deciding how and where funds move. That makes them the natural enforcement point for sanctions screening - the last stop before money leaves. agentmail checks every leg of a route: sender, receiver, and intermediary wallets or names.

When an agent orchestrates payouts, refunds, or splits, it inherits the compliance duty for each hop. Screening each party against OFAC in real time means a flagged receiver is blocked before the transaction is authorized, not reconciled after.

How does sanctions screening work for Payments agents?

One API call per party, sub-second latency, MCP/HTTP/CLI. The free tier covers prototyping; paid tiers scale to 100,000 checks/month.

Example: screen a wallet before paying

curl "https://sanctionsai.dev/sanctions?wallet=0x098B716B8Aaf21512996dC57EB0615e2383E2f96"

Real OFAC data. Free tier: 5 checks/day, no API key.

What exactly does agentmail screen for payments agents?

Related resources

Add compliance to your payments agents

MCP, HTTP, and CLI. Self-host free, or use the hosted API.

See pricing