OFAC Sanctions Screening - SDN & Consolidated Lists

Screen any list of people, companies, vessels or aircraft against US Treasury OFAC sanctions - the SDN list and the Consolidated (non-SDN) list - with fuzzy matching and match scores. Every hit returns the listed entity's aliases (AKA/FKA), sanctions programs, entity type, addresses, title and remarks (DOBs, passports, crypto addresses where OFAC publishes them), and every clear name can emit an auditable all-clear row. Reads OFAC's official public-domain data directly - no API key, no browser, no proxy.

What you get per screening result

Field	Meaning
query / matched / score	The name you screened, whether it hit, and how strong the match is (1-100)
matchedName / matchedNameType	The exact listed name that matched - primary, aka, fka...
primaryName / entityId / listName	The listed entity, its OFAC ID, and SDN vs CONSOLIDATED
sdnType	individual, entity, vessel or aircraft
programs	Sanctions program tags - SDGT, IRAN, RUSSIA-EO14024, SDNTK, CUBA...
akaNames / akaCount	The entity's other listed identities
addresses / addressCount	Listed addresses with country
title / remarks	Role and OFAC's remarks (DOB, POB, passports, digital-currency addresses...)
callSign / vesselType / vesselFlag / vesselOwner	Vessel/aircraft details where applicable

Input

{ "names": ["Gazprom", "Wagner Group"], "minScore": 85, "includeClears": true }

• Names to screen - one per line. Import from a file - paste a list, or link a public .txt/.csv, a Google Sheet/Drive link, or an Apify key-value-store record.
• Lists - SDN, Consolidated, or both. Entity types - individuals / companies / vessels / aircraft.
• Programs - keep only matches in given OFAC programs (e.g. SDGT, RUSSIA-EO14024).
• Minimum score - 100 = exact name; 85 (default) also catches full-word-subset matches.
• Include clear results - one auditable row per name with no match (on by default).

Leave everything empty and the run returns a small free sample so you can see both result shapes.

Reliability

Downloads the current lists straight from the US Treasury (with the Sanctions List Service as an automatic failover) at the start of every run, so results always reflect OFAC's latest published data. No key, no anti-bot. If the downloads fail, the run says so and bills $0.

Honest limits

• This is OFAC only - the US Treasury SDN + Consolidated lists. It does not cover EU, UN or UK lists, or the BIS export-control entity list (e.g. Aeroflot is BIS-listed, not OFAC-listed, so it screens clear here - correctly).
• A match is a lead, not a legal verdict. Fuzzy name matching cannot replace a compliance review; use score, remarks (DOB/passport) and addresses to adjudicate.
• Vessel fields fill only for vessels, aircraft details only for aircraft - by nature of the data.
• Clear rows carry nulls in the match columns - that is what an all-clear looks like.

Pricing

$0.002 per screening result on the FREE tier (tiered pricing lowers it with volume). Only saved rows are billed - a failed download or an empty run costs nothing.

Output views

• Screening results - screened name, match flag, score, matched name, list, type, programs, entity.

Use with AI assistants (MCP)

Available through the Apify MCP server - an agent can screen a counterparty before a transaction, batch-check a vendor list, or pull the full OFAC record (aliases, programs, addresses) for a flagged name in one call.

Agent-ready: autonomous payments (x402 & Skyfire)

This actor is agent-ready - AI agents can discover it, run it, and pay for it autonomously, with no Apify account and no human in the loop. It uses pay-per-event pricing and limited permissions, so it qualifies for Apify's agentic-payment standards:

• x402 - an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the Apify MCP server - no account, no API key.
• Skyfire - agent-to-service payments for fully autonomous AI-agent workflows.

Building an AI agent, MCP tool, or autonomous data pipeline? This scraper is ready to plug in and pay as it goes.