# Crypto Address Risk & AML Screener - OFAC Sanctions + On-Chain (`centorprat/crypto-address-risk-aml-screener`) Actor

Give crypto addresses. Each is screened against OFAC-published sanctioned digital-currency addresses (13 chains); Bitcoin addresses also get a keyless on-chain check for direct sanctioned-counterparty exposure + risk indicators, into a risk score, band and findings. Read-only, agent-callable.

- **URL**: https://apify.com/centorprat/crypto-address-risk-aml-screener.md
- **Developed by:** [Centor Prat](https://apify.com/centorprat) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $17.00 / 1,000 address 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

## Crypto Address Risk & AML Screener — OFAC Sanctions + On-Chain

Screen crypto addresses before you transact. Give one or more addresses and each is checked against the **OFAC-published list of sanctioned digital-currency addresses** (13 chains) **and**, for Bitcoin, against the public blockchain to see whether it has **transacted directly with a sanctioned address** (one-hop exposure) plus on-chain risk indicators — returned as a **risk score, band, findings and a human-review signal**. Keyless, read-only, public data only — agent-callable.

For compliance / KYC / AML teams, fintech & exchange ops, OTC desks, and AI agents doing pre-transaction screening at scale.

### What it does

- **Sanctions screening** — checks each address against OFAC's published sanctioned digital-currency addresses across BTC, ETH, USDT, USDC, TRX, LTC, BCH, XMR, ZEC, DASH and more (~1,000+ addresses, sourced from a public OFAC-derived list, refreshed each run).
- **On-chain exposure (Bitcoin)** — reads the public ledger (keyless) and flags if any **direct counterparty** of the address is itself sanctioned.
- **On-chain risk indicators (Bitcoin)** — mixing-like fan-out, peeling chains, sweeping/consolidation, high-velocity bursts, large throughput.
- **Your own watchlist** — pass `extraSanctionedAddresses` to screen against your internal list too.

| Output field | Meaning |
|---|---|
| `riskScore` / `riskBand` | 0–100 and low / medium / elevated / high / critical |
| `signal` | sanctioned-match / sanctioned-exposure / elevated-risk / some-risk / no-indicators |
| `findings[]` | each risk indicator with severity + detail |
| `sanctionedCounterparties[]` | (BTC) direct counterparties that are sanctioned |
| `balanceBtc`, `totalReceivedBtc`, `txCount`, `uniqueCounterparties` | (BTC) on-chain context |
| `chain` | detected chain |

### Why not just ask an AI agent?

An agent can be told "is this address sanctioned?" and might check one list. It **can't** cheaply pull the latest OFAC list across 13 chains, read an address's recent transactions, intersect every counterparty against that list, and compute the mixing/peeling/velocity indicators — consistently and the same way each time. That cross-referenced, multi-source computation is what this actor delivers.

### Input

| Field | Type | Required | Description |
|---|---|---|---|
| `addresses` | array of strings | ✅ | Crypto addresses to screen. |
| `extraSanctionedAddresses` | array of strings | | Your own watchlist to flag in addition to OFAC. |
| `webhookUrl` | string | | POST the finished screenings here as JSON. |

**Example input**

```json
{
  "addresses": [
    "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa",
    "0x0000000000000000000000000000000000000000"
  ]
}
```

### Output

One record per address. **Example output** (clean address, real run):

```json
{
  "address": "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa",
  "chain": "BTC",
  "signal": "no-risk-indicators-found",
  "riskBand": "low",
  "riskScore": 0,
  "balanceBtc": 57.66512665,
  "txCount": 66959,
  "uniqueCounterparties": 18,
  "sanctionedCounterparties": [],
  "findings": [],
  "disclaimer": "Signals for human review from public data ... NOT a verdict ... absence of a match is NOT proof an address is clean."
}
```

When an address **is** on the sanctioned list, `signal` is `sanctioned-match--do-not-transact`, `riskBand` is `critical`, and `findings[]` names the chain. When a Bitcoin address has paid or been paid by a sanctioned address, `signal` is `sanctioned-exposure--review-required` and `sanctionedCounterparties[]` lists them.

### Use cases

- **Pre-transaction / onboarding checks** — screen a counterparty address before sending or accepting funds.
- **Exchange / fintech AML ops** — batch-screen deposit or withdrawal addresses.
- **OTC & treasury** — confirm an address isn't sanctioned or exposed before a large transfer.
- **AI compliance agents** — one call returns a structured risk screening to gate an action.

### For AI agents / MCP

```
https://mcp.apify.com/?tools=actors,docs,centorprat/crypto-address-risk-aml-screener
```

Loads as the tool `centorprat--crypto-address-risk-aml-screener`. Claude Code:

```
claude mcp add apify -- npx -y @apify/actors-mcp-server --actors centorprat/crypto-address-risk-aml-screener
```

### Alerts / scheduling

Set `webhookUrl` and schedule a re-screen of watched addresses — the OFAC list changes, and a previously-clean address can gain sanctioned exposure; the fresh result is POSTed to Make/Zapier/your endpoint.

### FAQ

**Where does the sanctions data come from?** OFAC publishes sanctioned digital-currency addresses in its SDN program. This actor loads them from a public OFAC-derived list covering 13 chains, fetched fresh on every run.

**Which chains get on-chain analysis?** Bitcoin, via keyless public explorers. For other chains the result is the sanctions-list screening (self-match) plus format detection — no key required, no partial/unreliable data.

**Does a "critical" result mean the owner is a criminal?** No. These are **signals for human review**. A sanctions-list match means do not transact and escalate to compliance; on-chain indicators are context to review — never an accusation about a person.

**Does "no-risk-indicators-found" mean the address is safe?** No. Absence of a match is **not** proof an address is clean — it only means nothing was found in the public data checked.

**Is this legal / allowed?** It reads only public data: the US-government-published sanctions list and the public blockchain. No keys, no private data, no deanonymisation.

**How current is the list?** Fetched on each run, so it reflects the latest published list.

**How fast / how much?** A couple of seconds per batch. Pay-per-event, one charge per address screened.

### Data & attribution

Sanctions data originates from the U.S. Treasury OFAC SDN program (public domain), loaded via a public OFAC-derived address list; Bitcoin on-chain data via the keyless Blockstream Esplora API (mempool.space fallback). No keys, no personal data. Results are computed signals, not legal or compliance advice — always confirm with your own compliance process.

### Related actors

- [Bitcoin Wallet & Transaction Tracer](https://apify.com/centorprat/bitcoin-wallet-transaction-tracer)
- [Sanctions & Watchlist Screening](https://apify.com/centorprat/sanctions-watchlist-screening)

# Actor input Schema

## `addresses` (type: `array`):

Crypto addresses (BTC, ETH/ERC-20, TRX, LTC, ... ). One risk screening per address.

## `extraSanctionedAddresses` (type: `array`):

Extra addresses to treat as flagged, in addition to the OFAC list (your internal watchlist).

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

If set, the finished screenings are POSTed here as JSON when the run completes.

## Actor input object example

```json
{
  "addresses": [
    "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa",
    "0x0000000000000000000000000000000000000000"
  ]
}
```

# Actor output Schema

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

One risk screening per address: sanctions-list match, (Bitcoin) direct sanctioned-counterparty exposure and on-chain risk indicators, a risk score, band, findings and a human-review signal.

# 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 = {
    "addresses": [
        "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa",
        "0x0000000000000000000000000000000000000000"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("centorprat/crypto-address-risk-aml-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 = { "addresses": [
        "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa",
        "0x0000000000000000000000000000000000000000",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("centorprat/crypto-address-risk-aml-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 '{
  "addresses": [
    "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa",
    "0x0000000000000000000000000000000000000000"
  ]
}' |
apify call centorprat/crypto-address-risk-aml-screener --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,centorprat/crypto-address-risk-aml-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/fuh0gAfuX0HNmicz4/builds/kFDiN6gCeCCd2xP5x/openapi.json