AI Agents Need Spending Limits Alongside Crypto Payment Rails
Amazon Bedrock AgentCore payments pair x402 with per-session spending limits, while Base settlement totals cannot confirm whether off-chain services were delivered.

As software agents begin paying for digital services through crypto protocols, companies need wallet limits and records to govern spending because settlement data alone cannot confirm service delivery.
With x402, a server can answer an API request with HTTP 402 and payment terms. The client sends a signed payment, which the server or a facilitator verifies and settles before returning the requested resource. The protocol can work across different networks and payment setups, including fixed payments, spending caps and batch settlement.
The payment flow does not itself manage a wallet’s spending authority or verify an off-chain service. A separate x402 implementation on the XRP Ledger enables software agents to use XRP and Ripple USD (RLUSD) for payment-gated services.
Amazon Bedrock AgentCore payments became generally available Aug. 18, 2026. The service connects to Coinbase and Stripe Privy wallets and supports x402 and the Machine Payments Protocol. Each payment session can set a maximum spend in a specified currency and an expiration time. Requests above the limit are denied, and credentials are stored in AWS Secrets Manager.
From Sept. 17, 2025, through June 23, 2026, a 280-day period, Base recorded 136,708,672 x402 settlements worth $44,121,383.81. Within that activity, 21.20% were classified as fictitious, while 63.78% were internal settlements among linked wallet clusters.
A total of $187,861.35 was linked to a named service in the catalog examined. The upper bound for value not proven to be manufactured was $20,258,746.09; services missing from the catalog could affect the estimates. These figures describe settlement activity and wallet relationships, but do not establish what portion of the transactions paid for useful services.
For companies, enabling payments and setting an agent’s spending authority are separate parts of the system. Session limits can constrain how much an agent may spend, while credential management controls access to payment capability. A blockchain record documents settlement; it cannot by itself confirm that an off-chain service was delivered.