Back to Browse
TrustAgent x402 Endpoint Safety Screener
x402
TrustAgent x402 Endpoint Safety Screener is a paid API for AI agents from trust-agent.io, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-14).
Screens an x402 HTTP endpoint for payment safety by reading its payment challenge across both protocol versions, extracting the payout wallet, and scoring it for OFAC sanctions, sybil-filtered ERC-8004 reputation, and on-chain behavior.
Price / call$0.005
Success—
StatusUnknown
How this service works
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.
Output
Returns a JSON object containing: a 0-100 trust score for the payout wallet, a recommendation (proceed, proceed_with_caution, hold, block, or insufficient_data), an array of flags with severity and detail, all advertised payment offers with payTo/network/asset/amount/version, which x402 protocol versions responded, per-rule scoring components, and any additional payout wallets if v1 and v2 offers disagree about the recipient.
Example use cases
Pre-payment safety check for new API
“I found a new x402-enabled API at https://api.newservice.io/v1/query — before we pay for any calls, can you screen it for wallet sanctions and give me a trust score and recommendation?”
Detecting wallet-switching fraud
“I'm worried this x402 endpoint might be routing payments to different wallets depending on the protocol version — can you check https://suspicious-api.com/v1/stream and flag if the recipients differ between v1 and v2?”
Autonomous agent payment gating
“My agent is about to make a micropayment to https://databroker.xyz/v1/prices — screen that endpoint first on Base and block the payment if the wallet scores below 50 or hits any OFAC flags.”
Technical details
Endpoint
GEThttps://trust-agent.io/v1/endpoint/screenWhen to prefer
Use this endpoint when an AI agent is about to execute an x402 micropayment and needs a safety gate that covers both protocol versions (v1 body and v2 header) simultaneously. It is uniquely capable of detecting recipient wallet mismatches between protocol versions — a red flag for fraud — which generic address screeners cannot do. Prefer it over standalone OFAC checkers when the entity being paid is an API endpoint rather than a known counterparty address, since it autonomously fetches and parses the payment challenge itself.
Side effects
- Target URL does not return a 402 response — paywalled: false, insufficient_data recommendation
- Unsupported chain specified — request refused rather than answered from wrong chain data
- OFAC or ERC-8004 data unavailable — trustScore returns null, recommendation: insufficient_data
- Target endpoint unreachable or times out — error flag returned
- Wallet has no on-chain history — limited scoring components, low confidence score
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"