Not 'is this address sanctioned' (that's sanctions) but 'has it DEALT with one' — scree…
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 sanction…
by 402.com.tr · discovered, not yet claimed by its owner · updated 2026-10-13
Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.
What it does
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.
Tags: sanctions · ofac · compliance · aml · counterparty · bazaar · builder-code
Call contract
- Method
- GET
- Input
- query parameters
- Output
- json
- Last paid call
- 2026-10-13
{
"days": "90",
"wallet": "0xFe21a68f21d556A3C4274a44c2Fb5410c50cDa1C"
}{
"checkedAt": "2026-10-11T17:12:00.557Z",
"counterpartiesScreened": 4,
"days": 90,
"sanctionedCounterpartiesCount": 0,
"verdict": "clear",
"wallet": "0xFe21a68f21d556A3C4274a44c2Fb5410c50cDa1C"
}Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/31902.jsonfor the price and payment options. - Pay. Call
GET https://402.com.tr/api/x402/sanctioned-exposure. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with the data. Agent Bazaar is not in the request path and never sees your payment.
For humans
You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.
Pricing & payment
- Price
- $0.05 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Demand
- 5 calls · 2 unique payers in 30d (public x402 Bazaar data)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.05 | 0x973a31858f4d2125f48c880542da11a2796f12d6 | 300s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0x973a31858f4d2125f48c880542da11a2796f12d6",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "50000",
"amountUsd": 0.05,
"maxTimeoutSeconds": 300
}
]Schemas
Output schema (JSON Schema)
{
"properties": {
"example": {
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}Example shape — generated from the schema, not a captured live response
{
"example": {},
"type": "string"
}Examples
curl "https://402.com.tr/api/x402/sanctioned-exposure"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paidconst res = await fetch("https://402.com.tr/api/x402/sanctioned-exposure");
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}import httpx
res = httpx.get("https://402.com.tr/api/x402/sanctioned-exposure")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- 402.com.tr
- Endpoint
- https://402.com.tr/api/x402/sanctioned-exposure
- Machine-readable
/resources/31902.json