# OFAC Sanctions Screening - SDN & Consolidated Lists (`scrapesage/ofac-sanctions-scraper`) Actor

Screen any list of names against US Treasury OFAC sanctions - the SDN and Consolidated lists - with fuzzy matching and match scores: aliases (AKA), programs, entity type, addresses and remarks per hit. Official public data, straight from OFAC - no API key, no browser.

- **URL**: https://apify.com/scrapesage/ofac-sanctions-scraper.md
- **Developed by:** [Scrape Sage](https://apify.com/scrapesage) (community)
- **Categories:** Other, Agents, Integrations
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.10 / 1,000 name screeneds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## 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

```json
{ "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](https://docs.apify.com/platform/integrations/mcp) - 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](https://docs.apify.com/platform/actors/publishing/monetize/pay-per-event) pricing and [limited permissions](https://docs.apify.com/platform/actors/development/permissions), so it qualifies for Apify's agentic-payment standards:

- **[x402](https://docs.apify.com/platform/integrations/x402)** - an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp) - no account, no API key.
- **[Skyfire](https://docs.apify.com/platform/integrations/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.

# Actor input Schema

## `names` (type: `array`):

People, companies, vessels or aircraft to screen against the OFAC sanctions lists, one per line. <b>Leave empty and the run returns a small free sample.</b>

## `namesFromFile` (type: `string`):

Bulk-load names. Either <b>paste the whole list</b> (one per line), or give <b>a single link</b> to a public <code>.txt</code>/<code>.csv</code>, a Google Sheet/Drive link, or an Apify key-value-store record. A file that cannot be read says so and charges nothing.

## `lists` (type: `array`):

Which OFAC lists to screen against. Leave empty for both.

## `entityTypes` (type: `array`):

Keep only matches of the selected entity types. Leave empty for all.

## `programs` (type: `array`):

Keep only matches tagged with these OFAC program codes, e.g. <code>SDGT</code>, <code>IRAN</code>, <code>RUSSIA-EO14024</code>, <code>SDNTK</code>, <code>CUBA</code>. Free text because OFAC adds new program codes over time; values are matched case-insensitively against each entity's program tags. Leave empty for all programs.

## `minScore` (type: `integer`):

How strict the fuzzy match is. 100 = exact normalized name only; 85 (default) also catches names whose words all appear in a listed name or alias; lower values catch partial-word overlaps.

## `maxMatchesPerName` (type: `integer`):

How many sanction-list hits to return per screened name (best scores first).

## `includeClears` (type: `boolean`):

Emit one row for every screened name that has NO match (an auditable all-clear). Turn off to output match rows only.

## `maxItems` (type: `integer`):

Overall cap on saved screening results. You are only charged for results actually saved.

## `outputFields` (type: `array`):

Pick the fields you want and every record is trimmed to exactly those - handy for lean CSV/Sheets exports.

## Actor input object example

```json
{
  "names": [
    "Gazprom",
    "Sberbank",
    "Aeroflot"
  ],
  "minScore": 85,
  "maxMatchesPerName": 5,
  "includeClears": true,
  "maxItems": 10000
}
```

# Actor output Schema

## `results` (type: `string`):

Each screening result - a sanctions match with score, aliases, programs and addresses, or an all-clear row - as a JSON item in the default dataset.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "names": [
        "Gazprom",
        "Sberbank",
        "Aeroflot"
    ],
    "namesFromFile": ""
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapesage/ofac-sanctions-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "names": [
        "Gazprom",
        "Sberbank",
        "Aeroflot",
    ],
    "namesFromFile": "",
}

# Run the Actor and wait for it to finish
run = client.actor("scrapesage/ofac-sanctions-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "names": [
    "Gazprom",
    "Sberbank",
    "Aeroflot"
  ],
  "namesFromFile": ""
}' |
apify call scrapesage/ofac-sanctions-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapesage/ofac-sanctions-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/eS9Qz9ILlqFdpt4yN/builds/v2B7K4UKqd43CBJL1/openapi.json