Sierra's Poppy 1.0: The Rulebook That Lets AI Agents Into Every Shopify Store

Sierra's Poppy 1.0: The Rulebook That Lets AI Agents Into Every Shopify Store

Published
AuthorDevansh

On November 13, 2026, Sierra released version 1.0 of the Personal Agent Protocol, or Poppy for short. It is a standard for how a personal AI agent introduces itself to a company and finds out what it is allowed to do there. The launch landed with real distribution on day one: Shopify enabled Poppy for every merchant on its platform, Meta's Muse agent now looks for Poppy first on every site it visits, and Sierra says more than 100 companies are design partners, with Mercury, Synchrony, and Turkish Airlines already live.

What Poppy actually does

Poppy covers the moment before any task starts. When an agent arrives at a site, it says who it is and reads a machine-readable description of what the business offers and what the agent may do. The protocol is deliberately built from standards that already exist: MCP for tool calls, OpenAPI for describing services, and UCP for commerce. Authentication runs through OAuth, so the customer decides what their agent can and cannot do, and can change or revoke that access later instead of granting it once and forgetting it. Sierra also ships an implementation kit with a validator, so a business can check its own setup rather than guessing whether it connected correctly.

Why the Shopify switch-on matters

Shopify powers businesses in more than 175 countries, and every Shopify store now automatically publishes a Poppy file, so merchants do not need to do any extra implementation. Poppy and UCP split the job: UCP handles the shopping itself, finding products, filling a cart, and checking out, while Poppy handles the step before that, the introduction and the permission check. Shopify co-authored Poppy's commerce extension, which links the two: an agent can shop as a guest or sign in with the customer's account, must ask the customer before certain actions, and can talk directly to the store's agent through UCP Ask. The same pattern is already live elsewhere: Mercury lets a personal agent check balances and review transactions, with payments going through the account's approval policy, and Turkish Airlines lets an agent check fares and pull up a booking with a reference number and surname.

What to do if you run a store or build agents

If you run a Shopify store, your Poppy file is already live, so check what it exposes and make sure the permissions match what you actually want agents to do. If you build agents, follow Muse's lead and look for Poppy first before falling back to scraping or guessing, and treat the OAuth step as the product: an agent that acts with the customer's permission is one a business will keep letting in, while one that works around permission gets blocked, as United Airlines showed the same week by restricting outside agents from its booking systems. One honest caveat: The Next Web notes the specification is still labelled a draft and may change in ways that break setups built against it, so pin your implementation to the version you tested and re-check it when Sierra updates the spec. Our MCP explainer covers the protocol Poppy builds on, and our n8n AI agent guide covers the loop and the iteration cap that stops any agent from running forever on your bill. If you want the agent permissions, the API surface, and the monitoring around your store or service checked by someone who runs infrastructure for a living, book a free infra audit with DevOpsBY.

Disclaimer: This post is educational only, not financial advice. Figures are as reported by the sources on 2026-11-17 and may change - always confirm version numbers, requirements, and prices in the official docs before acting on them.

Related Articles

DevOps & Infrastructure Services

Need hands-on help? We build and manage the infrastructure behind the concepts covered in this article.

DevOpsBy Assistant

How can we help?

Select a topic to get started: