Products & Tools

AWS Lets AI Agents Buy From Marketplace via AWS Billing

AWS now lets Bedrock AgentCore agents buy software, APIs and data from x402-enabled Marketplace sellers through AWS Billing, with session budgets and role separation capping what an agent can spend.

AWS Lets AgentCore Agents Buy Marketplace Products Through AWS Billing
AWS Lets AgentCore Agents Buy Marketplace Products Through AWS Billingmastersenaiper / pixabay
By Elena Vasquez5 min read

Why it matters

  • On November 19, 2026, AWS announced AgentCore payments can settle purchases from x402-enabled AWS Marketplace sellers through AWS Billing.
  • Agents buy per request in US dollars with no stablecoin wallets or API keys; charges land on the developer's monthly AWS bill.
  • Payment tokens stay valid for about five minutes, and a sample session defaults to a $0.05 budget with a $0.02 cap per request.
  • Separate session and agent roles stop an agent from raising its own budget.
  • AWS's documented test showed an agent completing one $0.01 payment after comparing two listings.

AI agents can now buy software, APIs, data and content from AWS Marketplace sellers and put the tab on their developer's AWS bill. On November 19, 2026, Amazon Web Services announced that Amazon Bedrock AgentCore payments can settle purchases from x402-enabled AWS Marketplace sellers through AWS Billing. Agents pay per request in US dollars, and the integration removes the need for stablecoin wallets or API keys.

The announcement matters because it wires autonomous purchasing directly into the billing and governance machinery that cloud customers already run. Developers keep spending limits, seller permissions and audit records inside their existing AWS accounts. An agent's purchasing autonomy is bounded by the session budget, approved sellers, role permissions and Marketplace catalog access its developers configure.

How does an agent actually pay?

The payment flow starts with a refusal. An agent calls a seller endpoint without payment. The seller responds with HTTP 402 Payment Required and places a signed quote in the PAYMENT-REQUIRED header. The agent forwards that quote to AgentCore payments through the ProcessPayment API, using the AWS_BILLING_X402 payment type.

If the session has enough remaining budget, the service returns a payment token. The agent retries the request with that token in the PAYMENT-SIGNATURE header and receives the content. Payment tokens remain valid for about five minutes, so the quote, payment and redemption steps occur in a single pass.

At launch, AWS Billing supports the x402 exact scheme, under which the seller quotes a fixed price for each request. AWS Marketplace verifies the quote's signature against the seller's registered key, rejecting any quote whose price has been altered.

The accounting then flows into standard AWS surfaces. The first purchase from a seller creates an AWS Marketplace agreement for the developer's AWS account, and later purchases are tracked against it. Products appear as Marketplace line items, with settlement running asynchronously before charges appear on the monthly AWS bill. Purchases are also recorded in AWS CloudTrail and AWS Cost Explorer.

What stops an agent from overspending?

Budgets, roles and catalog rules do the guarding. Setup requires a Payment Manager with an AWS Billing connector and an AWS Marketplace service-linked role. For each task, developers create a payment session with a spending limit and hand the agent its session ID. If the remaining budget is insufficient, the payment call fails and the developer is not charged.

AgentCore policy adds more layers on top:

  • Additional spending limits beyond the session cap
  • Approved-seller lists
  • Private Marketplace restrictions, which limit agents to products the private catalog allows

The open-source sample separates permissions by design. Its session role can set budgets but cannot pay. Its agent role can pay but cannot create sessions. That split prevents the agent from increasing its own budget — a small detail that addresses one of the more obvious failure modes of autonomous purchasing.

How do agents find what to buy?

An optional AWS Marketplace connector for AgentCore Gateway lets agents discover paid products and endpoints. The gateway connector exposes three read-only tools: search listings, get a listing and list fulfillment options. Listing search returns only endpoints that accept x402, and the fulfillment call supplies the seller's endpoint URL along with the payment protocols it accepts.

Developers can skip discovery entirely by setting a seller URL directly. In that case the agent pays only that endpoint.

What did AWS's test purchase look like?

AWS's walkthrough uses a Strands research agent answering a financial analyst's question about agentic-payment announcements that fall outside the model's training data. The agent finds Tavily's live-search listing, requests its x402 endpoints, obtains a quote and pays for one request. Its answer includes sources and identifies what it purchased and how much it cost.

The sample's defaults are deliberately small: a $0.05 session budget and a $0.02 cap per request. In AWS's documented test, the agent compared two listings before completing one $0.01 payment.

Why does this matter beyond AWS?

The launch connects two things that have lived in separate worlds: machine-native product discovery and enterprise-grade billing controls. x402-style per-request payments have mostly been discussed in crypto-adjacent circles, where agents needed stablecoin wallets to transact. AWS has stripped that requirement away and routed everything through AWS Billing in dollars.

That choice carries weight in the market. Enterprises that would never hand an agent a crypto wallet already trust AWS invoicing, CloudTrail audit logs and Cost Explorer reporting. By anchoring agent purchases in those systems, AWS positions autonomous commerce as an extension of existing cloud procurement rather than a new financial rail.

The governance model is the other half of the story. Every purchase lands in an audit trail developers already monitor. Every dollar an agent spends traces back to a session someone configured, a seller someone approved and a budget someone set. The agent never holds the keys to its own allowance.

For sellers, the calculus is straightforward: x402-enabled Marketplace listings become machine-purchasable by default, opening a channel where the buyer is software. For developers, the question shifts from whether agents can buy things to how tightly they can scope what agents buy — and AWS's answer is a stack of budgets, roles and catalog rules that all fail closed.

The next signal to watch is whether the "exact" pricing scheme — fixed prices per request — widens into negotiated or variable pricing, and whether other cloud providers follow AWS's move to bring agent payments under conventional billing rather than crypto rails.

By Elena Vasquez

Source: unite.ai

Share this article:

More from Elena Vasquez

Elena Vasquez

Show full bio

Market editor covering technology and product news in artificial intelligence and machine learning at AI In Context.

795 articles

Related articles

  1. OpenAI Opens ChatGPT Enterprise Sales Through AWS Marketplace
  2. Shopify opens checkout to browser-based AI agents
  3. AWS AgentCore’s Strands upgrade can change omitted agent settings
  4. AWS AgentCore Runtime Gets 8-vCPU Sessions and Filesystem Mounts
  5. Walmart Opens the Door to AI Shopping Agents, Amazon Slams It Shut

« Previous articleNext article »