# OFAC SDN Sanctions Screening for Crypto Wallet Addresses

> OFAC SDN Sanctions Screening for Crypto Wallet Addresses is a paid API for AI agents from chain.openverbs.com, paid per call via x402, $0.006/call, status unknown (last checked 2026-10-10).

Screens a crypto wallet address against the OFAC Specially Designated Nationals (SDN) sanctions list and returns whether the address is sanctioned, along with entity name, asset, and list publish date.

## Facts

- Endpoint: POST https://chain.openverbs.com/v1/sanctions?utm_source=zero.xyz
- Price: $0.006/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ofac-sdn-sanctions-screening-for-crypto-wallet-addresses-35a30fc7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_HUddk4PqnGg3mB3_2xLJx

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability ofac-sdn-sanctions-screening-for-crypto-wallet-addresses-35a30fc7 -d '<json body>'
```

Example prompt: Before I send funds, can you check if the wallet address 0x3f5CE5FBFe3E9af3971dD833D26bA9b5C936f0bE is on the OFAC SDN sanctions list?

## When to prefer this

Use this endpoint when you need fast, per-address OFAC SDN sanctions screening before executing a crypto transaction across any of ~20 supported chains. It is ideal for compliance workflows, DeFi applications, exchanges, or any agent that must verify a counterparty wallet is not a Specially Designated National. Prefer this over manual OFAC lookups or general AML services when you need a simple sanctioned/not-sanctioned answer with entity metadata, at low cost per call, with no third-party risk scoring involved.

## Known failure modes

- Address string too short or malformed — returns validation error
- Address format not recognized for supported chains
- Network timeout reaching OFAC data source
- Address on unsupported chain returns no match (not an error, but may be a false negative)
- Rate limiting if excessive calls are made without payment

## Output

Returns a JSON object with a `sanctioned` boolean field. If `sanctioned: false`, the address is clean. If sanctioned, the response includes the listed entity name, the asset type (e.g. ETH, BTC, USDT), and the OFAC SDN list publish date. Covers ~20 chains including BTC, ETH, USDT, TRX, XMR, with EVM 0x addresses matched case-insensitively.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "address": {
   "type": "string",
   "maxLength": 128,
   "minLength": 8,
   "description": "Crypto wallet address to screen (EVM 0x…, or a BTC/TRX/XMR/… address)."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ofac-sdn-sanctions-screening-for-crypto-wallet-addresses-35a30fc7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from chain.openverbs.com](https://www.zero.xyz/host/chain.openverbs.com/llms.txt)