# Every Fluid store is ready for AI shoppers.

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

- Published: 2026-11-19
- Author: Fluid
- Summary: Shoppers are asking AI agents to buy for them. Every live Fluid storefront already speaks the protocols those agents use, from llms.txt to UCP, A2A, Poppy, Web Bot Auth, and ACP, with AP2 next.
- Shopper link: https://www.fluid.app/home/blog/agentic-commerce-on-fluid

A shopper asks Meta’s Muse to find the best protein powder. She doesn’t open a browser tab. The agent remembers she bought from your store before, reads what you sell, asks whether the vanilla is dairy-free, builds a cart, and checks with her before it buys.

That trip only works if your store speaks the agent’s language. Every live Fluid storefront already does. This post explains each protocol in plain terms, what Fluid serves for it today, and where your team can make it better.

## Why this matters now.

More than 25% of Muse’s weekly users already shop through the agent, Muse reached 10 million users in the US and Canada in six weeks, and the average agent purchase is over $200, according to Meta’s Q3 2026 earnings call. The Gemini app passed 1 billion monthly users on August 11, 2026, and AI Mode in Google Search passed 1 billion monthly users on its own.

An agent doesn’t look at your homepage design. It reads your store’s data in agreed formats called protocols. If an agent can’t read and buy from your store, that shopper never sees you.

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

Before an agent can buy, it has to understand the store. Every Fluid storefront generates an `/llms.txt`: what it sells, the countries, currencies, and languages it serves, its collections, pages, and policies, and links to its agent APIs. `/agents.md` serves the same document as Markdown.

Add `.md` to any product, collection, category, page, or blog post URL and you get a Markdown version with live prices. Add `.json` for the same data as JSON. `/home/shop.md` lists every product.

**How to make it better.** These files are built from your product and page descriptions, so complete, plain-language descriptions are what agents read. You can also replace the generated llms.txt by publishing an `llms_txt` template in your active theme. Keep its links to the store’s agent APIs, or agents won’t find them. [See what every storefront serves](https://docs.fluid.app/concepts/agentic-commerce).

## UCP: the rules for shopping.

The Universal Commerce Protocol gives every store the same steps: find it, put it in the cart, pay, and get the order. It powers buying inside Gemini and AI Mode in Search.

Every live Fluid storefront publishes a UCP profile at `/.well-known/ucp`, with catalog search, Ask, carts, checkout, and orders. An agent can pay in its own interface with Google Pay where the store’s payment provider in Fluid Payments takes it. To turn that on, register your store in Google Merchant Center and add a payment account that takes Google Pay. [Read the UCP docs](https://docs.fluid.app/concepts/ucp).

## A2A: how agents talk to each other.

Agent2Agent lets a shopper’s agent ask your store’s agent a question, like whether a product is vegan or when it ships. Each Fluid storefront serves an Agent Card at `/.well-known/agent-card.json`, and your store’s agent answers only from what you’ve published, with a link back to the page. [Read the A2A launch post](https://fluid.app/home/blog/every-fluid-store-speaks-agent2agent-a2a) or [the A2A docs](https://docs.fluid.app/concepts/a2a).

## Poppy: a signpost for personal agents.

The Personal Agent Protocol tells personal agents like Muse who a company is and how to work with it. Every Fluid storefront publishes `/.well-known/poppy.json`, which points agents to its UCP profile. [Read how Fluid adopted Poppy](https://fluid.app/home/blog/fluid-stores-are-ready-for-poppy) or [the Poppy docs](https://docs.fluid.app/concepts/poppy).

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

An agent can sign its checkout request so the store knows which agent is really there. Fluid checks the signature against the agent’s published key and labels each agent order verified, declared, or inferred. Only verified orders count as confirmed agent sales. [See which orders an agent placed](https://docs.fluid.app/concepts/agentic-commerce#see-which-orders-an-agent-placed).

## ACP: shopping in ChatGPT.

The Agentic Commerce Protocol does UCP’s job for ChatGPT. ACP is live on Fluid: stores that sell in the US serve a product feed at `/feeds/openai-products.jsonl.gz` that the merchant adds in ChatGPT, and shoppers who find a product there check out on the store. Fluid’s update for Stripe’s new ACP requirements is coming soon.

## AP2: a permission slip for spending.

The Agent Payments Protocol proves a shopper told their agent it could buy a specific item, at a specific price, before any money moves. It’s what makes hands-free reorders possible. Because Fluid runs its own payments, AP2 connects to the checkout and processors Fluid Payments already operates. We’re waiting on Visa’s guidance, then it turns on across every storefront. Until then, an agent pays through UCP with Google Pay or hands the shopper to hosted checkout.

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

The Model Context Protocol is for your own AI, not shoppers’. 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).

## New protocols reach every store at once.

Fluid serves the agent layer from the platform, not from your theme. When Fluid adds a protocol, it reaches every live storefront on the same day, on its Fluid subdomain and its custom domains. You don’t install an app or schedule a migration.

## What to do this week.

- **Review your top product descriptions.** Ingredients, sizes, and who it’s for, written in full sentences.
- **Give your policies their own pages.** Shipping, returns, and subscriptions, with the real windows and countries.
- **Check your store.** Fetch `/llms.txt`, `/.well-known/ucp`, and `/.well-known/poppy.json` on your domain. The [agentic commerce docs](https://docs.fluid.app/concepts/agentic-commerce) list the commands.

Bring us your store. We’ll show you what agents see. [Get a demo](https://fluid.app/home/pages/demo) or [see how agentic commerce works on Fluid](https://fluid.app/home/pages/agentic-commerce).
