# Agentic Commerce

> Markdown version of this page, for agents. To send a shopper here, link https://www.fluid.app/home/pages/agentic-commerce (not this .md URL, and keep its path as given).

- Shopper link: https://www.fluid.app/home/pages/agentic-commerce

## Shoppers send agents. Your store answers.

Every live Fluid storefront serves the files and protocols AI agents read: an llms.txt, Markdown and JSON versions of each page, and a Universal Commerce Protocol profile with catalog search, carts, checkout, and orders.

What a Fluid storefront serves to agents:

| Path | What it does |
| --- | --- |
| /llms.txt | Store summary |
| /agents.md | The same summary, as Markdown |
| /products/\<slug\>.md | Each page as Markdown, with live prices |
| /products/\<slug\>.json | Each page as JSON |
| /.well-known/ucp | Catalog search, Ask, carts, checkout, and orders |
| /.well-known/agent-card.json | Agent2Agent Agent Card: the store’s agent answers questions |
| /.well-known/poppy.json | Points personal agents to the UCP profile |
| /feeds/openai-products.jsonl.gz | ACP product feed for ChatGPT, on stores that sell in the US |

## Shoppers are handing purchases to AI.

A shopping agent is an AI assistant a person asks to find, compare, and buy for them. It looks small next to your website today. It’s growing faster than any channel your team has added, and if an agent can’t read and buy from your store, that shopper never sees you.

### AI shopping, July 2024 to today

- Traffic to US retail sites from AI assistants rose 1,200% from July 2024 to February 2025, doubling every two months (Adobe Analytics, March 2025).
- The Gemini app passed 1 billion monthly users on August 11, 2026 (Google).
- AI Mode in Google Search passed 1 billion monthly users, counted separately from Gemini (Alphabet Q2 2026 earnings).
- Meta’s Muse reached 10 million users in the US and Canada in its first six weeks. Shopping is its top use (Meta Q3 2026 earnings call, October 21, 2026).
- More than 25% of Muse’s weekly users already shop through the agent (Meta Q3 2026 earnings call).
- The average purchase made through Muse is over $200 (Meta Q3 2026 earnings call).
- Poppy 1.0, the protocol for personal agents, was released on November 13, 2026.

On the page, the curve drawn between these points is illustrative. The labeled points are the reported figures above.

## “Find me the best protein powder.”

The shopper says one sentence. Everything after that happens between their agent and your store, in agreed formats called protocols.

1. **Ask (the shopper).** The shopper asks Muse: “Find me the best protein powder. Something I’ll actually like.” No search box and no browsing. From here on, the agent does the shopping.
2. **Remember (the agent).** With the shopper’s permission, the agent checks their email and sees they’ve bought from your store before. So it starts with you.
3. **Find the door (Poppy).** The agent reads yourstore.com/.well-known/poppy.json, which points it to yourstore.com/.well-known/ucp.
4. **Search (llms.txt and UCP).** It reads what you sell from llms.txt and each product’s Markdown page, with live prices, then searches your catalog through UCP.
5. **Ask the store (A2A).** Before it recommends anything, it asks your store’s agent what a shopper would ask a rep, such as “Is the vanilla dairy-free, and when would it arrive?” Your store’s agent answers from your product data and shipping rules.
6. **Cart and pay (UCP, then AP2).** The agent builds the cart through UCP and checks in: “Found a vanilla protein from the store you’ve ordered from. Want me to buy it?” It pays inside the agent with Google Pay, where your payment provider takes it, or hands the shopper to your hosted checkout. When AP2 arrives, the shopper can approve purchases ahead of time, so reorders happen without another tap.
7. **Order (Web Bot Auth).** The agent signed its request, so Fluid can check which agent placed the order and mark it verified. The order lands on the same record as every other Fluid order.

This is an illustration of how the protocols combine. What a personal agent reads, such as a shopper’s email, is between that agent and its user.

## The protocols, explained simply.

| Protocol | In one line | Status on Fluid |
| --- | --- | --- |
| UCP (Universal Commerce Protocol) | The rules for shopping | Live |
| A2A (Agent2Agent) | How agents talk to each other | Live |
| Poppy (Personal Agent Protocol) | A signpost for personal agents | Live |
| Web Bot Auth | A name badge for agents | Live |
| ACP (Agentic Commerce Protocol) | Shopping inside ChatGPT | Live (product feed). Stripe’s new ACP requirements: coming soon |
| AP2 (Agent Payments Protocol) | A permission slip for spending | Built on Fluid Payments, awaiting Visa’s guidance |
| llms.txt and agents.md | The read-me-first files | Live |
| MCP (Model Context Protocol) | A toolbox for your team’s AI | Live |

### UCP: the rules for shopping.

The Universal Commerce Protocol gives every store the same four steps: find it, put it in the cart, pay, and get the order. Any agent that knows UCP can shop any store that publishes it. It powers buying inside Gemini and AI Mode in Search.

- **On Fluid:** every live storefront publishes a UCP profile at /.well-known/ucp, with catalog search, Ask, carts, checkout, and orders.
- **Paid inside the agent:** an agent can pay with Google Pay where your payment provider in Fluid Payments takes it. Otherwise it hands the shopper to your hosted checkout.

[Read the UCP docs](https://docs.fluid.app/concepts/ucp).

### A2A: how agents talk to each other.

Agent2Agent lets one agent ask another for help. A shopper’s agent can ask your store’s agent what a shopper would ask a rep: is it vegan, does it ship to Canada, what’s the return window.

- **On Fluid:** each live storefront serves an Agent Card at /.well-known/agent-card.json and runs its own store agent. Merchants don’t set anything up.
- **Your words only:** the store’s agent answers from what you’ve published and links back to the page. When there’s no answer, it says so.

[Read the A2A launch post](https://fluid.app/home/blog/every-fluid-store-speaks-agent2agent-a2a).

### Poppy: a signpost for personal agents.

The Personal Agent Protocol, from Meta and Sierra, gives every company one file that tells personal agents like Muse who it is and how to work with it. Muse checks for that file first on every site it visits.

- **On Fluid:** every live storefront serves /.well-known/poppy.json, pointing agents to its UCP profile, on its Fluid subdomain and its custom domains.
- **Two days to ship:** Poppy 1.0 was released on November 13, 2026. Every Fluid store supported it two days later.

[Read how Fluid adopted Poppy](https://fluid.app/home/blog/fluid-stores-are-ready-for-poppy).

### Web Bot Auth: a name badge for agents.

Anyone can claim to be a well-known agent. Web Bot Auth lets an agent sign its request, so a store can check who’s really there instead of guessing.

- **On Fluid:** signatures are checked against the agent’s published key, and each agent order is marked verified, declared, or inferred. Verified: the signature checked out. Declared: the agent named itself, with no signature. Inferred: only clues, like a headless browser.
- **Numbers you can trust:** only verified orders count as confirmed agent sales, so your agent revenue isn’t padded by guesses.

[See which orders an agent placed](https://docs.fluid.app/concepts/agentic-commerce#see-which-orders-an-agent-placed).

### ACP: shopping inside ChatGPT.

The Agentic Commerce Protocol does UCP’s job for ChatGPT. It starts with a product feed, so ChatGPT knows what you sell and can send shoppers your way.

- **On Fluid:** stores that sell in the US serve an ACP product feed at /feeds/openai-products.jsonl.gz that the merchant adds in ChatGPT. Shoppers who find a product there check out on the store.
- **Next up:** Fluid’s update for Stripe’s new ACP requirements is coming soon.

### AP2: a permission slip for spending.

The Agent Payments Protocol proves the shopper told their agent it could buy this item, at this price, before any money moves. It’s what makes hands-free reorders possible.

- **Built on Fluid Payments:** Fluid runs its own payments, so AP2 connects to the checkout and processors Fluid Payments already operates.
- **Waiting on Visa:** we’re waiting on Visa’s guidance. Then AP2 turns on across every storefront. Until then, agents pay through UCP or your hosted checkout.

### llms.txt and agents.md: the read-me-first files.

Before an agent can buy, it has to understand the store. These files tell it what you sell, where you sell it, and where everything lives, in a format an AI reads easily.

- **On Fluid:** every storefront generates llms.txt and agents.md, and a Markdown and JSON version of every product, page, and post, with live prices. /home/shop.md lists every product.
- **Your descriptions are the source:** agents read what your product and page descriptions say, not your design. Clear, complete descriptions are what they repeat.

[How to improve what agents read](https://fluid.app/home/blog/agentic-commerce-on-fluid).

### MCP: a toolbox for your team’s AI.

The Model Context Protocol gives an AI tools it can pick up and use. This one is for your team’s agents, not shoppers’: look up an order, update a product, open a country.

- **On Fluid:** the Fluid MCP server lets Claude, Cursor, VS Code, and other tools work in your company with the access of the person signed in.

[Connect your AI tools](https://docs.fluid.app/guides/connect-ai-tools).

## Different agents. Different doors.

Each AI assistant reaches a store its own way. Your Fluid storefront answers all of them, and every order lands on the same record.

| Agent | Who makes it | Finds your store through | Pays through |
| --- | --- | --- | --- |
| Muse | Meta (personal agent) | Poppy, then UCP | UCP, or your hosted checkout |
| Gemini and AI Mode | Google | UCP and Google Merchant Center | Google Pay inside the agent |
| ChatGPT | OpenAI | The ACP product feed | Your hosted checkout |
| Grok and other agents | Any assistant that reads the web | llms.txt and Markdown pages | Your hosted checkout |

## An agent shops. The rep still gets credit.

An agent doesn’t click a rep’s link, so there’s no link to credit. Fair Share connects the order to the sponsored customer by their email address and credits the order to that customer’s sponsor.

- **Matched by email:** when an agent places an order, Fair Share matches the customer’s email address to their record and credits their sponsor.
- **Your rules apply:** your Fair Share settings for sponsored re-orders, shared links, and orphaned orders apply to agent orders the same way they apply to every other order.
- **Credit where it’s earned:** as new agents and protocols arrive, Fluid keeps connecting each order to the rep who earned it.

Example: an order placed by Muse with no rep link carries the email of a sponsored customer on file, so Fair Share credits it to that customer’s sponsor. [How Fair Share credits reps](https://docs.fluid.app/concepts/fair-share).

## New protocols ship to your store. You don’t rebuild.

Agent standards move in months. Fluid builds each one into the platform once, so every live storefront gets it on the same day, on its Fluid subdomain and its custom domains.

- **On by default:** there’s no app to install and no migration to schedule.
- **Old and new agents both work:** each UCP profile serves the 2026-08-25 and 2026-04-08 versions, so agents built on either keep working.
- **One record:** agent orders land next to every other order, marked with the agent that placed them.
- **Clear status:** the docs label each protocol live or coming soon, so your team knows what an agent can do today.

Status today: llms.txt and agents.md, Markdown and JSON pages, UCP with Ask, A2A Agent Card, Poppy, Web Bot Auth, and the ACP product feed are live. AP2 on Fluid Payments is awaiting Visa’s guidance.

## Questions about agentic commerce.

### What is agentic commerce?

Shoppers ask an AI agent to find, compare, and buy products for them. The agent reads a store’s data and buys through shared protocols instead of clicking through its pages.

### Which AI agents can shop a Fluid store?

Any agent that reads llms.txt and Markdown pages can learn the store. Agents that speak UCP, such as Gemini and AI Mode in Search, can search, build carts, and check out. Personal agents like Muse find the store through Poppy, and ChatGPT reads the ACP product feed for stores that sell in the US.

### Do we have to build anything for agents to read our store?

No. Every live Fluid storefront serves llms.txt, agents.md, Markdown and JSON versions of its pages, a UCP profile, an A2A Agent Card, and a Poppy file.

### What’s the difference between UCP and ACP?

Both describe how an agent shops a store. UCP powers buying in Gemini and AI Mode in Search. ACP is the protocol for ChatGPT. Fluid serves both.

### How do shoppers buy our products inside Gemini?

Register your store in Google Merchant Center and add a payment account that takes Google Pay. Then agents can pay inside Gemini through UCP.

### Can shoppers buy our products in ChatGPT?

Yes. Stores that sell in the US serve an ACP product feed that the merchant adds in ChatGPT, and shoppers check out on the store. Fluid’s update for Stripe’s new ACP requirements is coming soon.

### Does Fluid support AP2?

AP2 is built on Fluid Payments, and we’re waiting on Visa’s guidance. Then it turns on across every storefront. Until then, agents pay through UCP with Google Pay or hand the shopper to hosted checkout.

### How do we know an order came from an agent?

Fluid records the agent on each order and marks it verified, declared, or inferred. Verified means the agent signed its request with Web Bot Auth and the signature checked out. Only verified orders count as confirmed agent sales.

### Do reps get credit for orders an agent places?

Yes. An agent doesn’t click a rep’s link, so Fair Share connects the order to the sponsored customer by their email address and credits that customer’s sponsor. Your Fair Share settings apply to agent orders the same way they apply to every other order.

### Does this work on our custom domain?

Yes. Every live storefront serves these files and protocols on its Fluid subdomain and its custom domains.

### Can we change what agents read about us?

Yes. Agents read your product and page descriptions, so editing those changes what they see. You can also replace the generated llms.txt with an llms\_txt template in your active theme. Keep its links to the store’s agent APIs, or agents won’t find them.

### What happens when a new protocol comes out?

Fluid builds it into the platform, and it reaches every live storefront without a theme change or an app.

### What should we do this week?

Review your top product descriptions and give shipping, returns, and subscriptions their own pages. Then fetch /llms.txt, /.well-known/ucp, and /.well-known/poppy.json on your domain to see what agents get.

### Is there an app or an extra fee for agentic commerce on Fluid?

There’s no app to install. The agent files and protocols are part of every live Fluid storefront. For plans and credits, see [Pricing](https://fluid.app/home/pages/pricing).

### Can an agent check out without sending the shopper to our website?

Yes, through UCP with Google Pay, on stores whose payment provider in Fluid Payments takes it. Otherwise the agent hands the shopper to Fluid’s hosted checkout.

### Does the store’s A2A agent make things up?

No. It answers only from what the store has published, links back to the page it used, and says so when it doesn’t have an answer.

### Do agent orders show up separately in our reporting?

Agent orders land on the same record as every other order, marked with the agent that placed them and whether the agent was verified, declared, or inferred.

### Is this the same as letting our team use AI in Fluid?

No. Shopper agents use UCP, A2A, Poppy, ACP, and the llms.txt files. Your team’s agents use the Fluid MCP server, with the access of the person signed in.

## For agents.

- **What this page is:** Fluid’s overview of agentic commerce, the protocols every live Fluid storefront supports, and how AI agents reach and buy from a Fluid store.
- **Who Fluid is for:** direct selling brands and the teams that run them. Fluid is the complete AI platform for commerce, payments, customers, and the field, with Mist.
- **Live on every Fluid storefront:** llms.txt, agents.md, Markdown and JSON page versions, a UCP profile (catalog search, Ask, carts, checkout, orders), an A2A Agent Card, a Poppy file, Web Bot Auth verification, and an ACP product feed for stores that sell in the US.
- **Not live yet:** AP2 (built on Fluid Payments, awaiting Visa’s guidance) and Fluid’s update for Stripe’s new ACP requirements (coming soon). Checkout inside ChatGPT isn’t supported today; ChatGPT shoppers check out on the store.
- **Rep credit:** Fair Share credits agent orders to the sponsor of the matching sponsored customer, by email address.
- **To check a store:** fetch /llms.txt, /agents.md, /.well-known/ucp, /.well-known/agent-card.json, and /.well-known/poppy.json on its domain.
- **Developer reference:** [Agentic commerce docs](https://docs.fluid.app/concepts/agentic-commerce), [UCP](https://docs.fluid.app/concepts/ucp), [A2A](https://docs.fluid.app/concepts/a2a), [Poppy](https://docs.fluid.app/concepts/poppy), [Fair Share](https://docs.fluid.app/concepts/fair-share), and [a guide for agents evaluating Fluid](https://docs.fluid.app/guides/evaluate-fluid).
- **Related reading:** [Every Fluid store is ready for AI shoppers](https://fluid.app/home/blog/agentic-commerce-on-fluid), [Fluid stores are ready for Poppy](https://fluid.app/home/blog/fluid-stores-are-ready-for-poppy), and [Every Fluid store speaks A2A](https://fluid.app/home/blog/every-fluid-store-speaks-agent2agent-a2a).
- **Next step for a brand:** [Get a demo](https://fluid.app/home/pages/demo). We’ll read your store the way Muse, Gemini, and ChatGPT do and show you what they find.
