SANCTIONS SCREENING
OpenSanctions Sanctions & Watchlist Screener
Screen entity names and crypto wallet addresses against sanctions and watchlists: OFAC SDN by default plus EU, UK, UN and 470+ more lists.
About this data
Screen entity names and crypto wallet addresses against sanctions and watchlists: OFAC SDN by default plus EU, UK, UN and 470+ more lists. Each match comes with the list, confidence tier, programs, authorities and source links; every query that finds nothing gets an audit row.
From the actor’s Apify Store listing. The per-call endpoint may return a bounded subset; its own description is below.
Buy per call over x402
One endpoint at api.ssh.autos. Each call is one JSON POST, paid in USDC with no account or API key, and answered in the same HTTP response.
POST /v1/opensanctions/screen
Screen up to five person or company names against the US OFAC SDN list as compiled by OpenSanctions, matching exact names, aliases and addresses: one row per matched name with the entity, programs, match basis and source links; names with no match return no row.
The dataset cache is at most seven days old.
A screening aid, not a legal determination.
Input
Send a JSON body to POST https://api.ssh.autos/v1/opensanctions/screen.
| Field | Type | Required | Notes |
|---|---|---|---|
queries | array of strings | required | up to 5 items |
Returned fields
The answer is JSON: records, a list, and summary, the run status and counts. Each record has these 23 fields; a field the source does not publish comes back null.
23 fields per record
| Field | Type | Notes |
|---|---|---|
recordKey | string | — |
source | string | always opensanctions-bulk |
kind | string | always sanctions_screen |
query | string | Verbatim query as given in the input. |
queryType | string | one of name, address |
match | boolean | Whether the query matched any sanctioned target in the selected datasets. |
confidence | string | Match tier: exact = primary name, alias = AKA, address = crypto wallet publicKey. Null on no-match rows. one of exact, alias, address |
matchedName | string | The source label that matched (name/alias/address); multiple lists may disagree, then joined with '; '. |
caption | string | OpenSanctions caption for the matched target. |
targetType | string | FollowTheMoney schema of the target: Person, LegalEntity, Company, Organization, Vessel, CryptoWallet, Airplane, … |
lists | array of strings | Sanction dataset(s) the target was matched in (us_ofac_sdn, eu_fsf, …). |
countries | array of strings | — |
topics | array of strings | — |
programs | array of strings | Sanction programs (e.g. RUSSIA-EO14024, IRAN-HR) across lists. |
authorities | array of strings | Sanctioning authorities (e.g. Office of Foreign Assets Control). |
sanctions | array of objects | Per-list sanction designations: program, authority, country, reason, sourceUrl, authorityId, dataset. |
sourceUrl | string | Primary source URL (target's own source URL, else the sanction's). |
entityUrl | string | OpenSanctions entity profile page. |
publicKey | string | Matched crypto wallet address (address matches). |
currency | string | Wallet currency code (XBT, ETH, TRX, USDT, …). |
holderName | string | Sanctioned holder of the matched wallet, when OpenSanctions links one. |
datasetsMeta | array of objects | Per-run dataset provenance: dataset, generatedAt (upstream build), targets, entities, cache hit/miss, ageHours. |
screenedAt | string | — |
Example call
npx agentcash@latest fetch https://api.ssh.autos/v1/opensanctions/screen -m POST -b '{"queries": ["BANK MELLI IRAN"]}'The example values come from the API spec or the actor’s own sample input. Running it is a paid call.
What is and isn’t charged
You pay the call price for
- An answer, including a definitive “not found” or an empty result.
- Confirmed no matches returns records: [] (charged: it is an answer).
Free
- Invalid input (422), busy (503), source failure (502), timeout (504) and calls whose client hung up are never charged.
- Invalid input and source failures are not charged.
Prefer a subscription? Run it on Apify
This data source is a public actor on the Apify Store: OpenSanctions Sanctions & Watchlist Screener. Run it with your Apify account and plan for larger, scheduled or exported runs; it may offer more input options than the per-call endpoint.
How x402 payment works
- Your client sends the request. The API answers
402 Payment Requiredwith the price and where to pay. - The client pays from its own wallet: USDC on Base or Solana over x402, or over MPP on Tempo. No account, sign-up or API key.
- The client retries with the payment attached and gets the JSON answer in the same call. You are only charged for answers.
The AgentCash CLI in the example does all three steps for you and pays from your AgentCash wallet. Any x402 or MPP client works the same way.
Machine-readable: openapi.json · llms.txt