For Trading agents

OFAC Sanctions Screening for Trading AI Agents

Trading bots screen counterparties, wallets, and jurisdictions against OFAC before each cross-border fill or settlement.

Try the free checker  Get an API key

By ·

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

Trading bots that execute cross-border transactions move fast - often too fast for manual compliance review. agentmail gives your trading agent a sub-second sanctions check on counterparty names, wallets, and jurisdictions before each fill or settlement.

A single trade with a sanctioned counterparty can freeze assets and trigger regulatory scrutiny that outweighs months of gains. Building the screen into the execution path means your bot declines the trade rather than explaining it later.

How does sanctions screening work for Trading agents?

Call it over HTTP from any trading runtime, or expose it as an MCP tool to your reasoning agent. No key needed to start - 5 checks/day free.

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

Related resources

Add compliance to your trading agents

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

See pricing