AWS Lets AI Agents Buy Marketplace Products on the Developer's AWS Bill
AWS says AgentCore agents can now buy Marketplace products per request in dollars via AWS Billing — no wallets, no API keys, with session budgets capping what agents can spend.
By Grace Kim
4 min read

What's News
- AWS announced on November 19, 2026 that AgentCore payments can settle x402 Marketplace purchases through AWS Billing in US dollars.
- Payment sessions cap agent spending; failed budget checks leave developers uncharged, and payment tokens expire after about five minutes.
- Separate session and agent roles prevent agents from raising their own budgets, while approved-seller lists and Private Marketplace add controls.
- AWS's documented test ran a $0.05 session budget, a $0.02 per-request cap and a completed $0.01 purchase via a Strands agent buying Tavily search.
- Purchases appear as AWS Marketplace line items and are recorded in AWS CloudTrail and AWS Cost Explorer.
AI agents running on Amazon Bedrock AgentCore can now buy software, APIs, data and content from x402-enabled AWS Marketplace sellers and put the charges straight onto the developer's AWS bill. AWS announced the capability on November 19, 2026. Purchases settle per request in US dollars, and the integration removes the need for stablecoin wallets or API keys.
An optional AWS Marketplace connector for AgentCore Gateway lets agents discover paid products and endpoints, while developers keep spending limits, seller permissions and audit records inside their existing AWS accounts. That last part is the point: agent spending now lands under the same billing and governance controls companies already run for everything else on AWS.
How does a purchase actually work?
The flow starts with an unpaid call. An agent hits a seller endpoint without payment, and the seller answers with HTTP 402 Payment Required plus 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 still has budget left, the service returns a payment token. The agent retries the request with that token in the PAYMENT-SIGNATURE header and gets the content.
At launch, AWS Billing supports the x402 exact scheme, where the seller quotes a fixed price per request. AWS Marketplace verifies the quote's signature against the seller's registered key and rejects any quote whose price has been altered. AWS says payment tokens stay valid for roughly five minutes, so quote, payment and redemption happen in a single pass.
The bookkeeping runs through familiar AWS plumbing:
- The first purchase from a seller creates an AWS Marketplace agreement for the developer's AWS account; later purchases track against it.
- Products show up as Marketplace line items, with settlement running asynchronously before charges appear on the monthly AWS bill.
- Every purchase lands in AWS CloudTrail and AWS Cost Explorer.
In plain words: an agent's buying becomes just another line on the invoice you already reconcile.
What stops an agent from overspending?
Quite a lot, by design. Setup requires a Payment Manager with an AWS Billing connector plus 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 can't cover a purchase, the payment call fails and the developer is not charged.
AgentCore policy adds more layers: additional spending limits and approved-seller lists, and organizations using Private Marketplace can restrict agents to whatever their private catalog allows. The open-source sample goes further on role separation — its session role can set budgets but cannot pay, while its agent role can pay but cannot create sessions. An agent physically can't raise its own budget.
The takeaway: a failed budget check costs the developer nothing, and autonomy stops exactly where the configured limits do.
How do agents find what to buy?
The optional 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 and accepted payment protocols. Developers who already know their supplier can skip discovery entirely by setting a seller URL directly — the agent then pays only that endpoint.
What did AWS's own test show?
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 numbers are small but precise. The sample defaults to a $0.05 session budget and a $0.02 cap per request. In AWS's documented test, the agent compared two listings before completing a single $0.01 payment — comparison shopping at cent scale, with a paper trail.
That's the real signal here. For AWS customers, the launch wires product discovery and per-request payment into established cloud billing and governance, so an agent's purchasing autonomy is bounded by the specific session budget, approved sellers, role permissions and Marketplace catalog access its developers configure.
Source: unite.ai
More from Grace Kim
Show full bio
Market editor covering people, launches and day-to-day practice in entrepreneurship, startups and venture funding at Business Bearings.
2,454 articles