Key Points
- AWS now allows AI agents to purchase eligible software, APIs and data automatically inside AWS Marketplace.
- Spending is capped by account owners and billed in US dollars on the existing AWS invoice.
- The shift moves agents from recommending purchases to executing them without a human clicking buy.
The latest:
AI agents can now pay for software, APIs, data and digital content on their own inside AWS Marketplace, Amazon Web Services announced on Thursday, 19 November 2026. Purchases run only within spending limits and vendor lists that account owners set in advance, and only for products configured to support the x402 payments protocol — not the full marketplace catalogue.
Details:
- The mechanism: The feature runs on the x402 payments protocol combined with Amazon Bedrock AgentCore payments, according to AWS. Charges are denominated in US dollars and appear on the customer’s existing AWS invoice, removing the need for a separate payment account with each vendor or a cryptocurrency wallet.
- How a purchase executes: A developer must enable the AWS Marketplace payments connector in AgentCore payments, and can link the agent to the marketplace connector inside AgentCore Gateway to find eligible products. When the agent requests a paid resource, the server returns a signed price quote in an HTTP 402 response.
- The payment step: AWS says the payments service then checks the session’s spending limits and issues a payment token, which the agent uses to resend its request and receive the content or service. Session limits are enforced technically, so an agent cannot exceed its allocated amount.
- Pricing model: At launch, billing supports the x402 pattern of a fixed price per request, per the company’s technical documentation. AWS cites a research agent buying a single paid query, or a coding agent calling a paid security tool mid-task, without opening an account with each supplier.
- Enterprise controls: Organisations can set spending ceilings, approved-vendor lists and payment rules before an agent starts buying. Private Marketplace policies still apply to what the agent can reach, and transactions can be traced in AWS CloudTrail with costs reviewed through AWS Cost Explorer.
- Seller requirements: Vendors must register with AWS Marketplace and integrate the platform’s x402 development kit to accept these payments. AWS adds the charges to the buyer’s invoice and settles the seller’s proceeds through the marketplace’s standard payments system.
- New data category: AWS separately made Data as a Service generally available, covering third-party datasets and licensed content. Sellers can deliver through APIs, Model Context Protocol servers, a web portal, live streams or Amazon S3 buckets, and set their own pricing and licensing terms, including contracts and pay-per-use.
- The limits: The new category does not mean every product in it can be bought automatically via x402; that depends on seller support and each product’s architecture.
- Not the chat assistant: AWS also expanded Agent mode inside the marketplace, a conversational interface that helps buyers identify products, review security documentation and contract terms, then buy and deploy. Unlike automated agent purchases, it requires user confirmation plus approval of the deployment plan and expected cost.
- Availability: x402 payments are offered in AWS regions that support AgentCore payments, while conversational Agent mode is available wherever AWS Marketplace operates.
Between the lines:
The design keeps the financial decision with the human while handing execution to the machine: ceilings, vendor lists and session limits are all set before an agent transacts, and CloudTrail logging preserves an audit trail. The split from Agent mode, which still demands user confirmation, suggests AWS is treating unattended spending as the higher-risk path.
What’s next
Watch how many sellers integrate the x402 kit, whether billing moves beyond fixed per-request pricing, and how fast Data as a Service listings become agent-purchasable rather than subscription-only.