# Every Fluid store speaks Agent2Agent (A2A).

> Markdown version of this page, for agents. To send a shopper here, link https://www.fluid.app/home/posts/every-fluid-store-speaks-agent2agent-a2a (not this .md URL, and keep its path as given).

- Published: 2026-11-15
- Author: Fluid
- Summary: Shoppers are starting to send their assistants to do the asking. As of today, every Fluid store has an agent that answers for it, in the merchant’s own published words, with a link back to the page.
- Shopper link: https://www.fluid.app/home/posts/every-fluid-store-speaks-agent2agent-a2a

A shopper is on the couch at 10:40 on a Tuesday night. She doesn’t open your website. She asks her assistant for a moisturizer for sensitive skin and tells it to come back with one pick.

The assistant has a short list of stores and three questions. Is this one fragrance-free? Does it ship to her? Can she send it back if her skin reacts? The store that answers all three in seconds makes the shortlist. The store that makes the assistant dig through pages and guess is easy to skip.

As of today, every Fluid store answers for itself. Each storefront runs its own Agent2Agent (A2A) agent, and merchants don’t have to set anything up.

## Your store gets a voice.

A2A is the open standard that lets one AI agent find another, see what it can do, and send it a message. Your store’s agent is the one on the other end. It knows your products, pages, posts, categories, and collections, and it answers in plain language.

- “Is this one fragrance-free?”
- “What’s your return policy?”
- “Does the starter kit come with everything a beginner needs?”
- “Which of these is vegan?”

When a question is about specific items, the assistant attaches their product IDs, so the answer is about exactly what the shopper is looking at.

## Your words, your pages, your traffic.

The agent answers only from what you’ve published. It doesn’t borrow from a reseller listing, a forum thread, or its own imagination. Each reply links to the pages it’s based on, so the assistant can hand the shopper straight to your product page or your policy.

You decide what your store says by deciding what you publish.

## What your store’s agent reads.

The answers come from the description and body of each storefront resource you publish: products, pages, posts, categories, collections, and the rest. Whatever you write there is what an assistant hears.

That makes your storefront copy your answer data. A few places to start:

- **Products.** Put ingredients, sizes, materials, and who the product is for in the description, in full sentences. “Fragrance-free” in an image doesn’t answer anyone. “This moisturizer has no added fragrance” does.
- **Policies.** Give shipping, returns, and subscriptions their own pages, with the actual windows, countries, and steps written out.
- **Categories and collections.** Say what belongs in each one and who it’s for, so the agent can point a shopper to the right group.
- **Posts.** How-to guides and routines answer the “how do I use it” questions before a shopper has to ask a rep.

Copy that answers a shopper on your site answers an assistant too. One edit improves both.

## Every “I don’t know” is a page to write.

When your store hasn’t published an answer, the agent says so. It doesn’t guess, and it doesn’t invent a return window. That protects the shopper, and it gives you a to-do list: a question your store couldn’t answer is a question an assistant just asked on someone’s behalf. Add the answer to the right description or page, and the next assistant that asks gets it.

## Found. Asked. Bought.

Three agent protocols cover the shopper’s path, and every Fluid store speaks all three.

- **Found.** Personal agents like Meta’s Muse discover your store through the Personal Agent Protocol (Poppy). [Read how Fluid adopted Poppy](https://fluid.app/home/blog/fluid-stores-are-ready-for-poppy).
- **Asked.** Any A2A agent reads your store’s Agent Card at `/.well-known/agent-card.json` and asks your store’s agent its questions.
- **Bought.** Agents that are ready to buy use the Universal Commerce Protocol (UCP) to search, build carts, and check out.

Fluid builds each standard into the platform once, so every store gets it on the same day, on its Fluid subdomain and on each of its custom domains. You don’t install an app or schedule a migration.

## A tenth of a cent, or less.

An answer costs less than $0.001 on average. That comes from how Fluid built the answer engine: it reads your published storefront content directly, so each question takes a small, focused amount of work instead of a long search.

A2A questions also share the same rate limits and daily cap per store as Fluid’s other agent features, so automated traffic can’t run up your costs.

## Where A2A comes from.

Google announced A2A in April 2025 with more than 50 technology partners. In June 2025, it moved to the Linux Foundation, so no single company controls it, and more than 100 companies supported it by then. It runs on HTTP and JSON-RPC, standards the web already uses.

Bring us the question your customers ask most. We’ll show you what your store’s agent says.

## For developers.

The Agent Card, message format, and error handling are documented in the [A2A docs](https://docs.fluid.app/concepts/a2a).
