Why is my x402 endpoint broken? Diagnose and debug an x402 payment endpoint (or MCP server) when payments fail: checks the 402 challenge, accepts[] (network, payTo, amount, asset), resource URL, Solana settlement readiness, which wallets and agents can pay, Bazaar/OpenAPI discovery and the browser paywall. Returns every check with a fix hint. Read-only: never pays. Bulk: 1000 credits for $0.80 via /api/v1/credits.

How do I fix my broken x402 endpoint? Diagnoses it, then returns per problem the concrete change as code for your stack (Express, Next.js, Hono or raw HTTP), filled in with your own payTo, amount, network and route. Bulk: 1000 credits for $0.80 via /api/v1/credits.

Is this x402 endpoint safe to pay? Call it before your AI agent pays an endpoint it has not used before. Returns a go / caution / no_go verdict, the recommended payment option (network and amount) and the reasons (payment would fail, over your budget, price above advertised, not HTTPS, unknown token). Never pays the endpoint. Cached 10 min. Bulk: 1000 credits for $0.80 via /api/v1/credits.

Are these x402 endpoints safe to pay? Up to 10 endpoints in one call (?url=a&url=b): per endpoint go / caution / no_go, the recommended payment option and why, plus totals. For marketplaces and agents that weigh several services. Never pays the endpoints.

Should my agent pay this expensive x402 endpoint? Call it before a costly or repeated payment. Returns the go / caution / no_go verdict plus the full diagnosis, the endpoint's check history per day over 30 days, how reliable the seller's other endpoints are and whether the endpoint moved domains. Never pays the endpoint. Bulk: 1000 credits for $0.80 via /api/v1/credits.