deniz.in

Markets

Weather

Loading weather

· via dev.to (home feed)

AI agents can now pay per request on AWS Marketplace and settle on the AWS bill

AWS's AgentCore payments now supports AWS Billing, letting AI agents buy x402-priced APIs, data and software on AWS Marketplace per request with charges settled on the developer's monthly AWS bill.

AI agents can now pay per request on AWS Marketplace and settle on the AWS bill

AWS Billing arrives as a payment option

Amazon Bedrock AgentCore payments is a managed service through which an AI agent pays a seller for one request, inside a session budget the developer sets and against a list of sellers the account has approved. According to dev.to, the service reached general availability in August 2026 with support for open payment protocols, and on 19 November 2026 AWS added two pieces: AWS Marketplace sellers, and AWS Billing as a settlement option. An agent can now buy x402-enabled software, APIs, data and content in US dollars, with the charge appearing on a bill the finance team already processes.

The problem this targets is familiar. An agent that needs paid data mid-task usually waits while someone registers an account, attaches a payment card and generates credentials before the machine can call anything. Moving the purchase inside the cloud account removes that bottleneck.

The six-call purchase flow

The dev.to walkthrough counts six calls between a question and a paid answer. Discovery uses three read-only tools in the AgentCore Gateway Marketplace connector: search listings, fetch one listing, then list its fulfillment options. Search results expose endpoints that accept x402.

The agent then calls the seller without payment attached. The seller replies with HTTP 402 and a signed quote in a response header stating the price for that request. AWS Marketplace checks the quote's signature against the seller's registered key before any money moves, so a price tampered with in transit fails validation and cannot be quietly swapped mid-flight.

The agent forwards the verified quote to the ProcessPayment API with the payment type AWS_BILLING_X402. If budget remains, the service returns a payment token valid for roughly five minutes; if not, the call fails and nothing is charged. The final call repeats the original request with the token in the PAYMENT-SIGNATURE header and receives the content. The short token lifetime forces quote, payment and redemption into a single pass, and retry logic must re-quote rather than reuse a stale token.

Budgets live outside the agent

The published sample splits authority across two IAM roles alongside a service-linked role. One role creates payment sessions and sets budgets but cannot pay; the agent's role can pay but cannot create sessions, so the agent cannot raise its own spending limit. Above the roles sit three AgentCore controls: spending limits, an approved seller list via AgentCore policy, and the session cap enforced by the payments service itself. Private Marketplace can further restrict which products are purchasable. Transactions land in CloudTrail and Cost Explorer, and the first purchase from a seller creates an agreement that later purchases are tracked against.

The sample's defaults are deliberately small: a $0.05 session budget, a $0.02 cap per request, and a demonstrated purchase of one search result for $0.01. The research agent compared two listings before buying — exactly the comparison-shopping behaviour a spending cap should produce.

Scope, timing and attribution limits

Dev.to flags three constraints. Scope: at launch AWS Billing supports only the x402 exact scheme, where each request carries a fixed price, so usage-based pricing needs a different arrangement. Timing: settlement runs asynchronously onto the monthly bill, which suits reconciliation but makes hourly spend tracking difficult. Attribution: charges land on the AWS account holding the payment manager, so total agent spend is visible at account level, but mapping costs to an individual customer's task requires your own metering — a real gap for support or research products where costs should map to customer conversations.

A budget also bounds only how much is spent, not whether the purchase was worth making. An agent that buys the wrong dataset stays inside its five cents and pulls that data into its prompt regardless.

Why it matters

This is a new monetization primitive for agentic commerce: per-request payment priced in dollars and settled through infrastructure billing that companies already operate. The control model — signed quotes verified by the marketplace, expiring payment tokens, and budgets held in a role the agent cannot touch — sketches what responsible spending looks like when software, not a person, is the buyer. The caveats are equally instructive: the first purchase opens a commercial relationship with a seller, triggered by code rather than procurement review, and usage-based pricing plus per-customer attribution remain unsolved. For API and data sellers it is a new distribution channel; for operators it is a reminder to start with a small budget and keep the agent's runtime and logs somewhere they can be inspected.

  • #aws-marketplace
  • #ai-agents
  • #payments
  • #x402
  • #agentic-commerce

Related posts