Short answer: AWS Marketplace Agentic Commerce lets AI agents pay for your API, MCP tool or data feed one request at a time, in US dollars, with the charge landing on the buyer’s existing AWS bill instead of a crypto wallet. AWS keeps a 3% listing fee and pays you through normal AWS Marketplace disbursements, and Tavily’s search endpoint is listed at $0.01 a request. The catch: it only runs in the us-east-1 Region, you must be a registered AWS Marketplace seller in an eligible country, and AWS publishes no seller earnings. The main alternative is open x402 on the Base network, where agents pay in USDC with no AWS account at all.
Key points
- AI agents built on Amazon Bedrock AgentCore can find x402-enabled AWS Marketplace listings, pay per request through AgentCore payments and settle on their company’s AWS bill.
- Sellers set the price in each signed quote their endpoint returns. Standard SaaS public offer listing fees apply, which AWS lists as 3% for Agentic Commerce products.
- Agentic Commerce products are separate listings: one usage-based public offer, no free trials, no private offers and no free pricing.
- It is available in US East (N. Virginia) only, with quotes in USD. Paid sellers must reside or be incorporated in one of AWS’s eligible jurisdictions.
- Nobody has published what sellers earn yet. Public data on open x402 shows most paid endpoints get a handful of buyers.
What is AWS Marketplace Agentic Commerce?
It is AWS’s version of a paywall for agents. When an agent calls your endpoint without paying, your server answers with HTTP 402 Payment Required and a signed price quote. The agent hands that quote to AgentCore payments, which checks the session budget and returns a payment token. The agent retries with the token, your endpoint verifies it and serves the request. AWS then creates an agreement between the buyer and you on the first purchase and meters every later charge to the buyer’s AWS invoice.
It builds on the same open x402 protocol we covered in our guide to selling APIs to AI agents with x402, with one big difference for sellers: the money moves in dollars through AWS billing, not USDC on a blockchain. The buyer needs no wallet and no API key from you, and their finance team sees your product as a normal AWS Marketplace line item with spending limits, approved seller lists and AWS CloudTrail logs.
AWS announced it alongside a wider AWS Marketplace update ahead of re:Invent, including a new Data as a Service product type and an agent mode that can walk buyers through checkout. In AWS’s own walkthrough, a research agent searches the marketplace, compares two listings, pays Tavily $0.01 for one web search and cites the result.
How much can you earn selling to agents on AWS Marketplace?
There is no honest number yet. AWS has not published seller counts, request volumes or payouts for Agentic Commerce, and the catalog is described as “select” products from verified sellers. What we can do is show the unit economics and the closest public data.
The per-request math is simple. If you charge $0.01 a request, AWS’s 3% fee leaves you $0.0097. Ten thousand paid requests in a month would gross about $97 after the fee, before your own hosting and model costs. That is an illustration, not a forecast.
The nearest real-world signal is open x402, which has run longer. Visa and Artemis count about $15.0M of x402 volume across 109.6M transactions since launch, with wash and test traffic removed. Tanod’s scan of the Coinbase Bazaar found only 7,465 of 36,078 listings had three or more paying wallets over 30 days, and the median listed price was $0.01 a call. In other words, most endpoints earn little, and a few useful ones take most of the volume.
The reason AWS could still matter: its buyers are companies that already approve AWS spend. If your product clears AWS’s review, you are selling into budgets that exist, not asking a solo developer to fund a wallet.
How does it compare with open x402 and a normal API?
| AWS Marketplace Agentic Commerce | Open x402 on Base | Normal API keys with Stripe | |
|---|---|---|---|
| Buyer pays with | USD on their AWS bill | USDC from an agent wallet | Card on a plan or credits |
| Your cost per sale | 3% listing fee | Coinbase facilitator: free for 1,000 settlements a month, then $0.001 each | Stripe’s standard US card rate of 2.9% plus 30 cents |
| Buyer signup with you | None | None | Account and API key |
| Who can sell | Registered AWS Marketplace sellers in eligible countries | Anyone with a wallet address | Anyone Stripe supports |
| Refunds | Billing adjustments on the buyer’s invoice | Final, manual transfer back only | Standard card refunds and chargebacks |
| Discovery | AWS Marketplace connector in AgentCore Gateway | Catalogs such as the Coinbase Bazaar | Your own marketing |
| Best fit | APIs and data that enterprise agents need mid task | Small, cheap calls to any agent | Humans and teams on monthly plans |
The fixed 30 cent card fee is why per-request pricing at a cent or less never worked on normal card rails. Both x402 routes remove that floor. AWS adds enterprise billing and review on top, and charges a percentage instead.
How do you list an API with AWS Marketplace Agentic Commerce?
- Register as a seller. In AWS Partner Central, complete seller registration with tax forms (W-9 for US entities, W-8 plus VAT or GST details for others) and a bank account in an eligible jurisdiction. Paid listings need this before you can create offers.
- Create a new SaaS API product. In the listing wizard, set the delivery method to API-based agents and tools and pick Agentic Commerce as the access model. You cannot add it to an existing product or switch later, so list it separately if you also sell API keys.
- Build the x402 endpoint. Use the AWS Marketplace x402 seller SDK for Python or TypeScript (the TypeScript package is
@aws/fiat-extension-for-x402). AWS also publishes anaws-marketplace-agentic-commerceagent skill that Claude Code or another coding agent can load through the AWS MCP Server to wire up quotes and token checks. - Register a quote-signing key. Point AWS at a JWKS URL or an AWS KMS key, and put your product ID in every quote as
settlement.product_id. Keep quote lifetimes short. - Apply the production settings. Accept each payment token once using a store all instances share, use a shared DPoP nonce store, block unpaid HEAD requests from running paid routes and throttle paid routes.
- Set an estimated cost per request and test. Buyers see the estimate before paying. AWS’s AgentCore sample runs a full purchase with a $0.05 session budget and a $0.02 per-request cap, so you can watch a real agent buy from you before you promote the listing.
What does it cost, and what are the risks?
- Fees: 3% of each charge, plus your infrastructure. Sellers in some jurisdictions may also owe tax on the listing fee.
- Slow cash: buyers pay on their monthly AWS invoice, and AWS disburses only after it collects, so expect weeks, not minutes, between a request and money in your bank.
- Narrow reach: only us-east-1, only USD, only agents set up with AgentCore payments, and only products a buyer’s Private Marketplace policy allows.
- Rigid offers: no free trial, no free tier and no private enterprise pricing on the Agentic Commerce product itself.
- Security work is yours: replayed tokens, proxy header spoofing and leaked signing keys all cost you money. AWS’s checklist exists because these mistakes are easy.
- Country limits: paid sellers must be in eligible jurisdictions such as the US, UK, EU states, Australia, Japan or the UAE. India-based sellers can only sell to buyers in India, and builders in countries outside the list, Pakistan among them, would need an entity in an eligible country.
What should you sell to agents?
Agents buy what they cannot cheaply do themselves mid task. AWS’s own examples are a single web search and a paid guardrail check. Tavily’s live search is the named launch seller, and the wider marketplace update features data providers such as Crunchbase, IMDb and Vaisala Xweather. Good fits for a solo builder look similar: a niche dataset you maintain, a scraper or parser for a hard source, a verification or compliance check, or a specialized model endpoint.
If you already run tools for agents elsewhere, such as Apify Actors that pay creators or the new agent app stores, AWS is another shelf for the same work, aimed at bigger buyers. If your customers already pay Anthropic directly, Claude linked billing solves a different problem: passing model costs on, not selling your own API.
Who is AWS Marketplace Agentic Commerce worth it for?
It suits developers and small API companies with a product agents already call, a business entity in an eligible country, and the patience for AWS seller review. It is a strong fit if your buyers are enterprises that prefer to spend through their AWS commit.
It is not a quick side income. With no seller data, one Region and a narrow catalog, treat it as a new distribution channel for an API you would build anyway. Start with one endpoint, price it per request, test it with the AWS sample, and only invest more once real agent purchases show up in your seller reports.
Sources
- AWS What’s New: AWS Marketplace now supports agentic payments with AgentCore
- AWS Machine Learning Blog: Enable AI agents to pay for AWS Marketplace x402 products
- AWS Marketplace Blog: AWS Marketplace helps humans and agents buy, deploy, and transact
- AWS Marketplace docs: Listing Agentic Commerce products
- AWS Marketplace docs: Listing fees for sellers
- AWS Marketplace docs: Getting started as a seller and eligible jurisdictions
- AWS Marketplace docs: Disbursement preferences
- GitHub: aws/fiat-extension-for-x402
- Tavily docs: x402
- Coinbase x402 help and answers
- Visa: agentic payments from the ground up
- Tanod: what x402 sellers earn



