x402 Integration

This guide explains the intended payment contract for supported HyperAgent flows. It replaces earlier wording that framed x402 as an Avalanche and Thirdweb-only surface.

Current Contract

The current documentation should describe x402 as the intended payment contract in the active HyperAgent workflow path. It should not describe x402 as one optional payment mode among many equally supported billing contracts. The active truth set is narrower: x402 is the target payment wall, and older credits-first language exists only as legacy implementation residue.

Implementation Gap

The remaining gap is documentation and implementation alignment. Older pages still mention earlier payment-provider assumptions and older network-specific examples. Those references should be read as historical or transitional unless a page has already been brought forward to the current product truth set.