Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

AI news ·

AWS Marketplace lets AI agents buy products and pay per request without human setup

AWS Marketplace now lets AI agents buy software and data on their own, charging per request to a customer's existing AWS bill. The x402 protocol routes spending through pre-set limits and approved seller lists, giving finance teams full CloudTrail visibility without manual procurement steps.

AWS Marketplace now lets AI agents buy software and data on their own, paying per request in US dollars through Amazon Bedrock AgentCore. The change means agents can complete tasks that require paid tools - like a single web search or a guardrail check - without a human stepping in to set up accounts, enter payment details, or manage API keys for each seller.

The new capability, announced November 19, routes all charges to a customer's existing AWS bill. No crypto wallet is required. Customers enable the AWS Marketplace payment connector inside AgentCore payments, then agents discover listings through the AgentCore Gateway. A research agent can purchase one search result. A coding agent can call a paid safety service mid-task. Spending limits, approved seller lists, and guardrails are set before agents transact.

How agentic payments work under the hood

Agentic payments run over the x402 protocol. When an agent needs a paid resource, it finds the listing through the AWS Marketplace connector, checks against the customer's pre-set limits and Private Marketplace policies, and completes the transaction. Every action appears in AWS CloudTrail and AWS Cost Explorer, giving finance and operations teams the same visibility they have for other AWS spending.

For sellers, the model removes the need to build sign-up flows, billing systems, or payment collection infrastructure. They register with AWS Marketplace, configure agentic payments for their listings, and integrate the AWS Marketplace x402 SDK. AWS Marketplace collects payments from buyers and disburses funds to sellers through existing seller disbursement channels.

What this shifts for procurement and finance teams

The setup collapses a multi-step procurement process into a policy layer. Instead of negotiating individual vendor contracts, approving API keys, and reconciling separate bills, finance teams define spending limits and approved sellers once. Agents stay within those boundaries. This matters for legal and insurance professionals whose teams increasingly use AI tools that need on-demand access to third-party data - property records, compliance checks, or identity verification services - where per-request pricing makes more sense than monthly subscriptions.

Operations and product development teams gain a faster path to experimenting with paid AI services. A developer building an internal support agent can plug in a paid moderation API without waiting for procurement to onboard a new vendor. The agent simply calls the service, and the charge lands on the AWS bill.

Seller implications

For companies that sell APIs, datasets, or AI services, agentic payments open a distribution channel that does not depend on convincing a human to fill out a registration form. Sellers list once on AWS Marketplace and become available to any agent whose operator has enabled the payment connector. AWS Marketplace handles the transaction lifecycle, from payment collection to disbursement.

The capability is available in all AWS Regions where AgentCore payments operates. Sellers can find implementation details in the AWS Marketplace Seller Guide.

Why this matters for customer support, sales, and hospitality teams

Customer support and sales workflows increasingly depend on agents that pull data from multiple sources - CRM records, identity verification services, sentiment analysis tools, or scheduling APIs. Each of those sources today typically requires a separate commercial relationship. Agentic payments let a support agent query a paid sentiment service for one interaction, or let a booking agent verify an identity through a paid check, without a manager approving each vendor relationship. For hospitality and events teams running AI-assisted booking or concierge services, the ability to pay per request means seasonal or spike-driven usage doesn't require long-term contracts. The spending controls and CloudTrail visibility give finance leads the audit trail they need without slowing down the operation.

Share