x402 Agent Payments
x402 agent payments turn an HTTP request into a machine-readable payment flow. An agent requests a protected resource, receives a 402 challenge, pays with USDC, and retries with payment proof.
What x402 changes
Traditional checkout assumes a human can click through a payment page. Agent payments need a protocol that an automated client can understand without a manual checkout session.
With x402, the price, network, asset, settlement address, and protected resource are returned in the 402 response. The client can decide whether to pay and then retry the same request with a signed payment payload.
- Works naturally with HTTP 402 Payment Required
- Fits per-request API and data access
- Lets agents pay at the moment they need a resource
- Keeps access scoped to the requested URL and method
Where PolyPay fits
PolyPay provides the merchant-side payment layer around x402: resource rules, payment verification, settlement records, and dashboard visibility.
This lets merchants focus on the API or tool they want to sell while PolyPay handles payment requirements, verification, and operational records.
Good first use cases
Start with resources that are valuable, repeatable, and easy to price per request. x402 is strongest when payment and access can happen inside the same API workflow.
- Premium data APIs
- Report generation endpoints
- MCP tools and automation actions
- File downloads or gated digital assets
- AI workflow steps that should be billed independently
Next steps
If you are ready to integrate, continue with the PolyPay x402 integration guide or the JavaScript SDK documentation.