Beauty & Personal Care · x402 · early usage

Sanctions screening for a crypto wallet before you pay it: checks the address, and an a…

by trust-agent.io · discovered, not yet claimed by its owner · updated 2026-10-11

30d calls5

30d payers5

MethodGET

Outputjson

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

Sanctions screening for a crypto wallet before you pay it: checks the address, and an agent's owner and payout wallet, against OFAC SDN-listed EVM addresses, then returns a 0-100 trust score, risk band and proceed / hold / block from on-chain history and sybil-filtered ERC-8004 reputation. Every flag and score component is itemized; insufficient_data instead of a guess. Base. Free: GET /v1/verify. Trial: /v1/trial.

Tags: sanctions · ofac · compliance · aml · wallet-screening · bazaar

Call contract

Method: GET
Input: query parameters
Output: json
Last paid call: 2026-10-11

Input example from Bazaar metadata

{
  "address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
  "chain": "base",
  "type": "contract"
}

Output example

{
  "address": "0x1111111111111111111111111111111111111111",
  "components": [
    {
      "contribution": 15.44,
      "id": "address_age",
      "observed": "147 days since first activity",
      "weight": 16
    }
  ],
  "confidence": 0.51,
  "example": true,
  "flags": [
    {
      "code": "BLOCKLISTED_ADDRESS",
      "severity": "critical",
      "title": "Address is on the \"ofac-sdn\" blocklist"
    }
  ],
  "overrides": [
    {
      "cap": 3,
      "from": 88,
      "id": "blocklisted",
      "reason": "Blocklisted by ofac-sdn on the queried address, agent owner, or payout wallet."
    }
  ],
  "recommendation": "block",
  "riskBand": "severe",
  "subjectType": "unregistered_address",
  "tier": "quick",
  "trustScore": 3
}

Use with an agent

Discover. Agents find this listing with GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP tool search_resources, or /discovery/resources.
Inspect. Fetch /resources/27655.json for the price and payment options.
Pay. Call GET https://trust-agent.io/v1/verify/quick. The provider answers 402 with its payment requirements. An x402 client signs one of the options below and retries with PAYMENT-SIGNATURE.
Execute. The provider returns 200 with 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.002 / request
Protocol: x402 v2
Auth: No account or API key. Pay per request.
Networks: Base
Demand: 5 calls · 5 unique payers in 30d (public x402 Bazaar data)

x402 payment requirements

Scheme	Network	Asset	Amount	Pay to	Timeout
exact	Base eip155:8453	USDC	$0.002	0x6121654D3Fd4C8B42a90d30472E4D40927C3e6BB	60s

accepts[] (raw JSON)

[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "payTo": "0x6121654D3Fd4C8B42a90d30472E4D40927C3e6BB",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "2000",
    "amountUsd": 0.002,
    "maxTimeoutSeconds": 60
  }
]

Schemas

Output schema (JSON Schema)

{
  "properties": {
    "example": {
      "properties": {
        "components": {
          "description": "per-rule scoring breakdown; the score is reconstructable from these plus overrides"
        },
        "confidence": {
          "description": "0-1, how much evidence backs the score"
        },
        "flags": {
          "description": "array of {code, severity, title, detail}"
        },
        "overrides": {
          "description": "hard caps applied after weighting, each with from/cap/reason"
        },
        "recommendation": {
          "description": "proceed | proceed_with_caution | hold | block | insufficient_data. insufficient_data means no judgment was possible — treat it as unknown, not as risky."
        },
        "riskBand": {
          "description": "minimal | low | moderate | elevated | severe | unknown"
        },
        "trustScore": {
          "description": "0-100, higher is safer; null when no rule could be evaluated"
        }
      },
      "type": "object"
    },
    "type": {
      "type": "string"
    }
  },
  "required": [
    "type"
  ],
  "type": "object"
}

Example shape — generated from the schema, not a captured live response

{
  "example": {
    "components": null,
    "confidence": null,
    "flags": null,
    "overrides": null,
    "recommendation": null,
    "riskBand": null,
    "trustScore": null
  },
  "type": "string"
}

Examples

curl

curl -X GET 'https://trust-agent.io/v1/verify/quick'
# -> 402 Payment Required; read PAYMENT-REQUIRED
# retry the identical request with PAYMENT-SIGNATURE

JavaScript

const res = await fetch("https://trust-agent.io/v1/verify/quick", {
  "method": "GET"
});
if (res.status === 402) {
  const { accepts } = await res.json();
  // pay one of accepts[] via an x402 client, then retry with the payment header
}

Python

import httpx
res = httpx.request("GET", "https://trust-agent.io/v1/verify/quick")
if res.status_code == 402:
    accepts = res.json()["accepts"]
    # pay one of accepts[] via an x402 client, then retry with the payment header

Details

Provider: trust-agent.io
Endpoint: https://trust-agent.io/v1/verify/quick
Machine-readable: /resources/27655.json