ToolVet
77trust / 100

Sanctions

by chain.openverbs.com in Security & trust

x402 APIPassing, checked 2 h ago

Screen a crypto wallet address against the OFAC SDN sanctions list (US Treasury Specially Designated Nationals) before transacting. Multi-chain across ~20 assets (BTC, ETH, USDT, TRX, XMR and more); EVM 0x addresses match case-insensitively. Returns whether the address is sanctioned plus the listed entity, asset and list publish date. Clean address returns `sanctioned:false`. Public-domain OFAC data.

POST https://chain.openverbs.com/v1/sanctions

Last 30 days

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

Uptime
100%
Response time
603 ms typical, 643 ms slowest 5%
Last check
2 h ago
Next check
any minute now

How to call it

POST https://chain.openverbs.com/v1/sanctions

Each call costs $0.006 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

POST https://chain.openverbs.com/v1/sanctions
content-type: application/json

{
  "address": "examplex"
}

Parameters

ParameterTypeRequiredDescription
addressstringYesCrypto wallet address to screen (EVM 0x…, or a BTC/TRX/XMR/… address).

Example response

The provider's example. We can't check it without paying.

{
  "address": "0x0000000000000000000000000000000000000001",
  "asOf": "10/02/2026",
  "asset": null,
  "entity": null,
  "listSize": 1050,
  "sanctioned": false,
  "source": "OFAC SDN",
  "stale": false,
  "uid": null
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.006.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://chain.openverbs.com/v1/sanctions' \
  -H 'content-type: application/json' \
  --data-raw '{"address":"examplex"}'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://chain.openverbs.com/v1/sanctions' \
  -H 'content-type: application/json' \
  --data-raw '{"address":"examplex"}' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.006 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.006" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.006 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fchain.openverbs.com%2Fv1%2Fsanctions&method=POST
const res = await pay("https://chain.openverbs.com/v1/sanctions", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "address": "examplex"
  }),
});
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.006 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.006"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://chain.openverbs.com/v1/sanctions",
        json={
            "address": "examplex",
        },
    )
    print(res.status_code, res.text)

Security scan

  • No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
2 h agoPassed402552 ms$0.006
6 h agoPassed402613 ms$0.006
10 h agoPassed402605 ms$0.006
14 h agoPassed402605 ms$0.006
18 h agoPassed402628 ms$0.006
22 h agoPassed402562 ms$0.006
26 h agoPassed402621 ms$0.006
30 h agoPassed402545 ms$0.006
33 h agoPassed402554 ms$0.006
37 h agoPassed402613 ms$0.006
40 h agoPassed402539 ms$0.006
44 h agoPassed402573 ms$0.006
2 days agoPassed402554 ms$0.006
2 days agoPassed402631 ms$0.006
2 days agoPassed402671 ms$0.006