For DAO Treasuries agents

OFAC Sanctions Screening for DAO Treasuries

Screen recipient wallets before DAO treasury disbursements — protect your multisig from OFAC violations.

Try the free checker  Get an API key

By ·

Answer: DAO Treasuries agents screen counterparties against the OFAC SDN list (19,086 names, 782 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 DAO Treasuries agents need OFAC sanctions screening?

DAOs that disburse treasury funds to contributors must screen every recipient wallet against OFAC sanctions lists. A single payment to a sanctioned wallet can expose signers to personal liability.

DAO treasury management is under increasing regulatory scrutiny. The Treasury Department has made clear that facilitating transactions with sanctioned entities is prohibited regardless of organizational structure.

How does sanctions screening work for DAO Treasuries agents?

Integrate sanctions checks into your DAO's payment workflow via HTTP API or MCP. Free tier: 5 checks/day. Production from $19/mo.

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 dao treasuries agents?

Related resources

Add compliance to your dao treasuries agents

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

See pricing