OFAC Sanctions for Insurance AI Agents

By agentmail team · 2026-07-18

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

OFAC Sanctions for Insurance AI Agents screen counterparties against OFAC before every transaction. agentmail gives you real-time sanctions data, no key to start.

Agents executing OFAC operations touch real value and real counterparties. A missed sanctions check is a violation.

How does sanctions screening work for OFAC agents?

Add the screen to your ofac agent workflow. Free tier, paid plans for 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 ofac agents?

• 947 OFAC-sanctioned crypto wallets across Ethereum, Bitcoin, Solana, and Tron — refreshed daily from US Treasury and vile/ofac-sdn-list
• 19,218 Specially Designated Nationals with fuzzy name matching for aliases, transliterations, and alternative spellings
• 16 embargoed jurisdictions including comprehensive sanctions on Cuba, Iran, North Korea, and Syria
• Sub-100ms response so the check fits inline in any payment path without degrading the agent experience
• Automatic audit trail with timestamp, subject, result, and SDN list version for every screen

Related resources

• OFAC screening for AI agents \u2014 general agent compliance guide
• What is the OFAC SDN list?
• What is strict liability?
• OFAC violation costs for ofac agents
• How to set up OFAC screening
• How to screen a wallet before your agent pays
• agentmail vs Chainalysis \u2014 pricing and feature comparison