AWS moves agent payments to GA: the plumbing is done, the sign-off is not

Amazon Bedrock AgentCore payments is now generally available, following the preview AWS launched in May with Coinbase and Stripe to let agents autonomously pay for paid APIs, MCP servers and content ^[1][2]. AWS says the general release is aimed at production workloads with security, guardrails and observability ^[3], which shifts the remaining obstacle to autonomous per-call purchasing from engineering to whoever in your organisation is willing to fund a wallet an agent can spend from.

The funding model is stablecoin. AgentCore payments integrates with Coinbase and Stripe Privy wallets, which AWS describes as purpose-built for microtransactions often measured in cents ^[4]. End users top up an agent wallet with conventional methods such as credit cards or with USDC, and must explicitly grant delegation for the agent to spend on their behalf ^[11]. Developer credentials are held in AgentCore Identity Secrets Manager, the agent does not see the raw credentials, and short-lived tokens derived from them instruct the wallet provider to perform operations such as transaction signing ^[12]. For Coinbase there is now a Quick Create path in the console or CLI to provision credentials without leaving AgentCore ^[5]; Stripe Privy credentials still have to be fetched from the Privy dashboard and pasted in ^[13].

The control that finance teams will actually read is the payment session: a scoped context for a single agent interaction, with two configurable caps, a maximum spend amount in a specified currency and an expiry time ^[6]. Before signing, AgentCore checks the request against the session budget and rejects anything that would push the session past its cap, and AWS states the check is deterministic and runs at the infrastructure layer ^[7]. That is a direct answer to the failure modes AWS names in the same post: a non-deterministic agent misreading a response as authorization to spend, or repeating a payment because of an unexpected retry ^[14].

Two protocol changes matter more than they look. AgentCore payments is protocol-agnostic and launched at preview with x402; GA adds the Machine Payment Protocol, co-authored by Stripe and Tempo, with AWS saying MPP-compatible services work without an additional line of code ^[8]. Separately, x402 now supports an "upto" scheme, where the agent sets a spending ceiling instead of committing to a fixed price and the merchant charges for exactly what was consumed at the end of the call, rather than the fixed-price "exact" scheme ^[9]. For anyone reselling metered capacity such as LLM tokens or compute, that inverts the buyer's position: the ceiling is the control, and the invoice is settled after the work.

On the supply side, AgentCore exposes Coinbase's pay-per-use x402 endpoints as an MCP server through AgentCore Gateway, and AWS says the list has been narrowed to curated, high-quality endpoints selected on social proof, metadata richness, description quality and availability ^[10]. Those are editorial criteria, and worth understanding before an agent picks a vendor without a human in the loop.

Three things to watch. First, cap scope: the session caps described are per interaction ^[6], so an account-level or monthly ceiling is something you will have to establish yourself before procurement asks. Second, whether MPP and x402 both persist as live standards or one absorbs the other, given AgentCore's stated abstraction is what protects you from that ^[8]. Third, the delegation chain: because the end user grants spend authority ^[11], any consumer-facing deployment inherits a consent and disclosure problem that no infrastructure guardrail settles.