AWS Marketplace now lets AI agents search, review and check out software, and lets developer-built agents pay some sellers directly on your AWS bill. The decision in front of procurement and IT this month is who and what may buy without a person. The controls exist, but they sit in three different places: IAM policies on the Marketplace side, a per-project auto-approve switch inside agent mode, and spending limits inside Amazon Bedrock AgentCore payments. None of them is set up for you by the procurement policy you already have.
AWS's VP of AWS Marketplace and partner services, Matt Yanchyshyn, told Fortune on November 19 that customers can let agents make a purchase "100% independently" in a product category they choose, or require a human handoff on everything. AWS's own agent mode buyer guide says the opposite for its console channel: "You always choose Subscribe yourself." Both statements can be true, because they describe different channels. Your job is to know which one each of your teams is using.
What AWS Added to Marketplace This Week
AWS added a checkout agent, a trust agent for security reviews and a deployment agent to Marketplace agent mode, plus agent purchasing of x402 products through AgentCore payments. Agent mode itself is older. AWS launched it on November 30, 2025 as a conversational discovery tool across more than 30,000 listings, able to start a purchase or produce a purchasing proposal for internal approval.
The new pieces, per AWS's Marketplace features page and Constellation Research's launch report:
- The checkout agent walks a buyer through pricing, configuration, governance, compliance and deployment in one conversation. Constellation reports it applies the buyer's own purchase order thresholds and summarizes license terms in plain English.
- The trust agent pulls vendor compliance evidence from Drata and Vanta trust centers. Constellation puts launch coverage at more than 1,000 vendors and 4,500 of about 35,000 listings.
- The deployment agent provisions supported AMI products with CloudFormation. The buyer guide says it supports "more than 100 AMI products" and provisions nothing until you approve the plan.
- For agent payments, AI agents "can discover and purchase select products in AWS Marketplace using the x402 agentic payment protocol through AgentCore payments, and pay in USD on your existing AWS bill," per the features page.
AWS pitches this partly on conversion. Constellation reports that buyers who go through agent mode "convert at a 6% to 7% clip." That is a seller-side number with no baseline given, and it tells you AWS has a commercial interest in removing approval steps.
None of the AWS pages we read state whether the checkout, trust or deployment agents are generally available or in preview, or in which regions. Ask your account team before you write policy around them.
Can an AI Agent Actually Buy Software Without a Person?
Yes, through the AgentCore payments channel, and possibly in agent mode if someone turns on auto-approve. The three channels behave differently:
| Channel | Who confirms a purchase | Spending control | Where it is documented |
|---|---|---|---|
| Agent mode in the Marketplace console | The buyer chooses Subscribe | IAM, Private Marketplace, PO number | Buyer guide |
| Agent mode signed in to an AWS account | Allow or Deny per action, unless auto-approve is on for the project | IAM, plus organization service control policies | Authenticated experience |
| A developer's agent paying x402 sellers through AgentCore payments | No person by default | Per-session budget and expiry | AgentCore payments guide |
The console channel is the conservative one. The buyer guide lists "completing a purchase without your confirmation" among the things agent mode cannot do. It also cannot change, upgrade or cancel an existing subscription, and it hands a long list of offer types back to the standard page: multi-product offers, annual-pricing AMI and container offers, SaaS trials with usage pricing, variable-payment contracts and data products among them. If your organization requires approval before purchase, Subscribe is not available in agent mode for those offers at all.
The signed-in channel is where autonomy enters. AWS's authenticated experience page says agent mode asks you to confirm each action and account with Allow or Deny. It also says "Auto-approve is turned off by default," that it is set per project, and that when it is on "agent mode can take actions in your AWS account without asking for your approval each time." The page does not say which actions are excluded. Treat auto-approve as covering purchases until AWS tells you in writing that it does not.
The third channel is built for software that never opens a browser. Part of Amazon Bedrock AgentCore, AgentCore payments is a managed service for "microtransaction payments in AI agents to access paid APIs, MCP servers, and content," using x402 and the Machine Payments Protocol, both of which use the HTTP 402 Payment Required status code. With an AWS Billing connector, agents "can pay AWS Marketplace sellers that accept x402 payments, and they don't need a crypto wallet," and the charges land on your AWS bill. AWS opened the service in preview on May 7, 2026 in US East (N. Virginia), US West (Oregon), Europe (Frankfurt) and Asia Pacific (Sydney).
Who in Your Company Can Buy Through Agent Mode Today
Anyone whose IAM role carries the AWSMarketplaceFullAccess managed policy can buy through agent mode. The authenticated experience page is explicit: "To buy or subscribe, you need the AWSMarketplaceFullAccess managed policy." Signing in needs only signin:CreateOAuth2Token against the marketplace-mcp.amazonaws.com service principal, which that same managed policy already includes. Deploying also needs AmazonSSMFullAccess and AmazonEC2FullAccess.
That makes the policy attachment list your real buyer list. If AWSMarketplaceFullAccess was granted years ago so engineers could subscribe to an AMI, every one of those roles can now buy through an agent. The same page notes that a service control policy in your AWS organization can block sign-in even when the role has the permission, which gives you an organization-wide brake if you want one while you sort out roles.
Projects also travel. Moving an agent mode project from the browser into an AWS account gives "Anyone who shares this AWS account" access to it, per AWS. A shared sandbox account with broad Marketplace rights is the place this goes wrong first.
What the Trust Agent's Security Review Covers
The trust agent runs one questionnaire, the Consensus Assessments Initiative Questionnaire (CAIQ), and only against sellers whose trust center runs on Drata or Vanta. AWS's security and compliance page says agent mode maps seller evidence, or evidence you upload, to each CAIQ control and highlights gaps, and that "other questionnaires aren't supported currently."
A CAIQ is a standard questionnaire of cloud security controls that a vendor can complete once and share with every buyer. If your third-party risk team uses SIG, a custom questionnaire or a sector framework, the trust agent produces a first draft at best.
Three limits matter for an auditor:
- "AWS doesn't audit, certify, or verify the seller's compliance claims." The output is a mapping of the seller's own evidence.
- NDA-gated documents such as SOC 2 reports need the buyer to accept the seller's NDA through the trust center, and if your organization already has an NDA on file, "you receive access automatically."
- A new assessment replaces the previous one in your session, so download each one before you rerun it, or you lose the record of what the agent concluded.
Fortune reports that the agent quotes the exact passage from vendor documents, such as a SOC 2 report, behind each conclusion; Drata CEO Adam Markowitz told the outlet it takes the security review work "down to minutes." That makes the output checkable, which is what a reviewer needs. Fortune also cites a June 2026 G2 survey in which 39% of B2B buyers named IT security reviews as the biggest source of delay after picking a vendor, so the trust agent is aimed at a real bottleneck.
Where Coupa, Ariba and Private Marketplace Fit
If you buy through Coupa or SAP Ariba, agent mode does not complete the purchase: the buyer guide says accounts that use "a procurement system integration, such as SAP Ariba or Coupa" get a message and a link to continue elsewhere. Your requisition approvals stay intact for that path. The features page confirms that Coupa or SAP Ariba buyers can purchase from the same place they raise every other purchase order, and that you can assign a unique PO to each Marketplace transaction.
Private Marketplace is the other existing control that carries over. It restricts users to a catalog of pre-approved products, and agent mode turns an unapproved product into a request link. If you never built a Private Marketplace catalog because nobody browsed Marketplace without a ticket, an agent that searches 35,000 listings on a developer's behalf changes that math.
The AgentCore channel sits outside both. A developer's agent paying an x402 seller through the AWS Billing connector is governed by the session budget the developer set, not by your Coupa approval chain. AWS's features page says you can "set spending limit transaction guardrails in AgentCore payments before an agent can transact, and audit every agent-initiated transaction in AWS CloudTrail." In the AgentCore guide, each PaymentSession carries a maxSpendAmount, a currency and an expiry, and when either runs out "further payment requests are denied." Those limits belong to whoever writes the agent. Someone in finance needs to own the defaults.
Vanta's Bill Fitzgerald, also quoted by Fortune, expects agents to take on small, high-volume purchases autonomously while seven-, eight- and nine-figure deals keep "a human in the loop." That is a reasonable line to draw, and it is one you have to draw yourself, in dollars, per channel.
What to Do Before an Agent Transacts on Your AWS Bill
This Week:
- Pull every IAM role and user with
AWSMarketplaceFullAccessattached across your AWS organization, and remove it from any role an automated agent or shared sandbox uses. - Ask your AWS account team in writing whether agent mode's per-project auto-approve can complete a subscription, and whether the checkout, trust and deployment agents are GA or preview in your regions.
- Check CloudTrail for any AgentCore payments activity in your accounts, so you know whether a team is already transacting.
This Month:
- Decide which product categories, if any, an agent may buy without a person, and set a dollar ceiling for each. Put it in procurement policy so it does not live only in a developer's config.
- Build or expand your Private Marketplace catalog so agent mode's search only returns approved products.
- Have your third-party risk lead run one trust agent CAIQ assessment against a vendor you have already reviewed by hand, and compare the gaps it flags with yours.
Before Your Next Marketplace Renewal:
- Require any team building on AgentCore payments to register its
maxSpendAmountand session expiry defaults with FinOps, and alert on x402 charges in the AWS bill. - If your AWS commitment draws down on Marketplace spend (as ChatGPT Enterprise purchases through AWS can), model what agent-initiated purchases do to that drawdown before you negotiate the next term.
The Bigger Picture
AWS has handed buyers the controls for agent purchasing and left the policy to them. Procurement went through the same thing with purchasing cards and then with SaaS free trials on corporate cards: spending moved to whoever held the card, and the policy caught up afterward. This time the card is an IAM role and a session budget, and both are visible in CloudTrail if you look.
Start with the AWSMarketplaceFullAccess attachment list this week.
Continue Reading
- Buy ChatGPT Enterprise Through AWS to Draw Down EDP Commitments
- Your Coupa or SAP Ariba Suite May Be the First AI Tool to Test
- Your AI Shopping Agent May Buy After It Fails, Visa Finds
- OpenAI's ChatGPT Wallet Leaves Fraud Decisions to Merchants
- AWS Makes AgentCore V2 Default as Startup Tokens Can Repeat
- Freshworks to Acquire Torii for AI and SaaS Spend Governance
