Frequently asked questions

OFAC sanctions screening is the process of checking whether a person, entity, wallet, or country your AI agent is about to transact with appears on the US Treasury's Specially Designated Nationals (SDN) list or an embargoed-jurisdiction list. For autonomous agents that move money, screening must happen programmatically, before every payment. agentmail exposes this as a single API call.

You pass a wallet address to the /sanctions endpoint (by query string, MCP tool, or CLI). agentmail looks it up against 947 OFAC-listed crypto addresses across EVM, Bitcoin, and Tron, and returns any matches with list, match_type, and confidence, plus a clean boolean. It runs in milliseconds so it fits inside an agent's payment path.

Crypto wallets come from the vile/ofac-sdn-list GitHub releases (multi-chain, refreshed daily). Names come from the US Treasury OFAC sdn.csv. Jurisdictions cover the 16 comprehensively sanctioned / embargoed regions. Everything is public, free, primary-source data.

No. The free tier gives you 5 sanctions checks/day metered by IP address, with no signup or API key. For higher volume, all four tools, and an audit log, upgrade to a paid key from $19/month at /pricing.

Wallet matches against the published OFAC address list are exact (confidence 1.0). Name matching uses fuzzy matching with a confidence score so your agent can set a review threshold. The underlying lists are refreshed daily, so you are screening against current, not stale, data.

Know Your Agent is the agent-era equivalent of KYC. Instead of asking who a customer is, KYA scores how much you should trust a counterparty AI agent before transacting with it, using evidence like wallet age, a linked domain, a public key, and a declared country. It sits above sanctions screening in the payment flow.

Yes. When x402 is enabled, an agent without an API key can attach an x402 payment to a /sanctions request and pay a tiny USDC amount per check. agentmail verifies the payment and returns the result, so agents can self-serve compliance per call.

Yes. The core toolkit is MIT licensed and self-hostable via pip install sanctions-mcp. You get all four tools locally for free; the hosted API at sanctionsai.dev adds the free tier, paid keys, and x402 per-call payments for production use.