Free Intensive Nov 21–22Free 2-day hands-on Vibecoding Intensive on Nov 21–22 at 16:00 MSK (Sat–Sun) · Live Cohort 3 starts Nov 23Join Free →Cohort 3 (Nov 23)
ReleaseAPI / Product · ActionableAWS Machine Learning Blog→ original

AWS teaches AI agents to buy APIs in Marketplace and pay through a regular AWS bill

AWS now lets AI agents buy paid APIs and data in Marketplace on their own. The money is charged to a regular AWS account in dollars, with no crypto wallets or API keys. The seller sends a digitally signed price, AgentCore checks the remaining session budget and issues a payment token. In the demo, an agent paid $0.01 for a single search query to Tavily with a session limit of $0.05. This means agents can be given a budget through familiar billing, without separate payment systems.

AI-processed from AWS Machine Learning Blog; edited by Hamidun News
AWS teaches AI agents to buy APIs in Marketplace and pay through a regular AWS bill
Source: AWS Machine Learning Blog. Collage: Hamidun News.
Listen to article
Article Fact Sheet & Key Figures
ParameterDetails
Primary sourceAWS Machine Learning Blog ↗
Editor-in-Chief
Key metric #1The token lives for about five minutes, so the whole purchase cycle runs in a single pass
Key metric #2The session role sets the budget but does not pay; the agent role pays but does not change the budget
The exact schemea fixed price per request; in the example, the limit is $0.05 per session

Imagine your agent realizes that it needs fresh news to answer a question, and its training data has none. Until now, the path looked like this: a developer picks a search service in advance, creates an account, gets an API key, puts it in a config and keeps an eye on the bills. Or they wrestle with a stablecoin wallet so the agent can pay via the x402 protocol. Amazon is trying to remove both problems: the agent finds a paid tool in AWS Marketplace on its own and pays for it through the same AWS bill you already use.

What exactly was launched

In summer 2026, Amazon Bedrock AgentCore gained payments (AgentCore payments): agents could pay for APIs, MCP servers and web content over the open x402 and MPP protocols, with limits and observability. Now AWS Billing has been added as a payment method. The agent pays sellers from the AWS Marketplace catalog for each request, in dollars, and the charge lands on the bill of the account where Payment Manager is configured. Crypto wallets and separate keys for each service are not needed.

For finding sellers, there is an optional AWS Marketplace connector in AgentCore Gateway. It shows the agent products and their endpoints. Only products that accept x402 appear in the results. If a company has Private Marketplace enabled, the agent can buy only what is allowed there.

How a purchase works

The flow resembles getting an invoice at the checkout counter before you pay.

  1. The agent searches for products through the gateway, opens a product page and requests the endpoints it can buy from.
  2. It calls the endpoint without paying. The seller responds with HTTP 402 (payment required) and sends a digitally signed quote. AWS Marketplace checks the signature against the seller's registered key, so a quote with a forged price will be rejected.
  3. The agent sends the quote to the ProcessPayment API with the type AWS_BILLING_X402. If the session budget has funds left, it receives a payment token. If not, the call fails and no money is charged.
  4. The agent repeats the request with the token in the PAYMENT-SIGNATURE header and gets the data. The token is valid for about five minutes, so steps 2 through 4 need to fit into a single pass.
  5. Settlement is asynchronous. On the first purchase from a seller, AWS creates an agreement; later charges are recorded against it and appear on the bill once a month as separate line items.

In the demo, a research agent answers an analyst's question about the week's news. It compared two product pages, chose the Tavily search service, paid $0.01 for a single query and returned an answer with sources, stating what it bought and how much it cost.

Spending controls and limitations

The main question about paying agents is what stops them from overspending. AWS answers with separation of roles. The example creates three separate IAM roles: the session role can set a budget but does not pay, while the agent role pays but cannot create sessions, so it cannot raise its own budget. By default, the example sets the session budget at $0.05 and the cap per request at $0.02. The gateway role is limited to three read-only actions. You can define a list of approved sellers through AgentCore policy, and transactions are visible in AWS CloudTrail and AWS Cost Explorer.

The limitations are also worth considering:

  • At launch, only the x402 exact scheme is supported, where the seller names a fixed price per request. There is no dynamic pricing yet.
  • Money is not charged instantly: settlement is asynchronous, and purchases show up on the bill with a delay.
  • The connector requires the service role AWSServiceRoleForMarketplaceAgenticCommerce.
  • The x402 catalog in Marketplace is still growing. Tavily is the only seller mentioned; the others have not been named yet.

What to do in practice

If you are building agents for a company whose purchasing runs through AWS, this is the shortest path to give them access to paid data without separate payment infrastructure and without approving a new vendor. You can start with the open example in the agentcore-samples repository. It has three scripts: payment setup, gateway connection and launching an agent on Strands. If you don't need the gateway yet, you can put a seller's address in the SELLER_URL variable, and the agent will pay only that seller.

For product teams, the takeaway is simpler: the agent itself can pay for calls, and budgets and roles will limit it, not a human confirming every purchase. Check how session limits and the seller list fit your procurement policy before giving an agent a real budget.

Story

Key Questions Answered

What exactly was launched?

In summer 2026, Amazon Bedrock AgentCore gained payments (AgentCore payments): agents could pay for APIs, MCP servers and web content over the open x402 and MPP protocols, with limits and observability. Now AWS Billing has been added as a payment method. The agent pays sellers from the AWS Marketplace catalog for each request, in dollars, and the charge lands on the bill of the account where Payment Manager is configured. Crypto wallets and separate keys for each service are not needed.

How a purchase works?

The flow resembles getting an invoice at the checkout counter before you pay. The agent searches for products through the gateway, opens a product page and requests the endpoints it can buy from. It calls the endpoint without paying. The seller responds with HTTP 402 (payment required) and sends a digitally signed quote. AWS Marketplace checks the signature against the seller's registered key, so a quote with a forged price will be rejected.

What are the key details on Spending controls and limitations?

The main question about paying agents is what stops them from overspending. AWS answers with separation of roles. The example creates three separate IAM roles: the session role can set a budget but does not pay, while the agent role pays but cannot create sessions, so it cannot raise its own budget. By default, the example sets the session budget at $0.05 and the cap per request at $0.02. The gateway role is limited to three read-only actions.

ZK
Zhemal Khamidun — CPO at Alpina Digital, product manager of AlpinaGPT. Building AI products since 2019. Hamidun News is a pet project that grew into a production aggregator with 6,000+ readers.
✦ Private AI Builders Community · Vibe Club

Ship AI Faster with Founders, Engineers & Weekly Architecture Reviews

Inside Vibe Club (hamidun.com/club) — weekly live masterminds with Zhemal Khamidun, Tech Radar, full LMS access, and 370+ production Claude Code skills.

Join Vibe Club →Explore Hamidun Academy
What do you think?
Loading comments…