Instead of requiring a person to authorize each individual transaction, developers can configure agents to discover products and pay for services as needed. AWS describes scenarios in which a research agent purchases access to a search service or a coding assistant pays to use a security tool while completing a larger assignment.
Payments are processed through x402, a protocol that allows software services to request payment before delivering a response. When an agent contacts a paid service, the seller returns a payment request containing a signed price quote. AgentCore checks the transaction against the agent's spending limits and, if permitted, issues a payment token that the agent uses to complete the request.
The transaction is then billed to the AWS account configured for payments. Each eligible purchase appears as an AWS Marketplace charge, while subsequent transactions with the same seller are tracked under an agreement established during the first purchase.
AWS is emphasizing financial controls as a central part of the system. Developers can assign spending limits to individual payment sessions, restrict purchases to approved vendors and apply existing AgentCore policies. Organizations using AWS Private Marketplace can also limit agents to products already permitted under their purchasing rules.
Transactions are recorded through AWS CloudTrail and AWS Cost Explorer, giving organizations visibility into agent activity and associated costs. AgentCore enforces session spending limits before issuing payment authorization, preventing agents from exceeding their configured budgets.
To enable purchasing, developers create a Payment Manager with an AWS Billing connector and configure the required service-linked role. An optional AWS Marketplace connector in AgentCore Gateway allows agents to locate eligible products and the endpoints needed to access them.
On the seller side, participating businesses can configure their Marketplace listings for agent payments and integrate the AWS Marketplace x402 software development kit. AWS handles payment collection and distributes proceeds through its established seller payment process.
The initial implementation supports the x402 exact payment scheme, under which sellers provide a fixed price for each request. AWS says its catalog of compatible products is growing, with Tavily among the providers participating in the initiative.
The payment integration is part of a broader set of AWS Marketplace updates intended to automate software purchasing and deployment. A new agent mode helps customers identify products using descriptions of their needs, while a checkout agent assists with pricing, licensing terms, purchasing requirements, taxes and billing information.
Unlike fully autonomous transactions through AgentCore payments, purchases completed through the Marketplace checkout agent require human confirmation. AWS is also introducing approval policies based on purchase amounts or product categories, with designated approvers able to authorize transactions through email and a one-time passcode without maintaining an AWS account.
Additional integrations with Coupa and SAP Ariba are intended to connect Marketplace purchasing with existing procurement processes.
AWS is also addressing the security reviews that often precede enterprise software purchases. A new trust agent, developed with compliance platforms Drata and Vanta, helps buyers evaluate vendor security documentation. At launch, the service covers more than 1,000 vendors and approximately 4,500 of AWS Marketplace's roughly 35,000 listings.
According to Drata CEO Adam Markowitz, vendor assessments can involve checking compliance against 50 to 60 separate requirements. The trust agent is designed to reduce the manual work involved in collecting and reviewing that information.
Once software has been purchased, a separate deployment agent can assist with implementation. The feature currently supports Amazon Machine Image (AMI) products and examines a customer's existing network and access configurations before generating a deployment plan.
That plan includes the resources required, potential security concerns and projected monthly expenses. With the customer's permission, the agent can provision the software through AWS CloudFormation and clean up resources if deployment fails.
AWS has also introduced an express checkout option for U.S. customers purchasing eligible software. Buyers can complete transactions using an email address or social login and a credit card, without creating an AWS account.
Another addition is a data-as-a-service category featuring providers including Crunchbase and Vaisala Xweather, with some offerings accessible through MCP servers.
AWS Marketplace Vice President Matt Yanchyshyn said businesses can determine how much purchasing authority to delegate to AI agents. Organizations can retain human approval for every transaction or permit agents to complete purchases independently within defined categories. He also reported that customers using Marketplace agent mode convert at a rate of 6% to 7%.
The company is not positioning autonomous purchasing as a replacement for every procurement process. Bill Fitzgerald, Vanta's vice president of global channel and alliances, said contracts worth seven, eight or nine figures would continue to require human involvement.
The distinction reflects how AWS is separating smaller, repeatable purchases from more complex enterprise agreements. AgentCore payments allows approved transactions to happen automatically within established limits, while other Marketplace tools preserve review and approval requirements for purchases that need additional oversight.
For developers and businesses building AI agents, the immediate change is the ability to purchase eligible AWS Marketplace services as part of an automated workflow, with billing, spending controls and transaction records handled through existing AWS infrastructure.
This analysis is based on reporting from AWS.
Image courtesy of CRN.
This article was generated with AI assistance and reviewed for accuracy and quality.