For Developer agents

OFAC Sanctions Screening API for Developers Building AI Agents

A single API call that screens any wallet, name, or country against OFAC before your agent pays. MCP, HTTP, CLI. Free tier, no key.

Try the free checker  Get an API key

By ·

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

Developers building payment agents need compliance that does not slow them down. agentmail is a one-call OFAC sanctions screen: pass a wallet address, name, or country code, get back a clean or flagged result in under 100ms. No SDK to install, no webhook to configure, no enterprise sales call.

The API screens against 947 OFAC-sanctioned crypto wallets across ETH, BTC, USDT, and Tron, plus 19,218 sanctioned names and 16 embargoed jurisdictions. Data is sourced from the US Treasury OFAC SDN list and vile/ofac-sdn-list, refreshed daily. Fuzzy matching catches name variations and entity aliases. Every screen is logged with a timestamp for audit purposes.

How does sanctions screening work for Developer agents?

Quick start: pip install sanctions-mcp for the MCP server, or curl https://sanctionsai.dev/sanctions?wallet=0x... for the HTTP API. Free tier gives 5 checks per day with no signup. Paid plans from $19/month for production volume, or $0.05 per check via x402 micropayments.

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

Related resources

Add compliance to your developer agents

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

See pricing