Beauty & Personal Care · x402 · early usage

Is this x402 endpoint safe to pay

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

30d calls4

30d payers2

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

Is this x402 endpoint safe to pay? Reads its payment challenge (v1 body and v2 PAYMENT-REQUIRED header), lists every offer, then screens the payout wallet: OFAC SDN check, 0-100 trust score, risk band and proceed / hold / block with itemized flags. Flags offers that name different recipients. It scores the wallet that gets paid, not the service behind the URL. Free: GET /v1/endpoint. Trial: /v1/trial.

Tags: x402 · payment-screening · sanctions · payee · pre-payment · bazaar

Call contract

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

Input example from Bazaar metadata

{
  "chain": "base",
  "url": "https://trust-agent.io/v1/verify/quick"
}

Output example

{
  "confidence": 0.34,
  "example": true,
  "flags": [
    {
      "code": "ONE_WAY_FUND_FLOW",
      "severity": "high",
      "title": "Address receives funds but rarely sends any"
    },
    {
      "code": "NEW_ADDRESS",
      "severity": "medium",
      "title": "Address is less than a month old"
    }
  ],
  "offers": [
    {
      "amount": "10000",
      "network": "eip155:8453",
      "payTo": "0xadaf6488600a810c8d3adc3a33a1b0217f7ce510",
      "version": 2
    }
  ],
  "payoutWallet": "0xADAF6488600a810C8D3aDc3A33A1B0217F7ce510",
  "paywalled": true,
  "recommendation": "hold",
  "riskBand": "elevated",
  "subject": "The score describes the PAYOUT WALLET this endpoint advertises, not the service behind it.",
  "trustScore": 43,
  "url": "https://example.com/v1/forecast",
  "x402Versions": [
    1,
    2
  ]
}

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/27658.json for the price and payment options.
Pay. Call GET https://trust-agent.io/v1/endpoint/screen. 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.005 / request
Protocol: x402 v2
Auth: No account or API key. Pay per request.
Networks: Base
Demand: 4 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.005	0x6121654D3Fd4C8B42a90d30472E4D40927C3e6BB	60s

accepts[] (raw JSON)

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

Schemas

Output schema (JSON Schema)

{
  "properties": {
    "example": {
      "properties": {
        "additionalPayoutWallets": {
          "description": "present only when the offers disagree about the recipient"
        },
        "components": {
          "description": "per-rule scoring breakdown"
        },
        "flags": {
          "description": "array of {code, severity, title, detail}"
        },
        "offers": {
          "description": "every advertised offer: payTo, network, asset, amount, version"
        },
        "payoutWallet": {
          "description": "the address scored"
        },
        "paywalled": {
          "description": "whether the endpoint answered 402 with a parseable payment offer"
        },
        "recommendation": {
          "description": "proceed | proceed_with_caution | hold | block | insufficient_data"
        },
        "trustScore": {
          "description": "0-100 for the payout wallet; null when no rule could be evaluated"
        },
        "x402Versions": {
          "description": "which protocol generations answered — [1], [2] or [1,2]"
        }
      },
      "type": "object"
    },
    "type": {
      "type": "string"
    }
  },
  "required": [
    "type"
  ],
  "type": "object"
}

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

{
  "example": {
    "additionalPayoutWallets": null,
    "components": null,
    "flags": null,
    "offers": null,
    "payoutWallet": null,
    "paywalled": null,
    "recommendation": null,
    "trustScore": null,
    "x402Versions": null
  },
  "type": "string"
}

Examples

curl

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

JavaScript

const res = await fetch("https://trust-agent.io/v1/endpoint/screen", {
  "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/endpoint/screen")
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/endpoint/screen
Machine-readable: /resources/27658.json