x402 extends HTTP payment semantics for machine clients. In agent ecosystems, it enables usage-metered interactions where clients can discover payable services, understand payment context, and complete requests without manual billing workflows.
From a discovery perspective, x402 is valuable because pricing and payment capability must be surfaced before invocation. Registry-backed discovery reduces integration friction by making payment-compatible listings queryable through standard search routes.
This hub keeps x402-specific guidance centralized and linkable so teams can align on protocol behavior, integration patterns, and discovery expectations.