Poppy 1.0: your online shop now talks to AI agents. What the file says and what is missing

A young man with dark hair and a beard in a black knit sweater stands at a pale green wall in front of a wooden key rack with six brass hooks. Only one hook holds a small glowing orb on a thread, and he touches the thread. In his other hand he holds a blank sheet of tracing paper. Next to him a card: 16 of 65 shops checked already publish a Poppy file for AI agents, our own measurement on November 17, 2026. Direct-to-consumer brands on Shopify 16 of 20, large retailers and travel providers 0 of 35, permissions for agents per file: 1. Poppy 1.0 by Sierra, switched on for all Shopify merchants since November 13

TL;DR. On November 13, Sierra released version 1.0 of the Personal Agent Protocol, Poppy for short. It defines how a personal AI agent approaches a company, identifies itself and learns what it is allowed to do there. Shopify switched it on for all merchants the same day, and Meta’s agent Muse looks for it first on every site. On November 17 we checked 65 shops selling in Germany: 16 already have the file, all of them through Shopify, none of the large retailers. Many small brands are open to AI agents sooner than the big players, often without knowing it. Their file allows exactly one thing: preparing a purchase. What an agent should not do is written nowhere.

What is new

Until now an AI agent moves around the web like a visitor without an ID: it reads pages, clicks buttons and hopes nothing goes wrong. Poppy gives it a proper entrance. Every company places a small file at a fixed address, /.well-known/poppy.json. It says who the company is, which permissions an agent can request, which interfaces it should use and which tasks the company deliberately does not offer.

Three things make version 1.0 notable. Every permission carries a hint whether it only reads, changes something reversibly or does something irreversible, and whether personal data is involved. The customer signs in with the company through standard OAuth and grants the agent only what they want. And the specification requires agents to treat text from the company as data, never as instructions, and never to pass access keys into the language model.

According to Sierra, more than 100 design partners back the standard, including Salesforce, Cisco, Delta Air Lines and Zoom. Live implementations include the bank Mercury, where an agent can only start transfers through the account’s approval rules, and Turkish Airlines.

Our test: who has the file today

On the morning of November 17 we checked 35 large retailers and travel providers and 30 well-known direct-to-consumer brands for a valid Poppy file at that address. We also read each homepage to see whether the shop runs on Shopify.

Poppy file present? One dot per site checked

Poppy file presentShopify with its own front end, no fileno filerequest blocked or unreachable

Our own measurement on November 17, 2026, simple request for /.well-known/poppy.json and the homepage, without a browser. Our own selection, not a sample.

The picture is clear. Wherever the file exists, Shopify wrote it. Of the 20 Shopify shops on our list, 16 have the file; the other 4 run their own front end in front of Shopify. On the 28 reachable sites without Shopify we found not a single one, including the large retailers. 13 of the 35 big players turned our request away at the door.

What the automatic file contains

All 16 files are identical. Shopify generated them for every shop from the same template, and the merchant entered nothing.

The six building blocks of a Poppy file, as Shopify ships it today

Content of the 16 files found on November 17, 2026, all identical. Building blocks as in section 3.1 of specification 1.0.

For shopping, that is enough. According to the description in the file, the buyer completes the purchase, and Shopify’s extension requires the agent to ask before certain steps. Everything after that, such as order status, returns or complaints, the file does not know. An agent asked to register a return ends up back on the normal website and has to click its way through.

The catch

  • One big agent is reading. So far only Meta’s Muse has been announced. OpenAI, Google, Anthropic and Amazon are not on Sierra’s list. In January, Google and Shopify presented their own shopping standard, UCP, which Poppy builds on.
  • One vendor drives the standard. Sierra itself sells customer service agents to companies. There is no neutral body.
  • Not everyone wants the agents. On November 11, United Airlines restricted third-party booking agents. It cites exposed login details, unintended purchases and spent miles, but according to reports also the worry of getting a new middleman.
  • A file is not an ID. The specification says so itself: nothing in the file confirms that the domain really belongs to the company. A lookalike domain passes every check.
  • Our test is small. Our own selection of 65 sites, a simple request without a browser. A site that blocks scripts does not necessarily block every agent.

What this means for mid-sized companies

If your shop runs on Shopify, it has been reachable for AI agents since Friday without you changing a line. That is more an opportunity than a risk: the agent can only prepare a purchase, the customer has to complete it. If you work with Shopware, Magento, SAP Commerce or your own system, you have nothing yet. For you, now is the time to decide before your customers do.

For manufacturers with a B2B portal the question is the same, just later. When buyers let their agents check delivery times and place repeat orders, the winner is whoever offers them a clear entrance with clear limits. The standard is built for that: mark what is irreversible, state what is excluded, run everything through the customer’s sign-in.

What you should do now

  1. Check. Open your-domain.com/.well-known/poppy.json in your browser. If you see a short text in curly braces, you are in.
  2. Decide what agents may do. Product search and cart, yes? Order status? Returns? What never, for example cancellation or changing bank details?
  3. Write down the limits. The specification provides a list of tasks that are not available to agents, each with another way to do them. That saves customers and agents the search.
  4. Tie anything irreversible to a human. Everything that moves money or changes data needs the customer’s confirmation. That is how Mercury and Turkish Airlines do it.
  5. Count. Check your server logs for how often agents already visit and whether your bot protection turns them away without you wanting it to.
  6. Without Shopify: wait, but plan. As long as only one big agent reads the standard, a rebuild does not pay off. Still keep your interfaces for stock, prices and order status clean. Every one of these standards builds on them.

Agents will not ask whether your shop is ready. Whether they find a clear entrance with you or click their way through the site is being decided right now. If you want to work out what agents should be allowed to do with you, we are happy to sit down with you.

A conversation worth having, even without an engagement.

20 minutes, no obligation. Usually a personal reply the same working day.