AWS Lets AI Agents Buy x402 Products in AWS Marketplace and Pay on the AWS Bill
On 19 November 2026 AWS said AI agents can now buy x402-enabled software, APIs, data and content in AWS Marketplace and pay for them on the company’s AWS bill. AWS added AWS Billing as a payment option in Amazon Bedrock AgentCore payments: an agent pays x402-enabled Marketplace sellers per request, in US dollars, within a spending limit set for each task, “removing the need for stablecoin wallets or API keys,” in AWS’s words.
What AWS added to AgentCore payments on 19 November
AWS announced the change in a technical post on its Machine Learning blog and in an AWS Marketplace post listing launches for re:Invent 2026. The main points, as AWS describes them:
- Payment on the AWS bill. “An agent can now pay x402-enabled AWS Marketplace sellers per request, in USD, settling on their AWS bill.” Charges land on the AWS account where the developer set up the AgentCore payments Payment Manager, and settle on the monthly bill.
- Fixed prices per request. At launch, AWS Billing supports the x402 “exact” scheme, in which the seller quotes a fixed price for each request.
- A budget for each task. The developer creates a payment session with a spending limit for each task and gives the agent the session ID. AWS says “the payment session cap is enforced by AgentCore payments, so an agent is unable to overspend.” In AWS’s setup, the role that creates sessions and sets budgets cannot pay, and the agent’s role can pay but cannot create sessions, so the agent cannot raise its own budget.
- Seller limits. Developers can set spending limits and approved sellers through AgentCore policy, and “if your organization uses Private Marketplace, agents can only buy the products it allows.”
- An audit trail. “Transactions are auditable in AWS CloudTrail and AWS Cost Explorer,” and each product appears as an AWS Marketplace line item.
- Agreements created on first purchase. “An agent’s first purchase from a seller creates an agreement for the AWS account with that seller,” and AWS Marketplace tracks later purchases against it.
On the selling side, AWS says sellers “must register with AWS Marketplace and integrate with the AWS Marketplace x402 SDK” before agents can buy their products, and go through the same registration and review process as other Marketplace sellers. The technical post names one seller, Tavily, a search provider, and says the x402 catalog is growing.
Why AWS Marketplace billing matters for x402 and B2B buying
x402 was created by Coinbase as an HTTP-native payment protocol for machine-to-machine payments, built around stablecoins, and AgentCore payments has supported it since its preview, paying from a Coinbase or Stripe Privy wallet (see the August general availability report). The 19 November change keeps the x402 request-and-pay pattern but settles in dollars on the AWS bill an enterprise already receives, with agent purchases going “through the same billing, budgets, and controls your finance team already uses,” in AWS’s words. For a company that wants an agent to buy API calls or data, AWS says that removes “the need for stablecoin wallets or API keys.”
It also puts agent purchases inside procurement controls that AWS customers already use: Private Marketplace product lists, CloudTrail and Cost Explorer. In the same set of launches AWS described buying policies that route AWS Marketplace purchases to approvers by amount or product type, including through Coupa and SAP Ariba; that announcement does not say whether it applies to x402 purchases.
For sellers of APIs, data and software, the arrangement is per-request pricing, with the agreement with the buyer’s AWS account created by the agent’s first purchase.
How to read the AWS launch
- Budgets in advance, not approval each time. AWS’s technical post does not describe a person approving each x402 purchase. The agent spends within a session budget and seller policy set in advance. That differs from consumer agent checkouts such as ChatGPT Wallet, where the user approves each purchase. AWS Marketplace’s separate conversational agent mode does require “human confirmation” before a purchase is complete, according to the Marketplace post, but that is a different flow from the x402 one.
- Status and regions. AgentCore payments itself has been generally available since August 2026. Neither 19 November post labels the AWS Billing option as generally available or preview, and neither states regional availability (the technical post’s setup example uses us-east-1).
- Catalog size. AWS names only Tavily as an x402 seller, so how many products agents can buy this way at launch is not stated.
See also how AI agents pay, x402 vs MPP, AI shopping agent payment authorization, and the agentic commerce timeline.
Frequently asked questions
What did AWS launch on 19 November 2026?
AWS added AWS Billing as a payment option in Amazon Bedrock AgentCore payments. An AI agent can now pay x402-enabled AWS Marketplace sellers per request, in US dollars, with the charges settled on the AWS bill of the account where the developer set up AgentCore payments, instead of from a stablecoin wallet or with API keys.
How does a company stop the agent overspending?
For each task, the developer creates a payment session with a spending limit and gives the agent the session ID. AWS says the session cap is enforced by AgentCore payments, so the agent cannot overspend. In AWS's setup, the role that creates sessions and sets budgets cannot pay, and the agent's role can pay but cannot create sessions. Developers can also set approved sellers through AgentCore policy, and if the organization uses Private Marketplace, agents can only buy the products it allows.
Does a person approve each x402 purchase?
AWS's technical post on the x402 flow does not describe a per-purchase approval step: control comes from the budget and policies set in advance. AWS Marketplace's separate agent mode, a conversational buying experience, does require human confirmation before a purchase is complete, according to AWS's Marketplace blog. The two are different flows.
What does a seller have to do?
According to AWS, sellers must register with AWS Marketplace and integrate with the AWS Marketplace x402 SDK before agents can buy their products, and they go through the same registration and review process as other AWS Marketplace sellers. An agent's first purchase from a seller creates an agreement between the buyer's AWS account and that seller, and AWS Marketplace tracks later purchases against it. Tavily is the only seller AWS names in its technical post.