# Sanctions & Watchlist Screening: OFAC SDN + UN Lists (`centorprat/sanctions-watchlist-screening`) Actor

Screens names of people or companies against keyless public sanctions lists - OFAC SDN and the UN Security Council Consolidated List (names + aliases). Returns one brief per name: scored possible matches + a review signal. Signals for human review, NOT a verdict; a name match is not identity proof.

- **URL**: https://apify.com/centorprat/sanctions-watchlist-screening.md
- **Developed by:** [Centor Prat](https://apify.com/centorprat) (community)
- **Categories:** Developer tools
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $8.50 / 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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

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

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Sanctions & Watchlist Screening: OFAC SDN + UN Lists

**Give it names of people or companies and get ONE screening brief per name** — scored possible matches
against public sanctions lists, with the match already done against every primary name *and* alias.
Keyless, agent-callable, built to answer *"does this party appear on a sanctions list, and what would a
reviewer need to decide?"*

> ⚠️ **Signals, not a verdict.** A match is a **possible name match** against the lists below and must be
> adjudicated by a human using secondary identifiers (date of birth, nationality, passport/ID). A name
> match is **not** confirmation of identity, and **absence of a match does not prove a party is
> unsanctioned** — lists change daily, spelling/transliteration varies, and most of the world's
> sanctions/watchlists are not covered here. This is a preliminary screen, never legal advice, a
> compliance determination, or an accusation.

### ⚡ Why it's different

Most sanctions actors on the Store hand you the **raw list dump** and leave the matching to you. This one
**takes your names and returns the answer**: it normalizes spelling and diacritics, matches each name
against primary names and **aliases** across multiple lists, scores every candidate, and emits a single
review signal per name. One call in, one decision-ready brief out.

### 🗂️ Lists screened (all keyless, no API key)

| List | Source |
|---|---|
| **OFAC SDN** | US Treasury — Specially Designated Nationals (+ alias/`alt` names) |
| **UN** | UN Security Council Consolidated List — individuals + entities (+ aliases) |
| **OFAC Consolidated** *(optional)* | US Treasury — non-SDN sanctions lists (+ aliases) |

### 📋 What each brief contains

| Field | Meaning |
|---|---|
| `query` / `normalizedQuery` | The name you gave, and its normalized form |
| `signal` | `strong-name-match…` / `possible-name-match…` / `weak-name-match…` / `no-match-in-screened-lists` (all "human-review-required" except no-match) |
| `matchCount` / `highestScore` | How many candidates, and the best score (0–100) |
| `singleTokenQuery` | `true` when you screened a single word (expect broad, lower-confidence matches) |
| `matches[]` | Per candidate: `score`, `listedName`, `matchedName`, `matchedVia` (primary/alias), `type`, `source`, `program`, `aliasesSample`, `details` (DOB, nationality, remarks), `listEntryId` |
| `listsScreened` | Each list used, its entry count and list date |
| `note` | The signals-only disclaimer |

### 📥 Input

```json
{ "names": ["Nicolas Maduro Moros", "Acme Trading LLC"], "lists": ["ofac_sdn", "un"], "minScore": 80 }
```

One brief per name. You can also point it at a `datasetId` (with an optional `datasetField`) to screen a
customer/supplier list produced by another Actor.

### 📤 Example output (real run, trimmed)

```json
{
  "query": "Nicolas Maduro Moros",
  "signal": "strong-name-match--human-review-required",
  "matchCount": 1, "highestScore": 99,
  "matches": [{
    "score": 99, "matchedVia": "primary",
    "listedName": "MADURO MOROS, Nicolas", "type": "individual",
    "source": "ofac_sdn", "program": "VENEZUELA, IRAN-CON-ARMS-EO",
    "details": { "title": "President of the Bolivarian Republic of Venezuela",
      "remarks": "DOB 23 Nov 1962; POB Caracas, Venezuela; citizen Venezuela; ..." }
  }],
  "note": "SIGNALS ONLY - not a compliance determination, legal advice, or an accusation. ..."
}
```

Other real results from the same run: `AEROCARIBBEAN AIRLINES` → **100** (OFAC SDN, program `CUBA`);
`Eric Badege` → **100** on the UN list (individual, DRC, DOB 1971) **and** 99 on OFAC SDN — one person,
both lists; `Allied Democratic Forces` → **100** via the UN alias `ADF`; `Jane Ordinary Baker-Smith` →
**no match in the screened lists** (returned honestly, not as a guarantee of clearance).

### 💰 Pricing (pay-per-event)

- **Name screened — $0.01** per name. Loading the lists once per run is shared and **not** charged.

### 💡 Use cases

- **KYC / onboarding / compliance:** a first-pass screen of a customer, counterparty, or beneficial owner.
- **Procurement / vendor vetting:** screen a supplier list (feed a `datasetId`) before contracting.
- **Fintech / marketplaces:** batch-screen new accounts and route only the signalled ones to a human.
- **Journalists / researchers:** check whether a named person or entity appears on OFAC/UN lists.

### 🔑 Keyless & agent-callable

No API keys, no accounts, no paid child Actors — just public government/UN data. Works as an MCP tool for
AI agents: give it names, get decision-ready signals back.

### 🚀 Ready-made tasks (one click)

- [OFAC SDN Name Screening - Fuzzy Match](https://apify.com/centorprat/sanctions-watchlist-screening/examples/ofac-sdn-name-screening)

### 🤖 For AI agents (MCP)

```
https://mcp.apify.com/?tools=actors,docs,centorprat/sanctions-watchlist-screening
```

Loads as `centorprat--sanctions-watchlist-screening`. Claude Code:

```
claude mcp add apify -- npx -y @apify/actors-mcp-server --actors centorprat/sanctions-watchlist-screening
```

# Actor input Schema

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

Names to screen, e.g. \["Nicolas Maduro Moros"], \["Acme Trading LLC", "Jane Doe"]. One brief per name. People and entities both work.

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

Which public sanctions lists to load. All keyless. OFAC SDN + UN by default.

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

Only return matches at or above this name-match score. 100 = exact; 85-99 = name fully contained; lower = partial. Default 80.

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

Cap the matches returned for each name (best first).

## `datasetId` (type: `string`):

Screen names pulled from an existing dataset you own (e.g. a customer/supplier list from another Actor).

## `datasetField` (type: `string`):

Which field holds the name in that dataset. If blank, common name fields are auto-detected (name, company, party, ...).

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

When a datasetId is given, cap how many rows to read.

## `webhookUrl` (type: `string`):

If set, all briefs are POSTed here as JSON when the run finishes.

## Actor input object example

```json
{
  "names": [
    "Nicolas Maduro Moros"
  ],
  "lists": [
    "ofac_sdn",
    "un"
  ],
  "minScore": 80,
  "maxMatchesPerName": 15,
  "maxItems": 5000
}
```

# Actor output Schema

## `briefs` (type: `string`):

One brief per name: the normalized query, the lists screened (with entry counts and list date), scored possible matches (listed name, aliases, type, sanctions program, DOB/nationality where available), a human-review signal, and a disclaimer. Signals only - not a compliance determination.

# 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": [
        "Nicolas Maduro Moros"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("centorprat/sanctions-watchlist-screening").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": ["Nicolas Maduro Moros"] }

# Run the Actor and wait for it to finish
run = client.actor("centorprat/sanctions-watchlist-screening").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": [
    "Nicolas Maduro Moros"
  ]
}' |
apify call centorprat/sanctions-watchlist-screening --silent --output-dataset

```

## MCP server setup

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

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/nmewF2UMadW5DQ5Jr/builds/70Pq2UZQy7nOjHrbh/openapi.json
