Asset 20 8 2
Does AI recommend your business? Run the free check →

Join 15,000 business owners, marketers and entrepreneurs. The Sunday newsletter you'll be annoyed only arrives once a week.

Article

9 Agentic Commerce Platforms for Selling to AI Agents

The best agentic commerce platform depends on which side of the purchase you're on: merchants need their catalogue and checkout exposed to AI agents, while builders need a checkout API and payment credentials an agent can use. Decide which job you're solving first, because the products in this category barely overlap.

A shopper types into an AI chat: "Find me a waterproof walking jacket under the price of my last one, in navy, delivered by Friday." The assistant reads three shops' catalogues, compares sizes against an order history it's been allowed to see, picks one, and pays. The shopper never opens a product page. Somewhere in that chain, a merchant made the sale without a single visit to their site.

That chain has four links: a catalogue the agent can read, a checkout it can complete, a way to pay that the merchant trusts, and a site that doesn't confuse it on the way. Agentic commerce platforms each sell one or two of those links, and buying the wrong link is the most expensive mistake you can make here.

What's changed in the category

Big payment and store platforms now pitch agents as a sales channel. Stripe markets an Agentic Commerce Suite connecting businesses, agents and buyers, and Shopify has an agentic storefronts page for selling in AI chats from a merchant's existing store and checkout. If you already run on one of those, your first step may be switching something on rather than buying something new.

The catalogue is now a battleground of its own. Product feed vendors that used to push listings to shopping channels and retailers offer AI channels meant to make products discoverable inside large language models. If an agent can't read your stock, price and variants cleanly, it won't recommend you, however good your checkout is.

Pricing has new shapes too. A few agent checkout APIs charge per order placed and per product fetched instead of a flat licence. That changes the maths for anyone building a shopping agent at volume.

Then there's the site itself. WebMCP is being used to make a website readable and usable by agents, with directories and SDKs appearing around it, which matters most to merchants who aren't on a platform with a built-in agent channel.

Payments and identity for agents are sold as separate products. Tools that give an agent verified identity and payment credentials are a different purchase from the platform a merchant sells on. Mix the two up and you end up with a payments wallet when you needed a storefront, or the reverse.

For merchants: getting your products in front of agents

Stripe Agentic Commerce Suite

Merchants already taking payments on Stripe can use this suite to connect their catalogue and checkout to AI agents and buyers.

Shopify Agentic Storefronts

A Shopify feature for selling through AI chats that reuses the store and checkout a merchant already runs on the platform.

BigCommerce

Hosted ecommerce platform with an agentic commerce offering pitched at both retail and B2B sellers, not just consumer brands.

Productsup

Product feed management with AI channels, so a catalogue can reach LLMs alongside the retailers and shopping channels it already feeds.

nekuda

Small vendor whose tool and SDK make an existing website agent-ready using WebMCP, then test how agents get through checkout.

For builders: letting agents check out and pay

firmly

Shoppers can buy inside AI agents, articles and ads without being redirected away, which is the whole point of this small platform.

Rye

If you're building a shopping agent, this checkout API lets it buy products from a wide range of online stores.

Skyfire

Gives AI agents verified identity and payment credentials, so they can access services and complete checkout across the open web.

Work with me

Want AI doing the heavy lifting in your marketing?

I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.

Crossmint

Wallet and payments platform letting agents transact in both ordinary currency and stablecoins, aimed at developers rather than shop owners.

The three forks that decide it

Are you selling, or building the buyer? A merchant wants agents to find and buy their products. A developer building a shopping assistant wants that assistant to buy from anyone. These are opposite ends of the same transaction, and the tools for each rarely do the other job. The merchant tools above are about exposure. The builder tools are about action.

Is your store already on a big platform? Then start with what your platform offers, because it'll reuse your existing checkout, tax and fulfilment set-up. If you're on a custom build or a smaller platform, you'll need a feed tool to get your catalogue readable and an agent-readiness layer for the site itself. Our guide to headless commerce platforms is worth a read if your front end and back end are already separate.

How do you want to pay? Pricing in this category comes in three shapes. Some tools charge per order and per product fetch. Some charge a monthly plan. Others don't publish a price at all and quote you. Where a price is published, the units don't line up: a monthly platform plan, a monthly developer plan, a fee per active wallet beyond a free allowance. Where it isn't, you're in a sales conversation, so go in with your expected monthly orders and browse volume written down.

A rehearsal you can run this week

Before you sign anything, rehearse the purchase the way an agent would make it. Pick three products: your best seller, something with lots of variants (size and colour), and something that's often out of stock. For each one, write down what an agent would need to know to buy it without asking a human: the exact price including delivery, stock by variant, delivery date to a real postcode, and the return terms.

Then check whether that information is machine-readable anywhere. Is it in your product feed, or only in images and tabs on the product page? Is delivery cost calculated before checkout, or only on the last step? Can the checkout be completed without a pop-up, a captcha, or a forced account sign-up? Every "no" is a point where an agent gives up and moves to a competitor.

If you're on a big platform, run the rehearsal through its agent channel once it's switched on, and see which of your three products comes through cleanly. If you're on your own build, use a trial of an agent-readiness tool to watch how an agent moves through your checkout. The products that fail tell you what to fix first.

Costs, risk and who's liable

The bill in this category is driven by volume more than seats. Per-order and per-fetch pricing means a busy agent can cost more than a quiet one, so model it on realistic order counts. If a tool charges per product fetch, every browse an agent makes counts, not just every purchase, so your fetch count can run many times your order count. With a monthly platform plan, ask in writing whether the agent channel sits inside the plan or is priced on top.

Free plans, trials and free allowances exist in this category but vary by vendor, so check each vendor's own pricing page on the day you start, and budget for a proof-of-concept phase on paid terms if you're building rather than selling.

The bigger risk is trust. When an agent pays, who's liable for a wrong size, a duplicate order or a fraudulent card? That's the gap identity and payment credential layers are built to fill. Before you route real money through any provider, get four answers from its terms or its sales team: who handles a chargeback when the agent placed the order, whether a spending limit can be set per agent or per shopper, how an order the shopper didn't intend gets cancelled, and what record of the agent's instruction is kept for a dispute. Keep a human-reviewed path for high-value or unusual orders whatever the answers are.

It's also worth thinking about the shopper's side. People will want to talk to the agent, not fill in forms, which links this category closely to AI shopping assistants that sit on a merchant's own site.

Do you make agentic commerce platforms? Tool makers can ask to be considered for a featured place on this list.

Where to start

If you're a merchant on one of the big store or payment platforms, switch on what your platform already offers and fix your feed before you buy anything else. If you're on a custom stack, start with a feed tool for AI channels and an agent-readiness layer, in that order. If you're building a shopping agent, start with a checkout API on a developer plan, add a payment and identity layer only when you're handling real money, and price your model on fetches as well as orders. And whichever side you're on, run the three-product rehearsal first. It's free, it takes an afternoon, and it'll tell you more than any demo.

Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.

Published and maintained by the Lilach Bullock team, covering marketing, AI and business growth.
Your buyers are asking AI who to use. Does it say you?

See for free whether ChatGPT, Claude, Perplexity, Gemini and Google name you, and get the plan to become the answer.

Check my AI visibility →
Sundays only

Get the Sunday newsletter.

One email a week. AI experiments, marketing tactics, and the workflows Lilach is building right now in her own business.

Subscribe free

Let’s get your marketing running on AI.

Book a free 30-minute call

We figure out what you need, where AI fits in, and what working together would look like.

Book the call →

Or take the 30-second calculator

You’ll see the hours and the money quietly leaking out of your week, and the three workflows worth building first.

Take the calculator →

Or grab the free AI resource library

Prompt packs, templates, checklists, and swipe files. The exact tools I build for paying clients. Yours, free.

Get the library →
Keep reading

More from the blog.