Screen Address for Sanctions
Check whether a blockchain address is on any sanctions list tracked by Chainalysis (OFAC SDN, EU, UN, etc.). Returns a boolean sanctioned flag, unique categories, and the full identifications list with source URLs. Chain-agnostic (EVM, BTC, Solana). Ideal for: compliance workflows, pre-transaction screening, counterparty risk checks, AML monitoring, audit trails.
Catalog action Integrations chainalysis-sanctions
Check whether a blockchain address is on any sanctions list tracked by Chainalysis (OFAC SDN, EU, UN, etc.). Returns a boolean sanctioned flag, unique categories, and the full identifications list with source URLs. Chain-agnostic (EVM, BTC, Solana). Ideal for: compliance workflows, pre-transaction screening, counterparty risk checks, AML monitoring, audit trails.
At a Glance
| Field | Value |
|---|---|
| Action ID | chainalysis-sanctions-check-address |
| Category | Integrations |
| Connector | chainalysis-sanctions |
| Requires gas | No |
| Funds movement | None declared |
| Tags | chainalysis, sanctions, compliance, aml, kyt, screening, risk, ofac, read |
Payload Schema
| Field | Type | Required | Description |
|---|---|---|---|
address | string | Yes | The blockchain address to screen against sanctions lists. Chain-agnostic (EVM, BTC, Solana, etc.). |
apiKey | string | No | API key for the Chainalysis Sanctions Screening API. Normally injected automatically by the 'chainalysis-sanctions' connector. If no connector is attached and this field is empty, the action falls back to the CHAINALYSIS_SANCTIONS_API_KEY environment variable. |
Result Schema
| Field | Type | Required | Description |
|---|---|---|---|
address | string | Yes | The address that was checked |
isSanctioned | boolean | Yes | True when the address appears on at least one sanctions list |
identificationsCount | number | Yes | Number of sanctions listings returned for the address |
categories | array | Yes | Unique categories across all matches (e.g. ['sanctions']) |
identifications | array | Yes | Full list of sanctions listings — empty array when the address is clean |
Examples
json{ "type": "chainalysis-sanctions-check-address", "payload": { "address": "0x0000000000000000000000000000000000000000" }, "children": [], "connector": { "type": "chainalysis-sanctions", "id": "conn_chainalysis_sanctions" }}
bashcurl -X POST "https://api.b3os.org/v1/actions/chainalysis-sanctions-check-address/test" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "inputs": { "address": "0x0000000000000000000000000000000000000000" }}'
Payload fields can use workflow expressions such as {{$trigger.body.amount}}, {{$nodes.fetch.result.price}}, and {{$props.asset}} when the value should come from a trigger, prior node, or reusable workflow prop.