Protocols · News from · Published · Stefan Hamann

AWS Marketplace x402 payments: How AI agents buy a single request

Amazon Bedrock AgentCore lets AI agents pay per request for selected AWS Marketplace services. Charges go on the existing AWS bill in US dollars, within limits the buyer sets.

CheckoutTrustMerchant operations

A magnifying glass over a search result, a single payment receipt and an invoice with one line highlighted in orange.
Illustration: Agentic Commerce

One search on the next cloud bill

A research agent needs to find out what happened in agent payments this week. It can stop and wait for someone to set up an account with a search provider, or it can buy the one query it needs to finish the job. The part that interests me is where that little purchase shows up. It can now land on the company’s regular cloud bill.

On 19 November, AWS Marketplace added this route for selected products. Agents can use Amazon Bedrock AgentCore payments to pay per request for eligible software, APIs, data and content. AWS charges the existing AWS account in US dollars. According to AWS, this route needs no separate crypto wallet. AgentCore has supported machine payments since August. The change here is that eligible Marketplace requests go through AWS Billing.

How do x402 payments work in AWS Marketplace?

In the example AWS published, a research agent finds a paid web search service. Its first request gets an HTTP 402 response with a signed quote. AgentCore checks the remaining budget for the session and issues a payment token when the request passes those checks. The agent sends the request again with the token, and the service returns the results. AWS meters the charge to the business account.

The buyer needs to enable the AWS Billing connector in AgentCore payments, and the seller needs an eligible Marketplace listing. At launch this billing route supports the x402 exact scheme, which lets the seller quote a fixed price for the request up front. AWS says the feature is available in regions that support AgentCore payments. Its region table lists Frankfurt and Ireland among them. What an agent can buy also depends on the organisation’s configuration.

Who sets the agent’s spending limit?

The cost of a single search can look immaterial. Run the same workflow a hundred times and the decision to buy one more query starts to matter. AWS describes a cap for each payment session, policies for approved sellers and continued application of Private Marketplace rules. It says transactions are visible in CloudTrail and Cost Explorer. Those records help a team trace the spend. To find out whether it was worthwhile, the team still needs to look at what the agent produced.

In my guide to shopping agent spending limits, the instruction records what the buyer authorised, while the payment system enforces the limits it can actually check. I’d apply the same reasoning to a research job: decide which data the agent may buy, what the whole job can cost and what it should report when the budget runs out. A paid search can be perfectly valid and still add very little to the answer.

What this means for sellers of digital services

In Chapter 8 of my book, From the offer to the service that follows, I describe our x402 research preview. A Shopware plugin links an order to a payment request software can read. The local and Base Sepolia test flows illustrate why the request, transfer and order need a shared reference. AWS tackles another part of that problem by putting the charge for an individual service request onto an existing business bill.

Compare that with Lightspark Agent Accounts, which companies can embed to give agents a way to hold, send and receive money. With the AWS route, a specific use of a service becomes a charge on the buyer’s existing account. If I sold a digital service, I’d test whether the buyer can tell which request they paid for, what came back, and what happens to the bill if the connection drops and the agent tries again. That’s where I’d look to see how the purchase holds up in everyday use.

Source and further reading

Read the original announcement ↗

Read the related Agentic Commerce guide ↗

The Agentic Commerce handbook ↗

Save and share