For DeFi Protocol agents

OFAC Sanctions Screening for DeFi Protocol AI Agents

DeFi protocol teams bake OFAC sanctions screening into keeper agents, frontends, and routers so sanctioned wallets are blocked at the edge.

Try the free checker  Get an API key

By ·

Answer: DeFi Protocol 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 DeFi Protocol agents need OFAC sanctions screening?

DeFi protocols themselves are increasingly treated as responsible for the activity their contracts facilitate - including agent-driven flows. agentmail gives protocol teams a sanctions screen they can bake into keeper agents, frontends, and router contracts so sanctioned wallets are blocked at the edge.

Regulators have sanctioned mixer contracts and named wallets; a protocol whose autonomous keepers service those addresses inherits the problem. Embedding an OFAC check in your protocol's agent layer is how you demonstrate a compliance control that scales with TVL.

How does sanctions screening work for DeFi Protocol agents?

Expose it as an MCP tool for your keepers or call it over HTTP from your router. Free tier for integration; paid tiers for mainnet volume.

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 protocol agents?

Related resources

Add compliance to your defi protocol agents

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

See pricing