For x402 builders who need a direct answer to: is this paid route indexed, invocable, trusted, and ready for buyer agents to pay?
The preview checks whether a buyer agent should pay, block, or cap spend by verifying live unpaid 402 behavior, Payment-Required terms, payTo/amount/resource binding, and registry/schema evidence.
Run previewGET /preview/endpoint_risk
The paid JSON answer puts the buyer decision first: buyer_decision, exact payment contract, live-vs-indexed mismatch checks, spend cap/execution policy, replay/binding checklist, seller context, and then the directory-by-directory appendix for AgentCash/x402scan, 402index, Bazaar, x402gle, and Decixa. This copies the x402station pattern: free trial shape first, paid fresh evidence second.
POST /v1/x402/endpoint_risk — $0.05 USDC via x402 on Base
/.well-known/x402, expose /openapi.json, put x-payment-info on paid operations, and return HTTP 402 with Payment-Required plus Cache-Control: no-store.extensions.bazaar, useful input/output examples, and a routable resource URL so buyer agents can understand what they are paying for.x402, then verify listing/search readback instead of stopping at “submitted”.Use the preview for a free first pass. The paid diagnostic adds per-directory proof fields, replay/binding checks, active-validator checks, and the exact next fix for a seller route.
Check endpoint risksource=seller_diagnostics_matrix