# Sanctions Screening: OFAC, UN, EU, UK + Crypto Address (`calcio_you/sanctions-screening`) Actor

Screen people, companies and crypto addresses against the official OFAC SDN, UN, EU and UK sanctions lists in one call. Fuzzy name matching, scores, programmes. Built for AI agents and KYC/AML workflows. Pay per check.

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

## Pricing

Pay per event

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

## Sanctions Screening API (OFAC, UN, EU, UK) + Crypto Address Check

Screen a **person, company or crypto address** against the four main official sanctions lists in one run:

- **US OFAC SDN** list (with aliases, addresses and the digital currency addresses published by OFAC)
- **UN Security Council** Consolidated List
- **EU** Consolidated Financial Sanctions List
- **UK** Sanctions List (FCDO)

The lists are downloaded **live from the issuing authorities at the start of every run**, so you always screen against the current data. Fuzzy matching handles word order, accents, aliases and small typos. Optional filters (country, subject type, birth year) cut false positives.

Built for **AI agents** (via the Apify MCP server or API), KYC/AML onboarding flows, marketplaces, fintech back-offices and crypto payment checks.

### Why use it

- **4 official lists in one call**: no need to integrate 4 different file formats.
- **Crypto addresses**: checks BTC, ETH/EVM, TRON, LTC, XMR, SOL, DASH and ZEC addresses against every address OFAC has sanctioned.
- **Explainable**: every match comes with score, list, entity ID, programmes, countries, birth years and the remarks of the listing.
- **Pay only for results**: you pay per successful check, never for errors, and there is no start fee.

### Use cases

- An AI agent onboarding a new customer or supplier asks: "Is this company sanctioned?"
- A payment flow checks a wallet address before accepting a crypto payment.
- A compliance analyst bulk-screens a list of counterparties every week.
- A marketplace screens sellers' legal names at signup.

### Input

| Field | What it does |
|---|---|
| `names` | List of person or company names (Latin script). One check per name. |
| `cryptoAddresses` | List of crypto addresses. One check per address. |
| `subjectType` | `any` (default), `person`, `entity`, `vessel`, `aircraft`. |
| `country` | Optional ISO-2 code or country name of the subject (boosts matches from that country). |
| `birthYear` | Optional birth year of a person (boosts matches ±1 year, penalises others). |
| `threshold` | Minimum match score 60-100 (default 85). |
| `lists` | Subset of `ofac`, `un`, `eu`, `uk` (default: all four). |
| `maxMatchesPerName` | Max matches returned per name (default 10). |
| `queries` | Advanced: per-query parameters, see below. |

Example:

```json
{
  "names": ["Vladimir Putin", "Satya Nadella", "Rosneft"],
  "cryptoAddresses": ["TNiq9AXBp9EjUqhDhrwrfvAA8U3GUQZH81"],
  "subjectType": "any",
  "threshold": 85
}
```

Advanced, per-query parameters:

```json
{
  "queries": [
    {"endpoint": "sanctions_screen", "params": {"name": "Rosneft", "type": "entity", "country": "RU"}},
    {"endpoint": "sanctions_crypto_address", "params": {"address": "0x..."}}
  ]
}
```

### Output

One dataset item per check. Example for `"Vladimir Putin"` (shortened):

```json
{
  "endpoint": "sanctions_screen",
  "input": {"name": "Vladimir Putin", "type": "any"},
  "ok": true,
  "result": {
    "status": "potential_match",
    "match_count": 3,
    "top_score": 100.0,
    "matches": [
      {
        "list": "OFAC SDN (US)",
        "entity_id": "ofac:35096",
        "name": "PUTIN, Vladimir Vladimirovich",
        "score": 100.0,
        "type": "person",
        "programs": ["RUSSIA-EO14024"],
        "countries": ["RU"],
        "birth_years": [1952]
      }
    ],
    "lists_checked": [
      {"list": "OFAC SDN (US)", "entities": 19471},
      {"list": "UN Security Council Consolidated List", "entities": 1010},
      {"list": "EU Consolidated Financial Sanctions List", "entities": 6234},
      {"list": "UK Sanctions List (FCDO)", "entities": 6408}
    ],
    "disclaimer": "Automated name screening against official lists: a potential match is a signal for human review..."
  },
  "charged_event": "sanctions-screen",
  "price_usd": 0.01
}
```

`"Satya Nadella"` returns `"status": "no_match"`. The TRON address above returns `"status": "sanctioned_address"` (Bank Markazi, Iran, OFAC programmes IRAN / SDGT / IRGC).

### Pricing (pay per event)

| Event | Price |
|---|---|
| Name screened (successful result) | $0.01 |
| Crypto address checked (successful result) | $0.005 |

No start fee. Invalid input, unsupported address format, source outage or internal error: **not charged** (the item says `"ok": false` and why). You can cap your spend with the "Max cost per run" option.

### Honest limits

- **This is a screening signal, not a compliance decision.** A potential match must be reviewed by a human and confirmed with identifiers (date of birth, nationality, ID numbers). This is not legal advice.
- **No PEP lists and no adverse media**: only official sanctions lists.
- Names in Cyrillic or Arabic script are **not transliterated**: query in Latin script (the official Latin spellings of the lists are covered).
- Only OFAC publishes sanctioned crypto addresses: an address not found is not proof of legitimacy.
- If an official source is down at run time, the Actor falls back to a recent bundled copy and says so in `data_snapshot_used`; if a single list cannot be loaded at all, it appears in `list_errors`.

### Data sources and licences

- OFAC SDN List (US Treasury), US Government work, public domain
- UN Security Council Consolidated List, public UN document
- EU Consolidated Financial Sanctions List, EU open data (Decision 2011/833/EU)
- UK Sanctions List (FCDO), Open Government Licence v3.0

Made by Novarithm, AI agents and automation. Questions or a missing list: contact@novarithm.com

***

Want this whole store under your brand? → https://gogeta2-u35175.vm.elestio.app/agents/clones/en/cases/api-store-for-ai-agents/

# Actor input Schema

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

People or companies to screen (Latin script). One charged check per name.

## `cryptoAddresses` (type: `array`):

BTC, ETH/EVM, TRON, LTC, XMR, SOL, DASH, ZEC addresses checked against OFAC-listed addresses. One charged check per address.

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

Restrict name matches to one subject type.

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

ISO-2 code or country name (e.g. RU, IR, AE). Boosts matches from that country and penalises others.

## `birthYear` (type: `integer`):

Boosts matches with the same birth year (±1), penalises others.

## `threshold` (type: `integer`):

Lower = more potential matches (more false positives).

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

Leave empty to check all four lists.

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

Best matches kept per name, sorted by score.

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

Per-query parameters, e.g. \[{"endpoint": "sanctions_screen", "params": {"name": "Rosneft", "type": "entity", "country": "RU"}}, {"endpoint": "sanctions_crypto_address", "params": {"address": "0x..."}}]

## `maxQueries` (type: `integer`):

Safety cap: only the first N checks of the input are processed.

## Actor input object example

```json
{
  "names": [
    "Vladimir Putin",
    "Satya Nadella"
  ],
  "cryptoAddresses": [
    "TNiq9AXBp9EjUqhDhrwrfvAA8U3GUQZH81"
  ],
  "subjectType": "any",
  "threshold": 85,
  "maxMatchesPerName": 10,
  "maxQueries": 1000
}
```

# Actor output Schema

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

All result items in the default dataset (JSON).

# 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": [
        "Vladimir Putin",
        "Satya Nadella"
    ],
    "cryptoAddresses": [
        "TNiq9AXBp9EjUqhDhrwrfvAA8U3GUQZH81"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("calcio_you/sanctions-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": [
        "Vladimir Putin",
        "Satya Nadella",
    ],
    "cryptoAddresses": ["TNiq9AXBp9EjUqhDhrwrfvAA8U3GUQZH81"],
}

# Run the Actor and wait for it to finish
run = client.actor("calcio_you/sanctions-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": [
    "Vladimir Putin",
    "Satya Nadella"
  ],
  "cryptoAddresses": [
    "TNiq9AXBp9EjUqhDhrwrfvAA8U3GUQZH81"
  ]
}' |
apify call calcio_you/sanctions-screening --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,calcio_you/sanctions-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/fftzNIRGb26oaZ0cU/builds/DeXzOc6AkpEA72nCU/openapi.json