AWS Marketplace 加入 AWS Billing,讓 AI Agent 按請求付款並記入 AWS 帳單
AWS Marketplace Lets an Agent Pay Per Request and Settle on Your AWS Bill
AWS 於 2026 年 11 月 19 日將 AWS Billing 加入 Amazon Bedrock AgentCore payments,讓 AI Agent 可在 AWS Marketplace 按請求購買支援 x402 的軟件、API、數據及內容,費用記入開發者的 AWS 帳單。
TL;DR
- Amazon Bedrock AgentCore payments is a managed service that lets an AI agent pay for a single request from a seller, inside a session budget the developer sets and against a list of sellers the account approves.
- AWS added AWS Billing as a payment option on 19 November 2026, so an agent can buy x402-enabled software, APIs, data and content on AWS Marketplace in US dollars and have the charge settle on the developer's AWS bill.
- The seller answers an unpaid request with HTTP 402 and a signed quote in a response header, and AWS Marketplace validates that signature against the seller's registered key before any money moves.
- The agent exchanges the quote for a payment token at the ProcessPayment API, and the token stays valid for about five minutes, which keeps quote, payment and redemption inside one pass.
- Budgets and permissions are split across two IAM roles in the published sample: one role sets the session budget and cannot pay, the other pays and cannot create sessions.
- The sample session budget is $0.05 with a $0.02 cap per request, and the demonstrated run bought one search result for $0.01 that appeared as an AWS Marketplace line item.
- At launch AWS Billing supports the x402 exact scheme, where the seller quotes a fixed price per request, and settlement runs asynchronously onto the monthly bill.
Figure 1 from the AWS post: the agent, AgentCore payments and the AWS Billing integration that meters a Marketplace purchase onto the account. Source: aws.amazon.com/blogs/machine-learning, retrieved 19 November 2026.
An agent that needs paid data mid-task usually faces the same wall: a human signs up, adds a card, and creates an API key before the machine can call anything. AWS's answer, published on 19 November 2026, puts the purchase inside the cloud account. AgentCore payments became generally available in August 2026 with support for open payment protocols; the change announced on 19 November 2026 is that AWS Marketplace sellers and the AWS Billing integration joined it, so the receipt lands on a bill an accountant already reconciles.
Netics visual, 19 November 2026: the four hops between discovery and settlement, drawn from the walkthrough AWS published with its sample agent.
Editorial count: six calls between a question and a paid answer
The flow is short enough to hold in one hand. Discovery uses three read-only tools in the AgentCore Gateway Marketplace connector: search listings, fetch one listing, then list its fulfillment options, and the search returns endpoints that accept x402.
The fourth call goes to the seller with no payment attached. The seller replies with HTTP 402 and a signed quote in the PAYMENT-REQUIRED header, which states the price for that request. The agent forwards the quote to ProcessPayment with the payment type AWS_BILLING_X402; if the session still has budget, the service returns a payment token, and if it does not, the call fails and nothing is charged. The sixth call repeats the original request with the token in the PAYMENT-SIGNATURE header and receives the content.
A signed quote, a session budget, a five-minute token
Two details carry most of the design. The first is that the quote is signed by the seller and verified by AWS Marketplace against the seller's registered key, so a quote whose price was altered in transit fails validation and the agent cannot be talked into a different number by the thing it is buying from.
Netics visual, 19 November 2026: the controls that bound a purchase, mapped to the question each one answers.
The second is the token lifetime. Payment tokens remain valid for about five minutes, which forces the quote, the payment and the redemption into a single pass. That choice rules out a workflow where an agent collects a price early, thinks for ten minutes and pays later, and it means retry logic has to re-quote and cannot reuse a stale token.
The controls that bound what an agent spends
The published sample sets up three IAM roles alongside the service-linked role AWSServiceRoleForMarketplaceAgenticCommerce. The session role creates payment sessions and sets budgets but cannot pay at all. The agent role pays and cannot create sessions, so the agent has no path to raising its own ceiling. That separation is the most interesting line in the whole post, because it treats the budget as an authority that lives outside the component being budgeted.
Netics visual, 19 November 2026: the three numbers from the sample configuration that show how small a first budget can be.
Three AgentCore controls sit above the roles: spending limits, an approved seller list through AgentCore policy, and the payment session cap enforced by AgentCore payments itself. For organisations that use it, Private Marketplace adds rules that restrict the products an agent can buy. Transactions land in AWS CloudTrail and AWS Cost Explorer, and the first purchase from a seller creates an agreement that later purchases are tracked against.
A sample that spends one cent
The GitHub sample runs a research agent that looks for a live search tool, compares two listings, and buys one request. Its defaults are modest on purpose: a session budget of $0.05, a per-request cap of $0.02, and a test purchase of $0.01 from a seller charging a cent. The agent compared two listings before buying, which is the behaviour a budget is meant to encourage.
Where the accounting gets hard for an SME
Three limits deserve attention before anyone points an agent at a catalog.
The AWS What's New entry of 19 November 2026 describing agentic payments over x402 and the settlement on the AWS bill. Source: aws.amazon.com/about-aws/whats-new, captured 19 November 2026.
The first is scope. At launch AWS Billing supports the x402 exact scheme, where each request carries a fixed price, so usage-based pricing models need a different arrangement. The second is timing: settlement runs asynchronously and the charge appears as a Marketplace line item on the monthly bill. That schedule supports reconciliation. Hourly spend tracking remains difficult. The third is attribution: the charge lands on the AWS account that holds the payment manager. That identifies total agent spending at account level. Attributing the cost to a customer's task requires your own metering.
That last gap matters most in a support or research product, where the natural unit of cost is a customer conversation. AWS says transactions appear in Cost Explorer and each product appears as a Marketplace line item on the AWS bill; splitting costs by end user requires your own metering on top.
A budget bounds the amount spent. An agent that buys the wrong dataset stays inside its five cents and pulls that dataset into a prompt, and nothing in the payment path evaluates whether the purchase was worth making. That judgement stays with the agent's instructions and with the person who wrote the approved seller list.
What to test before an agent holds a budget
Start with the read-only path. One paid search request, one approved seller, a session budget small enough that a mistake costs less than lunch. The sample defaults are a reasonable template for a first week, and the CloudTrail record gives an audit line per purchase.
The AWS Machine Learning Blog post of 19 November 2026, with the walkthrough and the sample repository it references. Source: aws.amazon.com/blogs/machine-learning, captured 19 November 2026.
Then decide who owns the agreement. The first purchase creates a commercial relationship between the AWS account and the seller, which is a procurement decision with a technical trigger, and a team that treats it as a configuration detail discovers it during an invoice review.
Finally, keep the agent's runtime somewhere you can inspect it. An agent that spends money needs its loop, its tools and its logs in a place its operators can read, which is the case for a self-hosted AI agent platform and harder to arrange when the loop is a black box with a payment method attached.
Originally published on the Netics blog.
來源:DEV Community · dev.to





