# OFAC Sanctions Screening - SDN and Consolidated Lists (`kdhan/ofac-sanctions-screen`) Actor

Screen names, aliases and ID numbers against the official US Treasury OFAC SDN and Consolidated (non-SDN) sanctions lists. Exact and fuzzy matches with scores, programs and official entry links. Possible matches only, no key, no birth dates or addresses.

- **URL**: https://apify.com/kdhan/ofac-sanctions-screen.md
- **Developed by:** [Doohan Kim](https://apify.com/kdhan) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 screening records

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?

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

## OFAC Sanctions Screening - SDN and Consolidated Lists

Screen names, aliases and ID numbers against the official US Treasury OFAC **SDN** list and the **Consolidated (non-SDN)** lists. The Actor downloads the current lists from the OFAC Sanctions List Service at the start of every run (no API key, no login), builds an in-memory index and compares each input.

**Possible matches only.** A name match is never a confirmation that a person or company is sanctioned. This Actor is not legal or compliance advice.

### Input

| Field | Meaning |
|---|---|
| `names` | People, companies, vessels, or identifiers (IMO, tax ID, registration numbers). Up to 200. Empty input screens the harmless example `Acme Trading LLC`. |
| `entityType` | `any` (default), `individual`, `entity`, `vessel`, `aircraft` - only compare against that type. |
| `minScore` | 0.8 to 1.0, default 0.9. |
| `maxMatches` | Matches returned per name, 1 to 25, default 5. |

### How matching works

- **1.00 exact** - same words after normalising case, accents and punctuation (`LAST, First` also matches `First LAST`).
- **0.97 reordered** - same words in a different order.
- **0.95 legal-form-ignored** - equal once words such as LLC, LTD, INC, JSC are ignored.
- **below 0.95 similar** - word-level fuzzy match (typos). Short words (4 letters or fewer) must match exactly; longer words tolerate 1-2 edits. Words missing on either side lower the score.
- **identifier** - exact match on a number in the official remarks (tax ID, registration number, IMO, MMSI, SWIFT/BIC, passport ...). The number itself is not repeated in the output for people and companies; only its type is.

Each match shows the list, `uid`, which name or alias matched, score, sanctions programs, entity type, selected notes (linked entities, secondary-sanctions notes, listing dates) and a link to the official entry. For individuals a matching **date of birth or nationality** is the strong evidence - check it on the official entry. Birth dates, places of birth, addresses and contact details are deliberately **not** output.

### Output (one row per input)

`found` (`true` = possible matches, `false` = none in either list, `null` = could not be screened completely), `complete`, `matches[]`, `screenedLists`, `dataAsOf` (publication timestamp of each list), `sectionErrors`, `note`, `error`, `disclaimer`.

If a list cannot be downloaded, `sectionErrors` says so, `found` stays `null` when nothing was matched, and the Actor never claims "no sanctions".

### Pricing event

`screening-record` - one per name screened against **both** lists. Names that could not be screened (list download failed, invalid entry) are free.

### Data source

OFAC Sanctions List Service legacy CSV exports (`SDN.CSV`, `ALT.CSV`, `SDN_COMMENTS.CSV`, `CONS_PRIM.CSV`, `CONS_ALT.CSV`, `CONS_COMMENTS.CSV`) at `sanctionslistservice.ofac.treas.gov`. Lists change frequently; always verify with the official **OFAC Sanctions List Search** (https://sanctionssearch.ofac.treas.gov) before acting. Not affiliated with or endorsed by the US Department of the Treasury.

# Actor input Schema

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

Person, company or vessel names, or identifiers such as an IMO or tax ID number. Up to 200 per run.

## `entityType` (type: `string`):

Only compare against list entries of this type.

## `minScore` (type: `number`):

Between 0.8 and 1.0. Lower values return more possible matches, including more false positives.

## `maxMatches` (type: `integer`):

Upper limit of listed entries returned for each name.

## Actor input object example

```json
{
  "names": [
    "Acme Trading LLC"
  ],
  "entityType": "any",
  "minScore": 0.9,
  "maxMatches": 5
}
```

# Actor output Schema

## `screenings` (type: `string`):

Per name: found flag, possible matches with score, matched name or alias, programs and official entry link, list publication dates, section errors and disclaimer.

# 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": [
        "Acme Trading LLC"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("kdhan/ofac-sanctions-screen").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": ["Acme Trading LLC"] }

# Run the Actor and wait for it to finish
run = client.actor("kdhan/ofac-sanctions-screen").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": [
    "Acme Trading LLC"
  ]
}' |
apify call kdhan/ofac-sanctions-screen --silent --output-dataset

```

## MCP server setup

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

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/tqZBIU3mdH2dMf8PU/builds/ofRHAHMj2Cg5W1MEX/openapi.json