Sanctions screening - crypto address

Is this blockchain address on the OFAC SDN list? Send GET /api/sanctions/wallet with the required field address and pay $0.002 per call over x402 or MPP (there is no free tier). It returns a JSON object with address, verdict, entity, sdnId, asset and 5 more.

Screens any address against every Digital Currency Address OFAC publishes (Bitcoin, Ethereum, Tron, USDT, USDC, Monero, Litecoin and more). A match names the sanctioned entity and its SDN id. A miss is reported as 'not on the lists checked, as of this date' and is never a clearance - the answer carries that caveat in the payload. Deterministic: a cached copy of the published list, no model in the path.

Category: Address screening · Tags: sanctions ofac compliance screening wallet aml

TRY IN PLAYGROUND →

Parameters

Example request

curl -i "https://agent402.tools/api/sanctions/wallet?address=0x098B716B8Aaf21512996dC57EB0615e2383E2f96"

Without payment this returns HTTP 402 Payment Required with the exact price for sanctions-wallet; any x402 v2 or MPP client pays it and retries.

Example response

{
  "address": "0x098b716b8aaf21512996dc57eb0615e2383e2f96",
  "verdict": "match",
  "entity": "LAZARUS GROUP",
  "sdnId": "12345",
  "asset": "ETH",
  "listedAddress": "0x098b716b8aaf21512996dc57eb0615e2383e2f96",
  "addressesOnList": 492,
  "listsChecked": [
    {
      "list": "OFAC SDN",
      "authority": "US Treasury OFAC"
    }
  ],
  "listsFetchedAt": "2026-09-12T00:00:00.000Z",
  "confirmBeforeActing": "a match is a string match against a published list, not a confirmed identification..."
}

From an MCP client

catalog.call {
  "slug": "sanctions-wallet",
  "params": {
    "address": "0x098B716B8Aaf21512996dC57EB0615e2383E2f96"
  }
}

The hosted connector at https://agent402.tools/mcp needs a payment for sanctions-wallet; the stdio package pays it from a wallet or from AGENT402_CREDITS_KEY. Local install: npx -y agent402-mcp.

Errors and behavior

• address is required. An input the tool rejects returns an HTTP 4xx whose body carries error, tool, expected, required and example, so the caller can correct it.
• A paid call that ends in any status of 400 or above is not charged over x402, MPP or a prepaid credits key: settlement is cancelled when the tool fails. The exception is a Tempo push credential, a transfer the buyer sent before the call: it settles before the tool runs, so if the tool then fails the payment is recorded as a refund owed to the paying wallet.
• Wallet-only: this tool reaches the network or stored state, so it has no proof-of-work tier. A prepaid card-credits key issued earlier (Authorization: Bearer a402_...) also pays it.
• A POST with a JSON body to /api/sanctions/wallet is served as this GET, with the body as the input.
• An Idempotency-Key header makes a retried paid call replay the first 200 instead of charging again (an answer larger than 1 MB is not replayed).

Paid call (JavaScript agent)

import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

const client = new x402Client();
client.setSpendControls?.(false); // keep your own spending ceiling in code
registerExactEvmScheme(client, { signer: privateKeyToAccount(KEY) });
const payFetch = wrapFetchWithPayment(fetch, client);

const res = await payFetch("https://agent402.tools/api/sanctions/wallet?address=0x098B716B8Aaf21512996dC57EB0615e2383E2f96");

Related tools