AWS lets AI agents charge pay-per-request Marketplace purchases to cloud bills
The AgentCore update covers fixed-price requests from x402-enabled sellers, with session budgets and an optional connector for finding services.
Loading page…
The AgentCore update covers fixed-price requests from x402-enabled sellers, with session budgets and an optional connector for finding services.
Listen to this story
The integration gives developers a way to route eligible, per-request agent purchases through AWS Billing, with Marketplace charges appearing on the account’s monthly bill. It extends AgentCore’s existing payment capabilities rather than giving agents spending power for the first time. Session budgets, seller policies, signed price quotes and separate roles for setting budgets and making payments provide controls; developers should note that the flow currently supports x402’s fixed-price “exact” scheme and payment tokens expire after about five minutes.
AWS added the Marketplace billing route to Amazon Bedrock AgentCore payments on November 19, 2026.
A seller’s first sale creates an agreement with the AWS account; later purchases are metered asynchronously as Marketplace line items.
The sample uses a $0.05 session budget and a $0.02 per-request cap; its illustrated agent made one $0.01 purchase.
AI agents can now buy individual requests from eligible AWS Marketplace sellers and put the charges on a developer’s AWS bill. AWS added the payment route to Amazon Bedrock AgentCore payments on November 19, 2026, letting agents purchase tools, data and content in dollars without setting up stablecoin wallets or API keys.
AgentCore payments became generally available in August 2026, already allowing agents to pay for APIs, tool servers and web content over open payment protocols. The new integration extends that system to AWS Marketplace purchases through AWS Billing. It changes the payment route rather than introducing agents’ ability to spend for the first time.
Alongside billing, AWS launched an optional Marketplace connector in AgentCore Gateway, its tool-access service. The connector lets agents search listings, inspect a product and find its service endpoints—the addresses they call to use it. Its search tool returns only endpoints that accept x402, the payment protocol supported by this integration.
At launch, AWS Billing supports the x402 “exact” scheme: a seller quotes a fixed price for each request. To enable purchases, a developer creates a Payment Manager with an AWS Billing connector and sets up the required AWS Marketplace service-linked role. Each task can then receive a payment session with its own spending limit.
AWS Marketplace checks the quote’s signature against the seller’s registered key, rejecting a quote whose price has been altered. Payment tokens last about five minutes, so the agent must complete the quote, payment and redemption sequence within that window. If the budget check fails, AWS says the developer is not charged.
The first purchase from a seller creates an agreement between that seller and the AWS account. Marketplace tracks later purchases against the agreement and meters the charges asynchronously. Each product appears as a Marketplace line item on the account’s monthly AWS bill, rather than requiring a separate payment arrangement for each request.
Developers can restrict approved sellers through AgentCore policy as well as set session spending limits. Organizations using Private Marketplace add another boundary: agents can buy only products that organization allows. AWS’s accompanying sample also separates payment authority from the authority to create the session that holds the budget.
AWS says purchases are auditable in CloudTrail and Cost Explorer. The sample also prints the payment amount, Marketplace product identifier and payment-processing identifier after a run, giving developers a transaction record to inspect alongside the eventual billing entry.
AWS illustrates the integration with a research agent asked about the week’s agentic-payment announcements. It discovers search provider Tavily through Marketplace, buys a search request and answers with sources, stating what it purchased and the cost. The accompanying GitHub sample lets developers evaluate the workflow in their own AWS accounts.
The sample defaults to a $0.05 session budget and a $0.02 per-request cap. In AWS’s illustrated run, the agent compared two listings and made one $0.01 purchase. Those are demonstration settings and results, not a universal Marketplace price.
Discovery is optional, not a prerequisite for payment. Developers who already know which service an agent should use can skip the Gateway connector and configure the seller’s endpoint directly; in that sample configuration, the agent pays only that specified address.
Loading discussion...
Join the conversation
Explain when flexibility is worth giving up a predictable supplier.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.