# EU Consolidated Financial Sanctions Screening (FSF) (`itulo/eu-sanctions-screen`) Actor

Screen names, companies & IDs against the official EU Consolidated Financial Sanctions List (DG FISMA FSF). Exact matches & 'possible match' fuzzy similarity, list publication date, source attribution & legal disclaimer in every record. Not legal advice.

- **URL**: https://apify.com/itulo/eu-sanctions-screen.md
- **Developed by:** [Italo Armenti](https://apify.com/itulo) (community)
- **Categories:** Business, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 screened query / entity rows

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

## EU Consolidated Financial Sanctions Screening API (`itulo/eu-sanctions-screen`)

Screen company names, individuals, EU sanctions reference numbers (`EU.xx.xx`), UN IDs, and tax/registration numbers against the official **European Commission Consolidated Financial Sanctions List (DG FISMA — Financial Sanctions Files, CSV 1.1)**. Built for KYC/KYB onboarding, trade compliance, accounts-payable screening, and AI compliance agents.

Ships as both a **Pay-Per-Event Apify Actor** (`itulo/eu-sanctions-screen`) and an open-source **stdio MCP Server** (`src/mcp-server.js`).

> **Disclaimer — Not Legal Advice:** Screening results are informational aids only and do not constitute a legal determination of sanctions status. Fuzzy matches are strictly labeled **`"possible match"`** for human review. Only the regulations published in the **Official Journal of the European Union** are legally binding. Independent tool; not affiliated with or endorsed by the European Commission.

***

### Key Features for EU KYC / KYB & Sanctions Compliance

- **Unified Entity Index:** Collapses the ~25 MB official DG FISMA FSF CSV 1.1 into unified entity records with all transliterated aliases, functions/titles, birth dates, citizenships, addresses, passport/registration IDs, programme codes (`RUS`, `BLR`, `IRN`, `SYR`, etc.), and Official Journal regulation URLs.
- **Exact & Non-Distorting Fuzzy Screening:**
  - **Exact Match (`score = 1.0`):** Exact normalized match on primary name, any listed alias, `Entity_EU_ReferenceNumber`, `Entity_UnitedNationId`, or `Identification_Number`.
  - **Possible Match (`score < 1.0`):** Composite Jaro-Winkler + token-order-independent similarity. Per Commission Decision 2011/833/EU Art. 6(2), every non-exact candidate is explicitly labeled `"possible match (fuzzy similarity — manual review against the Official Journal required; not a determination)"`.
- **Mandatory Audit Trail Envelope:** Every output record includes `listPublicationDate`, `fileGenerationDate`, `disclaimer`, and `attribution`.

***

### Pay-Per-Event Pricing (`PAY_PER_EVENT`)

| Event Name | Price (USD) | Description |
|---|---|---|
| `actor-start` | **$0.01 / run** | Flat fee for starting an Actor run |
| `screened-query` | **$0.002 / query** ($2.00 / 1,000) | Each screened query or sanctions match row written to the dataset (primary event) |

***

### Data Licence & Attribution Compliance

- **Official Source:** European Commission, DG FISMA — Financial Sanctions Files (FSF), Consolidated list of persons, groups and entities subject to EU financial sanctions (`data.europa.eu`).
- **Licence:** Reused under **European Commission Decision 2011/833/EU** on the reuse of Commission documents.

***

### Connect to Claude Desktop, Cursor & MCP Clients (Model Context Protocol)

You can use **`itulo/eu-sanctions-screen`** as a live tool inside **Claude Desktop**, **Cursor**, **Windsurf**, or any MCP-compatible AI agent in two ways:

#### Option A: Hosted Apify MCP Server (`@apify/actors-mcp-server`)

Zero local setup required. Add this to your `claude_desktop_config.json` (macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`, Windows: `%APPDATA%\Claude\claude_desktop_config.json`) or Cursor `.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "eu-sanctions-screen": {
      "command": "npx",
      "args": [
        "-y",
        "@apify/actors-mcp-server",
        "--actors",
        "itulo/eu-sanctions-screen"
      ],
      "env": {
        "APIFY_TOKEN": "YOUR_APIFY_API_TOKEN"
      }
    }
  }
}
```

#### Option B: Local Stdio MCP Server (Open-Source CLI)

Run the bundled stdio MCP server (`src/mcp-server.js`) directly on your machine. Exposed MCP tools: `eu_sanctions_screen`, `eu_sanctions_lookup`, `eu_sanctions_list_info`.

```json
{
  "mcpServers": {
    "eu-sanctions-screen-local": {
      "command": "node",
      "args": [
        "/absolute/path/to/tools/eu-sanctions-screen/src/mcp-server.js"
      ]
    }
  }
}
```

***

### n8n, Make.com & REST API Integration (One-Call Sync JSON)

Trigger **`itulo/eu-sanctions-screen`** synchronously and get the normalized JSON dataset items back in a single HTTP request — ideal for **n8n `HTTP Request` nodes**, **Make.com**, **Zapier**, or cron webhooks:

- **Method:** `POST`
- **Endpoint:** `https://api.apify.com/v2/acts/itulo~eu-sanctions-screen/run-sync-get-dataset-items?token=YOUR_APIFY_API_TOKEN`
- **Headers:** `Content-Type: application/json`

#### cURL Example

```bash
curl -s -X POST \
  "https://api.apify.com/v2/acts/itulo~eu-sanctions-screen/run-sync-get-dataset-items?token=${APIFY_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{"queries":["Saddam Hussein Al-Tikriti","Clean Nordic Logistics Oy"],"subjectType":"all","fuzzyThreshold":0.78,"maxMatchesPerQuery":5,"includeClearQueries":true}'
```

***

### LangChain, CrewAI, Node.js & Python SDK Snippets

#### Node.js (`apify-client`)

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

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('itulo/eu-sanctions-screen').call({
  "queries": [
    "Saddam Hussein Al-Tikriti",
    "Clean Nordic Logistics Oy"
  ],
  "subjectType": "all",
  "fuzzyThreshold": 0.78,
  "maxMatchesPerQuery": 5,
  "includeClearQueries": true
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);
```

#### Python (`apify-client` / LangChain `ApifyWrapper` / CrewAI)

```python
import os
from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("itulo/eu-sanctions-screen").call(run_input={
  "queries": [
    "Saddam Hussein Al-Tikriti",
    "Clean Nordic Logistics Oy"
  ],
  "subjectType": "all",
  "fuzzyThreshold": 0.78,
  "maxMatchesPerQuery": 5,
  "includeClearQueries": true
})
items = client.dataset(run["defaultDatasetId"]).list_items().items
for row in items:
    print(row)
```

#### LangChain Python Tool

```python
from langchain_community.utilities import ApifyWrapper

apify = ApifyWrapper()
loader = apify.call_actor(
    actor_id="itulo/eu-sanctions-screen",
    run_input={
  "queries": [
    "Saddam Hussein Al-Tikriti",
    "Clean Nordic Logistics Oy"
  ],
  "subjectType": "all",
  "fuzzyThreshold": 0.78,
  "maxMatchesPerQuery": 5,
  "includeClearQueries": true
},
    dataset_mapping_function=lambda item: str(item),
)
docs = loader.load()
```

***

### Frequently Asked Questions (FAQ)

#### Where does the EU Sanctions Screening API get its sanctions list data?

It fetches and parses the official European Commission DG FISMA Consolidated Financial Sanctions Files (FSF CSV 1.1) published on the EU Open Data Portal (`data.europa.eu` / `webgate.ec.europa.eu/fsd/fsf`), collapsing all aliases, birth dates, nationalities, identification numbers, and Official Journal legal basis links into unified entity records.

#### How are exact matches vs. fuzzy matches scored and labeled?

An exact normalized match on a primary name, alias, EU reference number (`EU.xx.xx`), UN ID, or passport/registration number returns `score = 1.0` (`matchType: "exact"`). Non-exact matches above `fuzzyThreshold` use composite Jaro-Winkler + token-order-independent scoring and are strictly labeled `"possible match"` for human compliance review against the Official Journal.

#### Can I screen an entire batch of counterparty names in one API call?

Yes. Pass hundreds of company or individual names in the `queries` array. The actor loads and indexes the consolidated EU sanctions list once in memory and screens the entire batch in milliseconds.

**Related Search Keywords:** EU Sanctions Screening API · EU Consolidated Financial Sanctions List API · DG FISMA FSF Sanctions Check · KYC AML Sanctions Screening Europe · Fuzzy Name Matching EU Sanctions · EU Sanctions MCP Server

# Actor input Schema

## `queries` (type: `array`):

Names of persons, companies/entities, EU reference numbers (e.g. EU.27.28), or identification/registration numbers to screen against the EU Consolidated Financial Sanctions List.

## `subjectType` (type: `string`):

Filter sanctions entries by subject classification: all, person, or enterprise.

## `programmes` (type: `array`):

Optional filter by EU sanctions programme codes (e.g. RUS, UKR, BLR, IRN, SYR, IRQ).

## `country` (type: `string`):

Optional 2-letter ISO country code (e.g. RU, BY, IR, IQ) to restrict candidate entities by citizenship, address, birth or ID country.

## `fuzzyThreshold` (type: `number`):

Minimum similarity score \[0.50..1.00] to report a non-exact candidate as a 'possible match'. Default: 0.78. Set to 1.0 for exact matches only.

## `maxMatchesPerQuery` (type: `integer`):

Maximum number of candidate sanctions entries returned per screened query.

## `includeClearQueries` (type: `boolean`):

When enabled, queries with zero matches still emit a 'clear' audit row in the output dataset.

## Actor input object example

```json
{
  "queries": [
    "Saddam Hussein Al-Tikriti",
    "Example Clean Company Oy"
  ],
  "subjectType": "all",
  "programmes": [],
  "fuzzyThreshold": 0.78,
  "maxMatchesPerQuery": 5,
  "includeClearQueries": true
}
```

# Actor output Schema

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

Exact and possible-match fuzzy screening results against the official DG FISMA Consolidated Financial Sanctions List (FSF).

## `summary` (type: `string`):

Summary metadata and licence attribution stored in the default key-value store.

# 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 = {
    "queries": [
        "Saddam Hussein Al-Tikriti",
        "Example Clean Company Oy"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("itulo/eu-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 = { "queries": [
        "Saddam Hussein Al-Tikriti",
        "Example Clean Company Oy",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("itulo/eu-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 '{
  "queries": [
    "Saddam Hussein Al-Tikriti",
    "Example Clean Company Oy"
  ]
}' |
apify call itulo/eu-sanctions-screen --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,itulo/eu-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/726vgLbzE8fO96XZr/builds/DtxLa6OmNavMHpXKj/openapi.json