Amazon Bedrock has launched AgentCore payments as a generally available service, allowing agents to autonomously transact with security and observability. This service enables enterprises to power agentic payments with guardrails and visibility for production workloads. AgentCore payments integrates with Coinbase and Stripe Privy wallets, providing developers with tools to set up payment capabilities with minimal code. Developers can use Coinbase API keys directly within the AgentCore console or CLI, while Stripe Privy credentials must be obtained separately from the Privy dashboard. These wallets are designed for cost-effective microtransactions, often in cents, and end users can fund them through traditional payment methods or stablecoins like USDC, with delegation required for the agent to spend on their behalf. Source: awsml

AgentCore payments is built to be protocol-agnostic, abstracting away the complexity so developers can integrate once and work with merchants regardless of the protocol they use. At general availability, the service supports the Machine Payment Protocol (MPP), co-authored by Stripe and Tempo, enabling developers to pay for any MPP-compatible service without additional code. Additionally, the service now includes support for the 'upto' scheme within x402, allowing agents to set a spending ceiling instead of a fixed price. This supports dynamic pricing and true pay-per-inference, where merchants can charge for exactly what was consumed at the end of a call rather than requiring a fixed price for requests. Source: awsml

The service also enhances discoverability of pay-per-use endpoints by exposing Coinbase’s x402 endpoints as an MCP server via AgentCore Gateway. Developers can now discover and select relevant paid endpoints based on their use case, with the MCP server updated to a curated list of high-quality endpoints based on social proof, metadata richness, description quality, and availability. Payment limits are enforced within a payment session, a scoped context for a single agent interaction, with configurable caps on maximum spend and expiry time. These checks are deterministic and run at the infrastructure layer to prevent unauthorized transactions. Source: awsml