OFAC Api Compliance Guide Part 1
How the OFAC screening API works and what a single call returns before an agent pays.
TL;DR
TL;DR: The screening API checks a counterparty in one HTTP call under 100 ms. Clean returns ALLOW and flagged returns BLOCK, using 947 OFAC-listed wallets and 19,218 SDN names synced hourly.
What the API does
The API screens a counterparty before an agent pays. It returns a binary decision: clean ALLOW, flagged BLOCK. Data comes from 947 OFAC-listed crypto wallets and 19,218 SDN names across 16 jurisdictions, synced hourly from the US Treasury sdn.csv.
Endpoints and tools
The API exposes sanctions_check for the decision, risk_score for borderline cases, kya_verify for counterparty verification, and dispute_open for challenging a flag. It is MIT-licensed and self-hostable, and it works through x402 and MCP integrations.
Pricing and getting started
- Free tier: five checks per day, no signup, no key.
- Dev: $19/mo for 10,000 checks.
- Pro: $99/mo for 100,000 checks.