Validate your x402 payment config in seconds

See Example Configs
{ "amount": 0.025, "currency": "USDC", "network": "solana", "payTo": "5F5Yy9qJov8xK67vEWRoZHppWHEmH3WuG7mSfvLuqUTz" }
Minimal format. Works but consider upgrading to v2 for multi-chain support.
Method:

FAQ

What is x402?
x402 is a protocol for machine-to-machine payments over HTTP. When an endpoint requires payment, it returns HTTP status 402 Payment Required with a config describing how to pay. Agents read this config, send payment, then retry with proof.
What should my endpoint return?
For unpaid requests: HTTP status 402 with config in response body (JSON) or PAYMENT-REQUIRED header (base64). After payment verification: return 200 with your actual response.
Which chains and formats are supported?
Chains: solana, base, solana-devnet, base-sepolia

Formats: We accept 3 formats (Flat, v1 accepts, v2 payments). All work, but v2 is recommended for new endpoints.
Why is my config failing?
Common issues:
• Missing address or amount
• Wrong chain name (must be lowercase: solana not Solana)
• Address format doesn't match chain (base58 for Solana, 0x for Base)
• Endpoint not returning 402 status
How do I list on x402jobs?
Add marketplace metadata (name, description, outputSchema) to your v2 config, then submit at x402jobs.com. Complete listings get better placement.