AWS describes Anchor Browser integrated with Amazon Bedrock AgentCore payments for x402-protected pages and APIs. When a resource returns HTTP 402 Payment Required, AgentCore payments can authorize and complete a transaction within a configured budget and let the workflow continue. AWS also says payment attempts, approvals, denials, and settlements are visible through CloudWatch.
The mechanism is: The agent encounters a paid resource while AgentCore payments handles wallet connectivity, spending limits, and transaction processing outside the agent. Pay-per-request data and APIs create a concrete point where autonomous workflows otherwise stop for human intervention. The guide extends agent payment from API-oriented examples to browser-mediated access to protected web resources; it does not establish that such flows are broadly deployed or reliable across merchants.
Teams can evaluate paid-resource access as a bounded workflow capability, with spend controls and transaction visibility outside the agent. The implication is that payment can become a permissioned capability in an agent runtime rather than a credential or signing task delegated to the model. AWS's own technical guide documents an integration and intended behavior, not independent testing, adoption, or measured outcomes. Whether developers can configure and audit spending limits and transaction outcomes across real x402 merchants without exposing wallet credentials to the agent runtime.