Can an AI agent buy from you?
In September 2025, ChatGPT learned to check out. Six months later, a federal judge was deciding whether a different AI was allowed to shop at Amazon at all. What actually changed, who needs to care today, and a plain checklist for sellers.
On September 29, 2025, OpenAI and Stripe announced Instant Checkout — products purchasable inside a chat, with no browser tab, no cart page, and no card form. Etsy shipped at launch, with Shopify and Walmart merchants following. Underneath it sat a new open standard, co-developed by the two companies: the Agentic Commerce Protocol.
Then came the reality check. Within six months OpenAI had scaled the first version back into ChatGPT Apps — early item data proved hard to keep accurate, and merchant onboarding ran heavier than promised. And on March 10, 2026, a federal judge blocked an AI shopping agent from Amazon entirely, in the first real legal test of who is allowed to buy from whom.
So the question for anyone selling online has quietly changed. It is no longer “can an AI agent read my site” — it is “can one complete a purchase here, and have I decided whether it may?” This guide is the short version of what you need to know.
What Instant Checkout actually is
Strip the branding and an agentic purchase needs three machine-readable things from the seller. Everything else — the protocols, the acronyms, the launch posts — is plumbing for these three.
A machine-readable catalog
What you sell, at what price, in stock or not — as structured data or a feed an agent can parse without clicking through your theme’s JavaScript.
A checkout an agent can drive
Endpoints for cart, order, and status that a program can call — not a flow designed around a human with a mouse and a credit-card form.
A payment leg with a mandate
Proof that a human authorized this agent to spend — tokens that can be scoped, capped, and revoked, instead of a bot typing card numbers.
The field has already split into three named protocols. You do not need to love the acronyms; you do need to know which one your channel speaks.
Agentic Commerce Protocol
The OpenAI + Stripe protocol behind Instant Checkout. Merchants publish a structured product feed and implement the checkout spec; payment providers implement delegated payment. Discovery follows the web’s favourite convention: a /.well-known/acp.json file on the seller’s domain.
Universal Checkout Protocol
The Google + Shopify answer, with Stripe shipping an Agentic Commerce Suite on top of it. Same discovery pattern at /.well-known/ucp. If ACP is the ChatGPT rail, UCP is the Google-surfaces rail — large sellers will end up speaking both.
Agent Payments Protocol
The payment-authorization layer underneath: cryptographically signed mandates that prove who authorized an agent to pay, now stewarded by the FIDO Alliance. You will not implement it yourself — your payment provider will — but it is why “the agent bought it” can become an auditable fact.
Stripe’s own technical field guide (March 2026) is the most useful single document a seller can read: make sure agents know you exist, help them understand how to use your site, configure for nonhuman traffic — with llms.txt, server-rendered content, product feeds, and rate limits named explicitly.
The first legal test arrived fast
In November 2025, Amazon sued Perplexity over Comet, its agentic browser: the complaint was that a bot was browsing, selecting, and buying on Amazon on users’ behalf without authorization. On March 10, 2026, a federal judge in California granted Amazon a preliminary injunction — finding “strong evidence” of unauthorized access, including through password-protected customer logins — and ordering Perplexity to stop and delete the collected data. GeekWire called it what it is: an early test of agentic commerce. A federal appeals court later vacated the injunction — which mostly proves the law here is unsettled.
The lesson for sellers is not “block all agents.” It is that your robots.txt, your terms of service, and your bot policy are now documents a court may read. A site that states plainly which agents are welcome to transact — and which are not — is in a materially better position than one that never decided.
Who needs agent-payable surfaces now
Not everyone — the urgency tracks how feed-shaped your sales already are. If your “product” is a scoped engagement priced in conversation, your job today is being readable and negotiable by agents, not payable. If you recognise yourself below, the checklist is for you.
Retail & e-commerce
The obvious case. Your feed is the new shelf: if price or stock drifts in the feed while the site says otherwise, agents will confidently sell the wrong thing — inaccurate item data is exactly what tripped up the first Instant Checkout cohort. Structured data on product pages, a current feed, and a bot policy that admits shopping agents are now baseline retail hygiene.
Travel
Comparison shopping is the most agent-native buying behaviour there is, and travel inventory is already feed-shaped. Availability, rates, and cancellation terms that a machine can read without scraping five pages decide whether an agent books you or the hotel next door. Payment and ticketing stay the hard half — start with legibility.
B2B self-serve
Reorder agents and procurement copilots are the quiet near-term case: “renew our consumables at the best contracted price” is a purchase a bot can complete. Public catalog pages with real (or account-tiered) prices and an API beat a “contact sales” wall. Quoted, relationship-priced business still ends in a human — the agent’s job is shortlisting and paperwork.
The plain checklist
Eight items, in the order we would do them. The first three make you legible; the middle three make you deliberate; the last two make you safe. Our free agent-readiness check now detects the commerce-shaped ones — product markup, declared feeds, ACP/UCP discovery files — as signals only: it tells you what is there, and makes no claims about compliance.
- 01
Product pages carry schema.org Product and Offer markup
Name, price, currency, availability — server-rendered, on the page, not injected after hydration. This is the first thing any shopping agent reads.
- 02
Prices and stock are never JavaScript-only
If a plain HTTP GET cannot see the price, most agents cannot either. Render the number in the HTML.
- 03
A product feed exists — and is declared
Google Merchant feed, a /products.json endpoint, or a feed API. Declare its URL in llms.txt or robots.txt so an agent can find it without guessing.
- 04
robots.txt states a policy that matches your commercial intent
Blocking GPTBot and then wondering why no agent surfaces your products is a strategy mismatch, not a technicality. An explicit no is fine — make it deliberate.
- 05
Rate-limit agents instead of blocking them
A 429 with a Retry-After header is the polite wall. A hard 403 is how you end up as a defendant’s exhibit — or invisible.
- 06
If you are in an agent-checkout program, publish the discovery files
/.well-known/acp.json (ACP) and/or /.well-known/ucp (UCP), kept in sync with what you actually sell.
- 07
Payment rails through a PSP that supports agentic checkout
Stripe and peers now ship this. The requirement that matters: scoped, revocable payment tokens — never a stored card an agent can reuse forever.
- 08
Write the policy down before a court asks
Who may transact on a customer’s behalf, up to what amount, and what your terms say about agents. Amazon v. Perplexity turned a bot policy into a legal document; yours should be deliberate too.
Where we come in
We do not sell products; we sell the work of making a company legible to machines — the thesis this company runs on. Making a commerce surface agent-payable (feeds, markup, discovery files, bot policy, kept current) is a focused piece of work we do, and our free check scores where you stand before and after. Prefer to do it in-house? The checklist above is genuinely the whole game — talk to us only when you want it done by next week.
Where the facts come from
- OpenAI — Buy it in ChatGPT: Instant Checkout and the Agentic Commerce Protocol — the launch announcement, Sept 29, 2025
- OpenAI — Agentic Commerce Protocol docs — product feeds, the agentic checkout spec, delegated payment
- Stripe — How to prepare for agentic commerce: a technical field guide — feeds, llms.txt, well-known files, nonhuman traffic, governance — March 2026
- CNBC — Amazon wins court order to block Perplexity’s AI shopping agent — the March 10, 2026 preliminary injunction
- GeekWire — Judge blocks Perplexity’s AI bot from shopping on Amazon — “an early test of agentic commerce”
- Reuters — Amazon wins order blocking access to Perplexity’s AI shopping agent — the wire report on the same ruling
We are not affiliated with OpenAI, Stripe, Google, or Amazon. Protocol details are stated as their documentation states them, as of October 2026; the 9th Circuit outcome of the Amazon v. Perplexity dispute may have moved since.