Is this x402 endpoint safe to pay? Reads the endpoint's own payment challenge under BOTH p
Is this x402 endpoint safe to pay? Reads the endpoint's own payment challenge under BOTH protocol versions — v1 body and v2 PAYMENT-REQUIRED header, so a live v2-only service is not reported as dead — extracts the payout wallet it advertises, and screens that wallet: OFAC sanctions, sybil-filtered ERC-8004 reputation, on-chain behaviour. Flags an endpoint that names different recipients under the two versions. Scores the wallet, not the service behind it, and says so.
5000 (raw units)
price
1
calls / 30d
1
unique payers
2026-09-03
updated
Provider
trust-agent.io · discovered, not yet claimed by its owner
Payment (x402 accepts[])
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0x6121654D3Fd4C8B42a90d30472E4D40927C3e6BB",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "5000",
"maxTimeoutSeconds": 60
}
]Output schema
{
"bazaar": {
"info": {
"input": {
"method": "GET",
"queryParams": {
"chain": "base",
"url": "https://trust-agent.io/v1/verify/quick"
},
"type": "http"
},
"output": {
"example": {
"additionalPayoutWallets": "present only when the offers disagree about the recipient",
"components": "per-rule scoring breakdown",
"flags": "array of {code, severity, title, detail}",
"offers": "every advertised offer: payTo, network, asset, amount, version",
"payoutWallet": "the address scored",
"paywalled": "whether the endpoint answered 402 with a parseable payment offer",
"recommendation": "proceed | proceed_with_caution | hold | block | insufficient_data",
"trustScore": "0-100 for the payout wallet; null when no rule could be evaluated",
"x402Versions": "which protocol generations answered — [1], [2] or [1,2]"
},
"type": "json"
}
},
"schema": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"input": {
"additionalProperties": false,
"properties": {
"method": {
"enum": [
"GET"
],
"type": "string"
},
"queryParams": {
"properties": {
"chain": {
"description": "OPTIONAL. Only \"base\" is served; any other value is refused rather than answered from the wrong chain.",
"type": "string"
},
"url": {
"description": "REQUIRED. The x402 endpoint to screen, e.g. https://example.com/v1/thing.",
"type": "string"
}
},
"required": [
"url"
],
"type": "object"
},
"type": {
"const": "http",
"type": "string"
}
},
"required": [
"type",
"method"
],
"type": "object"
},
"output": {
"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"
}
},
"required": [
"input"
],
"type": "object"
}
}
}Use it
curl
curl "https://trust-agent.io/v1/endpoint/screen" # -> 402 Payment Required, accepts[] lists how to pay # retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paid
JavaScript
const res = await fetch("https://trust-agent.io/v1/endpoint/screen");
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.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 headerMachine-readable
Everything on this page is also available as clean JSON at /resources/5181.json, and this resource appears in /discovery/resources and /discovery/search.