# OFAC SDN Sanctions Screener — Name Matching (`v0iddo/ofac-sdn-screener`) Actor

Screen names against OFAC SDN (Specially Designated Nationals) — the primary US sanctions list. Joins sdn.csv + alt.csv + add.csv for full names, aliases, addresses. Returns matches with similarity score, programs, type, addresses. Daily-refreshed from treasury.gov. No auth.

- **URL**: https://apify.com/v0iddo/ofac-sdn-screener.md
- **Developed by:** [vøiddo](https://apify.com/v0iddo) (community)
- **Categories:** Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$20.00 / 1,000 sdn match returneds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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 SDN Sanctions Screener — Name Matching

Screen any list of names against the **OFAC SDN list** — Specially Designated Nationals and Blocked Persons, the primary US sanctions list maintained by Treasury. ~13,000 entities. Joins `sdn.csv` + `alt.csv` + `add.csv` for full names, aliases, addresses.

Built for **KYC / compliance / AML / sanctions screening** workflows. No login, no API key — pulls fresh files from treasury.gov on each run.

### Two modes

#### `screen` (default) — name matching

```json
{
  "mode": "screen",
  "names": ["John Smith", "Acme Trading Co"],
  "minScore": 60
}
```

Output: one row per match per input name. Includes match score (0-100) for downstream thresholding.

#### `dump` — full list export

```json
{ "mode": "dump" }
```

Output: one row per SDN entity. Use for ETL or building your own screening logic.

### Inputs

| input | default | notes |
|---|---|---|
| `mode` | `screen` | `screen` or `dump`. |
| `names` | `[]` | Required when `mode=screen`. |
| `minScore` | `60` | Drop matches below this. `100` = exact only. |
| `typesFilter` | all | Restrict by entity type: `Individual`, `Entity`, `Vessel`, `Aircraft`. |
| `programsFilter` | all | Restrict to specific OFAC programs: `IRAN`, `RUSSIA-EO14024`, `SDGT`, `NARCOTICS`, `CUBA`, etc. |

### Output schema

| field | example |
|---|---|
| inputName | `John Smith` (screen mode only) |
| matchScore | `82` (screen mode only) |
| matchKind | `alt_name_substring` |
| matchedName | `Johnny Smith` (screen mode only) |
| entityNumber | `12345` |
| name | canonical SDN name |
| type | `Individual` |
| programs | `["IRAN", "SDGT"]` |
| title | (when present) |
| altNames | `[{"type": "aka", "name": "..."}, ...]` |
| addresses | `[{"address": "...", "cityState": "...", "country": "..."}]` |
| remarks | (when present) |
| vesselType | `Tanker` (when type=Vessel) |
| callSign | (when applicable) |
| tonnage | (when applicable) |
| vesselFlag | (when applicable) |
| vesselOwner | (when applicable) |

### Scoring

Deterministic, no ML:

- Exact normalized name → 100
- Exact alt-name → 95
- Input is substring of name → 90
- Name is substring of input → 80
- Token overlap (Jaccard) → up to 75

Normalization: lowercase, strip punctuation, collapse whitespace.

### What it doesn't do

- No EU / UN / UK / Canada / OFSI lists — OFAC SDN only. Other US lists (SSI, Entity List, MEU, ...) and EU/UN will be separate actors.
- No fuzzy / phonetic / NLP matching — deterministic scoring only.
- No "false positive flag" — that's your analyst's call.

### Maintained by

[vøiddo studio](https://voiddo.com) — small independent shop.

# Actor input Schema

## `mode` (type: `string`):

screen = match input names against SDN entries (one row per match). dump = export every SDN entry (one row per entity).

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

Used only in 'screen' mode. List of names/entities to check.

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

Drop matches below this. 60 is a sensible default. 100 = exact name only.

## `typesFilter` (type: `array`):

Empty = all. SDN types: Individual, Entity, Vessel, Aircraft.

## `programsFilter` (type: `array`):

Empty = all. Examples: IRAN, RUSSIA-EO14024, SDGT, NARCOTICS, CUBA. See treasury.gov for the full list.

## Actor input object example

```json
{
  "mode": "screen",
  "names": [],
  "minScore": 60,
  "typesFilter": [],
  "programsFilter": []
}
```

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("v0iddo/ofac-sdn-screener").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("v0iddo/ofac-sdn-screener").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 '{}' |
apify call v0iddo/ofac-sdn-screener --silent --output-dataset

```

## MCP server setup

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

```

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/nSxHxOrQYpvgBo1Xz/builds/xcUVm4hOU5dEyL867/openapi.json