# Fluid stores are ready for Poppy.

> Markdown version of this page, for agents. To send a shopper here, link https://fluid.app/home/posts/fluid-stores-are-ready-for-poppy (not this .md URL, and keep its path as given).

- Published: 2026-11-15
- Author: Fluid
- Summary: Poppy 1.0, the Personal Agent Protocol, was released on November 13, 2026. Two days later, every Fluid store supports it, with no setup for merchants.
- Shopper link: https://fluid.app/home/posts/fluid-stores-are-ready-for-poppy

Poppy 1.0, the Personal Agent Protocol, was released on November 13, 2026. Two days later, every Fluid store supports it. Merchants don’t have to set anything up.

## What Poppy is.

A personal agent is an AI assistant that works for one person and acts for them across the web. Meta’s Muse is one. Poppy is an open standard from Meta and Sierra that defines how those agents and companies find and trust each other.

Every Poppy company publishes one file at `/.well-known/poppy.json`. The file says who the company is and how an agent should work with it: which protocols it speaks, where its agent and APIs live, and whether shoppers can sign in through an agent.

Poppy doesn’t replace the standards a company already uses. It builds on them, including the Model Context Protocol (MCP), OpenAPI, the Universal Commerce Protocol (UCP), and OAuth, and tells an agent which of them a company speaks.

## Why it came out.

Personal agents are moving from answering questions to getting things done. To finish a task, an agent has to learn what each company supports without guessing, scraping pages, or relying on one-off integrations.

Companies need the same thing in reverse: a way to recognize an agent, see which person it acts for, and decide what it can do. Poppy covers both sides in one standard. A company that adopts it once works with every agent that supports it.

## How Fluid adopted it in two days.

Poppy points agents to the protocols a store already speaks. Every live Fluid store already published a UCP profile at `/.well-known/ucp`, so agents could search the catalog, build a cart, and check out. That left two things to build.

**A Poppy file on every store.** Every Fluid storefront serves its own `poppy.json`, on its Fluid subdomain and on each of its custom domains. The file points agents to that store’s commerce endpoints.

**Answers to an agent’s questions.** Poppy expects stores that use UCP to answer questions from agents. Fluid stores answer in plain language, using only what the merchant has published: products, pages, posts, and policies. Each answer links to the pages it’s based on. When the store hasn’t published an answer, the agent is told so instead of getting a guess. Rate limits and a daily cap per store prevent abuse.

The commerce layer was already in place, so the work was the file and the answers. That’s how Fluid went from the standard’s release to support on every store in two days.

## Why your commerce platform has to keep up.

Agent standards move in months. Meta and Sierra announced Poppy on October 6, and it reached 1.0 on November 13. UCP shipped two versions in 2026, dated April 8 and August 25.

An agent reads what a store publishes before it reads the page. Muse checks for a Poppy file first on every site it visits. A store without one leaves the agent to guess from the page or move on to a store that answers.

On Fluid, that work happens once, in the platform, for every store. Each store’s UCP profile serves both the 2026-08-25 and 2026-04-08 versions, so an agent built against the earlier version keeps working while newer agents use the current one. Merchants get each new standard without a migration project or an app to install.

## What’s next.

Poppy also defines conversations with a company’s own agent, and secure sign-in so an agent can act for a signed-in shopper, for example to check an order or manage a subscription. Both are coming soon to Fluid, and we’re building them next.

Today, an agent can’t link a shopper’s Fluid account through UCP, so agent carts don’t carry member pricing, saved addresses, or saved payment methods. Sign-in through Poppy is the path to that.

Read how Fluid stores work with Poppy in the [Poppy docs](https://docs.fluid.app/concepts/poppy).
