AI agents need to pay for services
without a human in the loop.
RelayPlane handles x402 today. Coinbase contributed x402 to the Linux Foundation in 2025, making it an open standard for agentic payments. RelayPlane was among the first proxies to support it, so your agents can authenticate and pay for external services without stopping to ask a human for a credit card.
What is the x402 protocol?
x402 is an HTTP extension that lets servers request micropayments before serving a response. When an agent hits a paid API endpoint, the server responds with HTTP 402 (Payment Required) and a payment header. The agent pays via stablecoin, the server confirms, and the request proceeds — all in one round-trip, no OAuth flow, no billing portal.
Coinbase donated the protocol specification to the Linux Foundation to keep it open and vendor-neutral. The x402 Foundation now governs the spec, ensuring no single company controls how agents pay for services on the web.
RelayPlane is x402-compatible today
Install the proxy, point your agent at it, and x402 payment flows are handled transparently. Zero config for standard facilitator patterns. Your agent never sees the payment handshake.
Why this matters now
Agent-to-agent and agent-to-API payments are the next frontier. As the Linux Foundation standardizes x402, more services will add 402 responses. Agents that cannot handle them will stall. Agents running through RelayPlane will not.
Being x402-compatible from day one means your agent pipelines are ready for paid APIs, data marketplaces, and compute-on-demand services as they come online, without code changes on your end.