Personal Agent Protocol (Poppy) on Fluid stores

The Personal Agent Protocol (Poppy) is an open standard for how a personal agent, an AI assistant that acts for one person, works with a company. A company publishes one document, /.well-known/poppy.json. It says who the company is and which protocols, APIs and agents a personal agent can use there. Personal agents such as Meta’s Muse read it first on every site they visit. Every live Fluid storefront serves a Poppy 1.0 document on its own host, with no setup.

What a Fluid store publishes

curl "https://<store>/.well-known/poppy.json"

{
  "protocol_version": "1.0",
  "organization": {
    "name": "Juniper & Oak",
    "domain": "shop.juniperandoak.com",
    "logo_uri": "https://cdn.juniperandoak.com/logo.png"
  },
  "agent": {
    "protocols": [
      {
        "type": "ucp",
        "endpoint": "https://shop.juniperandoak.com/.well-known/ucp",
        "description": "Search Juniper & Oak's catalog, ask about its products and policies, build carts and check out."
      }
    ]
  },
  "web": {},
  "extensions": { "ucp": [ { "version": "1" } ] }
}

Field	What Fluid serves
`organization.domain`	The host that served the document. Poppy requires it to match, so a store answers with its own subdomain on `fluid.app` and with each custom domain on that domain.
`organization.logo_uri`	The company’s logo, when it’s served over HTTPS.
`agent.protocols`	One `ucp` entry pointing to the store’s UCP profile on the same host. Through it, an agent searches the catalog, asks questions, builds carts and checks out.
`extensions.ucp`	Poppy’s UCP extension, version 1. It requires the UCP profile to offer Ask (`dev.ucp.common.ask`), which every Fluid store does. See Ask the store a question.
`web`	Empty. Agents browse the store’s website as any visitor would.

The document is served as JSON with a five-minute public cache and an ETag, and any origin can read it. When the storefront is turned off, or the company’s account is paused for billing, the path answers 404.

How a personal agent uses it

The agent fetches https://<store>/.well-known/poppy.json and checks organization.domain against the host.
It follows the ucp entry to /.well-known/ucp, which lists the store’s UCP versions and capabilities.
It answers the person’s questions with UCP Ask, finds products with catalog search, and builds a cart and checks out with UCP, as described in Universal Commerce Protocol.

What isn’t available yet

Shopper sign-in. The document has no auth block, so a personal agent can’t sign a shopper in to their account on the store. Agents shop as guests: no member pricing, saved addresses, order history or subscriptions.
Conversations with the store’s agent. There’s no poppy entry in agent.protocols yet, so agents use one-off Ask questions rather than Poppy conversations.
Excluded tasks and feedback. The document has no tasks endpoint.

To reach the same store through the Agent2Agent (A2A) protocol instead, see A2A.

Get started

Sites

Mist apps

Core concepts

Guides

Guided setup

Storefront guides

SDKs

Portal & Widgets

Personal Agent Protocol (Poppy) on Fluid stores

What a Fluid store publishes

How a personal agent uses it

What isn’t available yet