Agentic payments14 Jul 20263 min read
x402 just grew up
The x402 Foundation gives internet-native payments a neutral home. After helping build around x402 at Polygon, this feels like an important step from promising protocol to shared infrastructure.
When I first started working on x402 at Polygon, I still had to explain why an unused HTTP status code mattered. The idea was simple: a service should be able to return 402 Payment Required, an agent should be able to pay, and the request should continue without a checkout page.
What changed
The Linux Foundation launched the x402 Foundation with organizations across payments, cloud infrastructure, and digital assets. Polygon is a founding member.
The important part is not just the list of companies. x402 now has a neutral place where the protocol can be developed in the open. If agents are going to pay across different services and payment rails, developers need one interoperable standard rather than a separate integration for every provider.
The part I worked on at Polygon
I worked on making x402 useful from a developer's point of view. That included the Polygon Agent CLI, Agentic Services, AgentConnect, the x402-rs facilitator, integration documentation, demos, and direct support for teams adding pay-per-use services.
These pieces solve different parts of the same journey. The CLI gives an agent a wallet and payment capability. Agentic Services helps it find something worth paying for. The facilitator verifies and settles the payment. My DevRel work connected those products to developers through clearer onboarding, technical content, integrations, and feedback from teams actually building with them.
I also co-authored PIP-82, which proposed up to $1M in base-fee rebates for eligible agentic-commerce transactions. Polygon has since processed more than 24 million x402 transactions across the network.
What comes next
A foundation does not create adoption by itself. Developers still need good libraries, predictable payment flows, useful services, and documentation that gets them from an idea to a working integration quickly.
That is where I think the next phase will be won. The protocol now has a shared home. The work ahead is making it boringly easy for any developer—or agent—to use.
Building an API, dataset, or MCP tool agents should pay for?
I helped build Polygon's Agentic Services and the surrounding developer experience. If you want to talk x402, my inbox is open.