OFAC Screening Coverage Glossary Part 1

What screening coverage is, and what lists and jurisdictions a screening solution actually checks.

TL;DR

TL;DR: Screening coverage is the scope of lists, jurisdictions, and identifiers a screening solution checks. The sanctionsai.dev API covers 947 OFAC-listed crypto wallets, 19,218 SDN names, and 16 jurisdictions, synced hourly.

What screening coverage is

Screening coverage describes what a sanctions screening tool actually checks: which lists, how many jurisdictions, and which identifier types, names, addresses, or wallets. A tool is only as complete as its coverage, because a gap is where a missed match hides.

Why coverage matters

Incomplete coverage produces false negatives, and under strict liability, intent is not required for a violation. A payment to a listed party that is not in the tool's data still triggers a penalty starting at $356,000 per violation. Coverage also includes freshness: data that is stale misses newly designated parties.

Coverage in practice

The sanctionsai.dev API screens a counterparty before an agent pays in one call under 100 ms, drawing on 947 OFAC-listed crypto wallets and 19,218 SDN names across 16 jurisdictions, synced hourly. Payment rails such as x402, AP2, ACP, and Coinbase AgentKit move money but do not screen. Not documented: any additional non-OFAC list sources.