# Wallet Risk Screener - $0.85/1K Addresses | Johto Data (`johto.data/wallet-risk-screener`) Actor

For AI agents and payment bots: screen crypto addresses before you pay or accept funds. Official OFAC SDN digital-currency match (all coins) and ScamSniffer phishing list. Verdict BLOCK/REVIEW/CLEAR, with list dates in listsAsOf.

- **URL**: https://apify.com/johto.data/wallet-risk-screener.md
- **Developed by:** [Jo](https://apify.com/johto.data) (community)
- **Categories:** Agents, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.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

## Wallet Risk Screener: OFAC SDN + Phishing List | Johto Data

### For AI agents

**Call it when** an address is about to send or receive value and you need a sanctions and phishing check. One row per address: `verdict` (`BLOCK` / `REVIEW` / `CLEAR`), `riskScore` (0–100), `flags` and the evidence.

**Input (exact field names):**

```json
{ "addresses": ["0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045", "0x252a8bd2319d8a555b872990601221b3a2053bce"] }
```

Any address format (BTC, ETH, TRX, XMR, SOL...) is matched against OFAC. EVM `0x` addresses are also matched against ScamSniffer.

**Don't call it when** you need counterparty or mixer-exposure tracing. It checks the address itself only. Not legal advice or a compliance program.

**Connect:** MCP `https://mcp.apify.com/?tools=johto.data/wallet-risk-screener`, or REST `POST https://api.apify.com/v2/acts/johto.data~wallet-risk-screener/run-sync-get-dataset-items`.

### Checks

| Check | Source | Needs |
|---|---|---|
| Sanctions | OFAC SDN Advanced XML, downloaded from US Treasury each run (`ofacSource: "live"`), with a bundled snapshot as fallback | Nothing |
| Phishing | ScamSniffer scam-database address list | Nothing |

These two lists are the only sources. The same checks power the Johto Data x402 `/v1/wallet-risk` route, with the same output field names.

### Output fields

`address, addressType, verdict, riskScore, flags[], summary, ofacSanctioned, ofacMatches[] {name, currency, programs[], ofacProfileId}, ofacListDate, ofacListMode, listsAsOf {ofacSdn, scamSniffer: name, asOf, fetchedAt, source}, scamSnifferListed, scamSnifferChecked, checkedAt, disclaimer`

### Verdict rules

`BLOCK` if the address is on the OFAC SDN list. `REVIEW` if the score is 40 or more. Otherwise `CLEAR`.

| Flag | Points |
|---|---|
| `OFAC_SDN_MATCH` | 100 |
| `SCAMSNIFFER_PHISHING_LIST` | 70 |

### Pricing (pay per event)

- `address-screened`: **$0.00085** per address.
- `apify-actor-start`: $0.00004 per run.
- Example: 100 addresses = $0.085.

### Limits

- `CLEAR` means "not found on these lists", not "safe".
- Results are only as current as the source lists at run time. Each row's `listsAsOf` shows each list's date, fetch time and source URL. ScamSniffer publishes its list with a 7-day delay.

### Data sources and licenses

- **OFAC SDN list:** US Treasury, Office of Foreign Assets Control. US government work, public domain.
- **ScamSniffer scam-database:** https://github.com/scamsniffer/scam-database, licensed under GPL-3.0 (https://www.gnu.org/licenses/gpl-3.0.html). Address list read from the `address` array of `https://raw.githubusercontent.com/scamsniffer/scam-database/main/blacklist/all.json`.

Not affiliated with US Treasury or ScamSniffer.

# Actor input Schema

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

Crypto addresses to screen, one per line. Any format (EVM, BTC, TRX, XMR, SOL...) is matched against OFAC SDN; EVM 0x addresses are also matched against ScamSniffer. Use when: an address is about to send or receive value and you need a sanctions and phishing check. Don't use when: you need counterparty, mixer-exposure or fund-flow tracing (this checks the address itself only).

## `ofacSource` (type: `string`):

live = download the official SDN Advanced XML from US Treasury (falls back to the bundled snapshot on failure). snapshot = bundled list only. Use live when you want the latest list each run. Use snapshot when you want the fastest, cheapest run and accept the bundled list date (shown in listsAsOf.ofacSdn).

## `checkScamSniffer` (type: `boolean`):

Match EVM addresses against the ScamSniffer scam-database address list (GPL-3.0). Use when screening EVM addresses for phishing. Turn off when you only need the OFAC result.

## `maxAddresses` (type: `integer`):

Cap per run. Each screened address is one charged result ($0.00085). Use it to cap spend on large lists.

## Actor input object example

```json
{
  "addresses": [
    "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
    "0x252a8bd2319d8a555b872990601221b3a2053bce"
  ],
  "ofacSource": "live",
  "checkScamSniffer": true,
  "maxAddresses": 100
}
```

# Actor output Schema

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

No description

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

No description

# 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": [
        "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
        "0x252a8bd2319d8a555b872990601221b3a2053bce"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("johto.data/wallet-risk-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": [
        "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
        "0x252a8bd2319d8a555b872990601221b3a2053bce",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("johto.data/wallet-risk-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": [
    "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
    "0x252a8bd2319d8a555b872990601221b3a2053bce"
  ]
}' |
apify call johto.data/wallet-risk-screener --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,johto.data/wallet-risk-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/ehRJXS4emAIAbSBPw/builds/NlsXKA0UFZcVszR3N/openapi.json