77trust / 100

Sanctioned Exposure

by Sanctioned Exposure in Security & trust

x402 APIPassing, checked 7 min ago

Not 'is this address sanctioned' (that's sanctions) but 'has it DEALT with one' — screens a wallet's USDC counterparties (both directions) against the OFAC SDN list. Taint by association: receiving from or routing through a wallet that transacts with sanctioned addresses carries sanctions risk. Returns the sanctioned counterparties found. Covers direct counterparties; pair with fund-trace for the multi-hop funding chain. Not financial advice.

GET
https://402.com.tr/api/x402/sanctioned-exposure
Price
$0.05
per call in USDC
Uptime
100%
last 30 days
Response time
474 ms
607 ms slowest 5%
Last check
Passed
7 min ago, next in 26 min

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://402.com.tr/api/x402/sanctioned-exposure

Each call costs $0.05 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.

GET https://402.com.tr/api/x402/sanctioned-exposure?days=90&wallet=0xFe21a68f21d556A3C4274a44c2Fb5410c50cDa1C

Parameters

ParameterTypeRequiredDescription
daysstringNoWindow days (default 90, max 365)
walletstringYesWallet to screen

Example response

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

{
  "checkedAt": "2026-10-11T17:12:00.557Z",
  "counterpartiesScreened": 4,
  "days": 90,
  "sanctionedCounterpartiesCount": 0,
  "verdict": "clear",
  "wallet": "0xFe21a68f21d556A3C4274a44c2Fb5410c50cDa1C"
}

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.05.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://402.com.tr/api/x402/sanctioned-exposure?days=90&wallet=0xFe21a68f21d556A3C4274a44c2Fb5410c50cDa1C'

# 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 - 'https://402.com.tr/api/x402/sanctioned-exposure?days=90&wallet=0xFe21a68f21d556A3C4274a44c2Fb5410c50cDa1C' \
  | 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.05 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.05" });
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.05 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2F402.com.tr%2Fapi%2Fx402%2Fsanctioned-exposure
const res = await pay("https://402.com.tr/api/x402/sanctioned-exposure?days=90&wallet=0xFe21a68f21d556A3C4274a44c2Fb5410c50cDa1C");
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.05 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.05"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://402.com.tr/api/x402/sanctioned-exposure?days=90&wallet=0xFe21a68f21d556A3C4274a44c2Fb5410c50cDa1C")
    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
7 min agoPassed402516 ms$0.05
5 h agoPassed402584 ms$0.05
10 h agoPassed402510 ms$0.05
14 h agoPassed402584 ms$0.05
19 h agoPassed402463 ms$0.05
Show 10 older checks
24 h agoPassed402386 ms$0.05
28 h agoPassed402469 ms$0.05
32 h agoPassed402607 ms$0.05
36 h agoPassed402525 ms$0.05
41 h agoPassed402600 ms$0.05
45 h agoPassed402801 ms$0.05
2 days agoPassed402578 ms$0.05
2 days agoPassed402521 ms$0.05
2 days agoPassed402538 ms$0.05
3 days agoPassed402453 ms$0.05