x402 API

This section explains the payment-facing API boundary for HyperAgent. Read it as the current payment contract for supported flows, not as a promise of uniform payment behavior across every environment or chain.

Overview

The x402 API belongs to the workflow system, not to a separate standalone payment product. It should be understood as the payment contract that gates supported workflow operations where payment is required. This is why the current docs now frame x402 as part of the HyperAgent operating path rather than as a broad pay-per-use layer across every chain named elsewhere in older materials.

Current Contract

The active product truth set is narrower than older API descriptions. x402 is the intended payment contract for supported flows. Legacy language about credits or alternate billing paths should be read as implementation residue unless the current page explicitly restates them as supported behavior.

API Boundary

The payment API should be interpreted through three boundaries. First, it is part of the current workflow system. Second, it follows the narrower implementation scope documented in the current product path. Third, the surrounding billing, reconciliation, and policy controls are still part of an evolving operational layer rather than a fully generalized universal payment stack.