Sanctions screening - name

Screen a person or company name against the OFAC SDN list. Returns exact and substring matches with the SDN entry id and type, so every hit can be checked against the published list itself. Matching is exact and substring only - never a fuzzy similarity score, because a confident near-miss on a common surname is a liability rather than an answer. A miss is 'not on the lists checked, as of this date', never a clearance.

TRY IN PLAYGROUND →

Input

Example output

{
  "query": "Gazprom",
  "verdict": "match",
  "exactCount": 0,
  "containsCount": 2,
  "matches": [
    {
      "id": "12345",
      "name": "GAZPROMBANK JOINT STOCK COMPANY",
      "type": "-0-",
      "matchType": "contains"
    }
  ],
  "entriesOnList": 19388,
  "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..."
}

Try it - see the 402 challenge (free)

curl -i "https://agent402.tools/api/sanctions/name?name=Gazprom"

The response is HTTP 402 Payment Required with exact payment requirements. Any x402 v2 client pays automatically and retries:

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";
import { metaTitle, metaDescription } from "./seo-meta.js";

const client = new x402Client();
registerExactEvmScheme(client, { signer: privateKeyToAccount(KEY) });
const payFetch = wrapFetchWithPayment(fetch, client);

const res = await payFetch("https://agent402.tools/api/sanctions/name?name=Gazprom");

Related tools