For DeFi Protocols agents

OFAC Sanctions Screening for DeFi Protocols

DeFi frontends screen connecting wallets before allowing interaction. Comply without breaking composability.

Try the free checker  Get an API key

By ·

Answer: DeFi Protocols agents screen counterparties against the OFAC SDN list (19,086 names, 782 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 DeFi Protocols agents need OFAC sanctions screening?

DeFi protocols need to screen connecting wallets against the OFAC SDN list before allowing deposits, swaps, or withdrawals. agentmail gives you a sub-second wallet check that fits inside your frontend's connect-wallet flow.

OFAC enforcement against DeFi protocols (Tornado DAO, etc.) established that on-chain services cannot ignore sanctioned addresses. A pre-interaction wallet screen is the minimum control that protects your protocol.

How does sanctions screening work for DeFi Protocols agents?

Wire the screen into your wallet-connect handler. Free tier: 5 checks/day, no signup. Production from $19/mo.

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 defi protocols agents?

Related resources

Add compliance to your defi protocols agents

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

See pricing