AWS lets AI agents buy x402 products through Marketplace billing

AWS has added AWS Billing to Amazon Bedrock AgentCore payments, allowing AI agents to discover and purchase x402 enabled software, APIs, data and content through AWS Marketplace. The charges are settled in USD on the agent developer’s AWS bill, without requiring stablecoin wallets or API keys.
- AWS Billing is now a payment option in AgentCore payments.
- Agents can buy x402 enabled AWS Marketplace products in USD.
- Developers can set spending limits and approved sellers.
- Purchases are recorded in AWS CloudTrail and AWS Cost Explorer.
- AgentCore Gateway can help agents discover Marketplace products and endpoints.
AWS Marketplace purchases with spending controls
Amazon Bedrock AgentCore payments became generally available in August 2026 for autonomous payments to paid APIs, MCP servers and web content over protocols including x402 and MPP. The latest update extends that capability to AWS Marketplace.
Developers can create a Payment Manager with an AWS Billing connector, then create a payment session for each task with a spending limit. AgentCore payments checks the session budget before issuing a payment token, while the payment session cap prevents an agent from spending beyond the configured amount.
Developers can also approve sellers through AgentCore policy. Organizations using Private Marketplace restrict agents to the products their organization allows. Transactions can be audited in AWS CloudTrail and AWS Cost Explorer, and each purchased product appears as an AWS Marketplace line item.
How the x402 payment flow works
When an AWS Marketplace seller receives a request without payment, it returns HTTP 402 with a signed quote in the PAYMENT-REQUIRED header. AWS Marketplace checks the quote against the seller’s registered key, rejecting a quote with an altered price.
The agent passes the quote to the AgentCore payments ProcessPayment API using the AWS_BILLING_X402 payment type. If enough budget remains, the service returns a payment token. The agent sends the request again with the token in the PAYMENT-SIGNATURE header and receives the content.
At launch, AWS Billing supports the x402 exact scheme, in which the seller quotes a fixed price for each request. Payment tokens are valid for about five minutes. On an account’s first purchase from a seller, AWS Marketplace creates an agreement, then meters later charges to the AWS bill. Settlement runs asynchronously and appears on the bill monthly.
Discovery through AgentCore Gateway
A new AWS Marketplace connector in AgentCore Gateway can help agents find products and their endpoints. In AWS’s sample workflow, a research agent searches Marketplace listings, reads a listing from Tavily and requests the seller’s x402 endpoints.
The agent calls the endpoint, receives pricing details, sends the x402 payload to AgentCore payments and retries the request after receiving a token. The resulting answer includes sources and states what the agent bought and what it cost.
AWS says the x402 catalog is expanding with trusted, verified sellers. Tavily, a live search provider for agentic commerce, is among them. Tavily founder and CEO Rotem Weiss said, “Agentic commerce isn’t just about giving agents the ability to pay. It’s about giving enterprises the confidence to let them.”
What developers need to use it
To create an AWS Billing connector, an AWS account must have the AWS Marketplace service-linked role AWSServiceRoleForMarketplaceAgenticCommerce. AWS provides an open source sample in the agentcore-samples repository that demonstrates configuring AgentCore payments, connecting Tavily, running an agent and inspecting the transaction.
In the sample test run, the session budget is $0.05 and the per-request cap is $0.02. Against a $0.01 seller, the agent made one purchase totaling $0.01 after comparing two listings. The sample also separates permissions so the session role can set budgets but cannot pay, while the agent role can pay but cannot create sessions. This limits the agent’s ability to raise its own budget.


