pay-via-agent-wallet

Run circle services search with a keyword to find an endpoint, then circle services inspect to confirm price and schema, and finally circle services pay with the service URL, wallet address, chain, and data payload. The CLI signs the payment authorization and returns the API response as JSON.

x402 is a payment protocol where HTTP endpoints return a 402 response listing accepted payment options, and clients settle a small USDC fee per call. It removes the need for API keys, accounts, or prefunded billing since each request is paid individually.

Sellers publish accepted chains in their 402 response, and many accept only Polygon or Avalanche rather than BASE. When you see a chain rejection error, retry with the chain named in the CLI hint, which is authoritative.

Gateway payments use the GatewayWalletBatched scheme with sub-500ms settlement after a one-time deposit, while vanilla x402 pays directly per call at roughly 2 seconds each. When a seller lists both, the CLI picks Gateway first, so a Gateway deposit may be required.

HTTP 422 means the request payload schema is wrong, not a transient error. Check whether the CLI says payment was not charged before retrying with corrected field names, and never re-run the same payload blindly since post-authorization failures may have moved funds.

Verify the wallet is set up with circle wallet status and confirm a nonzero USDC balance. If login or terms errors appear, use the wallet setup flow first; if balance is zero, fund the wallet via fiat on-ramp, transfer, or Gateway deposit before paying.