Agents can now buy tools from AWS Marketplace on their own, and the bill lands on the developer's normal AWS invoice. On November 19, 2026 the AWS Machine Learning Blog published Enable AI agents to pay for AWS Marketplace x402 products with Amazon Bedrock AgentCore payments. It adds AWS Billing as a payment option in AgentCore payments, so an agent can pay x402-enabled Marketplace sellers per request, in USD, without a stablecoin wallet or an API key.
The short version: the agent finds a seller, gets a signed price quote, asks AgentCore payments for permission, receives a payment token, retries the request, and gets the content. The charge is metered to the AWS account that owns the Payment Manager. A per-task budget stops the agent from spending more than the developer allowed.
TL;DR: what changed and what to check
| Question | Short answer (per the AWS post) |
|---|---|
| What is new? | AWS Billing as a payment option in AgentCore payments, plus an AWS Marketplace connector in AgentCore Gateway |
| What do agents buy? | x402-enabled software, APIs, data and content from AWS Marketplace sellers |
| Which currency? | USD, settled on the developer's AWS bill |
| Wallets or API keys? | Not needed |
| Which x402 scheme? | The exact scheme: a fixed price per request |
| How is spend capped? | A payment session with a spending limit, enforced by AgentCore payments; approved sellers via AgentCore policy |
| How is it audited? | AWS CloudTrail and AWS Cost Explorer; each product is a Marketplace line item |
| Named seller | Tavily, a live search provider |
| Not published | Seller count, fees, regional availability, and any pricing beyond the sample |
Why this matters: the missing billing path
Until now the x402 story for agents had two awkward parts for companies. First, the money moved in stablecoins from a wallet. Second, a finance team had to understand a new payment rail before it could approve any agent spending. AWS is removing both. In its own words, agents can "pay in USD on the agent developer's AWS bill, removing the need for stablecoin wallets or API keys."
The idea of x402 is simple. It reuses the HTTP 402 Payment Required status code. A server answers an unpaid request with a 402 and a price. The client pays and retries with proof. For an agent that calls many tools, this is a way to buy one search or one data lookup without signing up for an account or a monthly plan.
We have followed this thread for months. In October, AWS and Anchor Browser showed how browser agents pay x402 pages without holding keys. Earlier, Cloudflare launched a Monetization Gateway for x402 micropayments and Cloudflare Wallets for agent payments. Mastercard published its Agent Pay for machines design. Today's change is different in kind: it connects x402 to the invoice that enterprises already pay and already audit.
What AWS is launching
The AWS post names two pieces.
1. AWS Billing in AgentCore payments. When a Marketplace seller replies with 402 Payment Required, the response includes a signed quote. The agent forwards that response to AgentCore payments. AgentCore payments checks the session budget and returns a payment token. The agent retries the request with the token and gets a successful response. AWS bills the charge to the account where the Payment Manager is set up.
2. An AWS Marketplace connector in AgentCore Gateway. This is optional. It helps agents find products and their endpoints. According to AWS, the search tool only returns endpoints that accept x402.
The post also says the x402 catalog on AWS Marketplace "is expanding with a growing roster of trusted, verified sellers." It does not list how many sellers exist today. The one named seller is Tavily. Its CEO, Rotem Weiss, is quoted in the post saying the company worked with the AWS team on the design and describing the sellers as KYC verified.
AWS also reminds readers where this sits. AgentCore payments became generally available in August 2026, when agents could autonomously pay for paid APIs, MCP servers and web content over open protocols like x402 and MPP, with payment limits and full observability. The November change extends that to AWS Marketplace.
How the five-step flow works
The post describes a five-step flow. Here it is in plain language.
An agent spending meter that shows how a per-session budget limits agent purchases through AgentCore payments.
- Discover. The agent calls three read-only gateway tools in order: search listings, get a listing, and list its fulfillment options. The last call returns the seller's endpoint URL and the payment protocols it accepts.
- Get a quote. The agent calls the endpoint with no payment. The seller answers HTTP 402 and puts a signed quote in the PAYMENT-REQUIRED header. AWS Marketplace checks the signature against the seller's registered key, so a quote with an altered price is rejected.
- Pay. The agent passes the quote to the ProcessPayment API with the payment type AWS_BILLING_X402. If budget remains in the session, AgentCore payments issues a payment token. If not, the call fails and the developer is not charged.
- Redeem. The agent sends the request again with the token in the PAYMENT-SIGNATURE header. The seller returns the content. Payment tokens are valid for about five minutes, so the agent completes steps 2 to 4 in one pass.
- Settle. On the first purchase from a seller, AWS Marketplace creates an agreement with that seller for the account. After that it meters each charge to the AWS bill. Settlement runs asynchronously and appears on the bill monthly.
Two details are easy to miss. The signed quote means the agent cannot be tricked into paying a different price than the seller registered. And the short token lifetime means a leaked token is not a standing credential.
The guardrails, and who holds which key
Spending control is the part that decides whether a security team says yes. The AWS post gives these controls:
- A payment session with a spending limit for each task. The developer gives the agent only the session ID.
- Session cap enforcement by AgentCore payments, "so an agent is unable to overspend."
- Approved sellers set through AgentCore policy.
- Private Marketplace support: if the organization uses it, agents can only buy the products it allows.
- Audit through AWS CloudTrail and AWS Cost Explorer.
The setup script also splits permissions across three IAM roles. The session role can set budgets but cannot pay. The agent role can pay but cannot create sessions. So the agent has no way to raise its own budget. That is a useful pattern for any agent that touches money: the identity that spends should never be the identity that sets the limit. The gateway role is limited to three read-only AWS Marketplace actions.
A usage-based pricing meter that represents per-request x402 charges metered to an AWS bill.
To create an AWS Billing connector, the account needs the AWS Marketplace service-linked role named AWSServiceRoleForMarketplaceAgenticCommerce, which AWS Marketplace uses to bill the agent's purchases to the account.
The worked example: a research agent buys one search
AWS walks through a financial analyst asking an agent what was announced about agentic payments this week. The model was not trained on this week's news, so the agent needs a search tool. Through AgentCore Gateway it searches AWS Marketplace, reads the Tavily listing, and requests the listing's x402 endpoints. It calls the endpoint, receives the price, forwards the quote to AgentCore payments, and gets a token. Then it retries and gets search results. The final answer cites sources and states what it bought and what it cost.
In the logged test run against a one-cent seller, the agent compared two listings before buying. The tool-call trace shows search_marketplace, get_remaining_budget, two more searches, two get_listing calls, two get_seller_endpoints calls, then fetch_paid_api and a final budget check. The run made one payment, for a total of one cent. The sample defaults to a session budget of five cents and a per-request cap of two cents.
Note what this proves and what it does not. It shows the plumbing works end to end for a single cheap request. AWS did not publish latency numbers, failure rates, or results for large catalogs.
How to try it
AWS provides an open-source sample in the agentcore-samples repository. The post lists four steps:
- Run
setup_aws_billing.pywith your region. It creates a payment manager with an AWS Billing connector, the Marketplace service-linked role, and the three IAM roles. - Run
setup_gateway.py. It creates an AgentCore Gateway with the AWS Marketplace connector. To skip discovery, set the SELLER_URL environment variable so the agent pays only that URL. - Run the agent script with a question. It creates a session as the session role, then runs the agent as the agent role.
- Inspect the transaction. The sample prints the amount, the Marketplace product ID and the processPaymentId. The Tavily line item may take a moment to show on the bill.
Run cleanup.py afterwards and check that the resources are deleted, because AWS warns that leftover resources can incur charges. The sample uses a Strands agent. For more on running agents in the same stack, see our guide to AgentCore Registry and runtime tool discovery over MCP and A2A.
What the post does not say
Be careful with these gaps before you plan a rollout:
- Fees and margins. The post gives no Marketplace fee for x402 purchases and no price list beyond the one-cent sample.
- Catalog size. "Growing roster" is not a number. Only Tavily is named.
- Regions and limits. The post does not list supported regions, or maximum session budgets.
- Scheme coverage. Only the exact scheme (fixed price per request) is supported with AWS Billing at launch. Variable-price schemes are not covered.
- Refunds and disputes. The post does not explain what happens when a seller returns bad data after a charge.
- Monthly settlement. Because charges settle asynchronously and show monthly, a runaway agent is stopped by the session cap, not by a real-time bill alert. Set the cap low.
Prompt injection is still the open risk. A session budget limits the blast radius, but an agent that has been talked into buying the wrong tool will still spend inside its cap. AWS makes a related point in its guidance on agent autonomy; see our summary of AWS trust in depth for agent autonomy.
The bigger picture: agents meet the enterprise bill
Agent commerce is moving on two tracks. One track is open and wallet-based: stablecoins, public protocols, and little human review. The other is the enterprise track: invoices, agreements, private catalogs and audit trails. AWS Billing for x402 is a bridge between them. The protocol stays open, but the money flows through a procurement path that finance and security teams already know.
There is also pressure from the other side. Merchants are not always willing to let agents buy. We covered United Airlines blocking third-party AI agents from booking flights, and US banks moving to block agents from customer accounts. Marketplace x402 sits at the other end: sellers who opt in, are verified, and want agent traffic. Identity for those agents matters too; see how Okta cross-app access works with AgentCore Gateway.
What to do now
Builders: Run the sample in a sandbox account with a five-cent budget. Check that a failed payment really leaves no charge. Test what the agent does when the budget runs out.
Founders selling APIs or data: The Marketplace x402 catalog is a new way to reach agent buyers who cannot hold wallets. Read the AWS Marketplace seller documentation linked from the post before you list.
Finance and security leads: Ask for the approved-seller list, the session cap policy, and the CloudTrail query that shows agent purchases. Treat the first month of settlement as a test.
Marketers: Agents that pick tools by reading listings will favor clear, structured descriptions. The AWS example shows an agent comparing two listings before it bought.
Sources and further reading
- AWS Machine Learning Blog, Enable AI agents to pay for AWS Marketplace x402 products with Amazon Bedrock AgentCore payments (November 19, 2026)
- AWS Machine Learning Blog, Building agents that transact with Anchor Browser and AgentCore payments (October 2026)
- The x402 protocol: x402.org
Related reading
- AWS AgentCore Payments and Anchor Browser: how agents pay x402 sites without holding keys
- Cloudflare Monetization Gateway for x402 micropayments
- Cloudflare Wallets for AI agent payments
- Mastercard Agent Pay for machines
- AWS trust in depth for agent autonomy
- Okta cross-app access with AgentCore Gateway
