Poppy 1.0, the first stable version of Sierra’s Personal Agent Protocol, has been available since 13 November 2026. The protocol defines how personal AI agents deal with companies: who the agent is, on whose behalf it acts and what it is allowed to do with a given business. At the same time, Shopify switched Poppy on for every merchant on its platform, and according to Sierra, Meta’s agent Muse now looks for a Poppy file first on every website it visits. A draft that was only introduced in early October has turned into a standard with serious reach.
Poppy 1.0: What the Personal Agent Protocol covers
Sierra describes Poppy as an open standard for how personal agents interact with companies through their business agents, websites and APIs. According to Sierra’s announcement of version 1.0, the protocol was introduced in October together with initial design partners including Meta, Genesys, Instinct, NiCE, Rocket, Shopify, Stripe and Walmart. A first draft followed a few days later.
Technically, Poppy does not reinvent much. Sierra says it is largely built on existing standards: the Model Context Protocol (MCP), OpenAPI and the Universal Commerce Protocol (UCP). Sign-in runs through OAuth, so customers decide what their personal agent may and may not do at a company and can change those permissions later.
The idea is simple. When an agent visits a website on behalf of a person, it should not stumble through forms like a scraper. Instead, it finds a machine-readable description of what the company offers, how the agent identifies itself and which actions are allowed. For companies, it is an attempt to keep control over this new access path instead of either blocking agents or letting them through unchecked.
What changed since the draft
Sierra says version 1.0 reflects about five weeks of design partners testing the drafts against real websites, APIs and agents. The company lists four changes since the first draft:
- Companies can adopt the protocol in stages, starting with the basics and adding capabilities over time.
- The way the protocol uses existing standards has been refined.
- Companies can give agents more guidance and collect feedback from them.
- Extensions now let industries build on the core protocol without changing it. The first is a commerce extension co-authored by Shopify.
For the launch, Sierra provides an implementation kit that walks companies through setup and includes a validator. According to the company, any business can now implement Poppy on its own.
The entry point is defined in the version 1.0 specification: a company publishes a JSON document at /.well-known/poppy.json on its domain, served over HTTPS. It tells a personal agent how to start a session and sign in, and which APIs and which company agent the business offers. For web developers, this is a familiar pattern, similar to other files in the .well-known directory.
Shopify: every store now publishes a Poppy file automatically
The biggest impact is likely to come from Shopify. According to Sierra, every Shopify store supports the Universal Commerce Protocol by default, and every store now automatically publishes a Poppy file. Merchants do not have to set anything up. According to Sierra, Shopify powers businesses in more than 175 countries.
Sierra describes the division of labour like this: UCP handles the shopping itself, meaning finding products, filling a cart and checking out. Poppy handles the step before that, when an agent arrives at a store, says who it is and learns what it is allowed to do. The commerce extension co-authored by Shopify connects the two. It lets an agent shop as a guest or sign in with the customer’s account, and it requires the agent to ask the customer before taking certain actions. It also connects to UCP Ask, so a shopper’s agent can talk directly to the store’s agent.
The background shows how hard agents are pushing into e-commerce. Shopify had already opened its checkout to AI shopping agents, as we covered in our piece on Shopify’s checkout for AI agents. Poppy adds the question of who is knocking on the door in the first place, and with which rights.
Meta Muse and the first live partners
On the agent side, Meta is the most important partner. According to Sierra, Poppy is on for everyone who uses Muse, Meta’s AI agent, and Muse looks for Poppy first on every site it visits. For companies, that is a practical argument: if you offer Poppy, this agent will prefer to talk to you through the structured interface.
Sierra says several design partners are already live:
- Mercury: personal agents can check balances, review transactions, categorise spending and keep budgets and receipts up to date. They can also initiate payments and transfers. According to Sierra, Mercury routes such requests through the account’s approval policy before anything is sent.
- Synchrony: the company is exploring how an agent could take financing and rewards offers into account while shopping. Sierra explicitly describes this as ongoing work.
- Turkish Airlines: agents can check fares, flight status and stopovers and pull up a booking with a reference number and surname. Members of the frequent flyer programme can have their agent look for business-class upgrades, which they approve before paying.
On top of that, Sierra says 60 new companies have joined as design partners, bringing the total to more than 100. The list includes Checkout.com, Cisco, Delta Air Lines, Hyatt, Intuit, Salesforce, Twilio, Wix and Zoom, among others. Being a design partner does not mean these companies already use Poppy in production. Based on the announcement, only the examples above are live so far.
Analysis: control, approvals and open questions
Poppy is one of several attempts to organise the relationship between AI agents and businesses. Only days ago, OpenAI used ChatGPT Wallet to define how its agents pay: with payment tokens instead of real card details and a biometric approval for every purchase. Poppy starts one layer earlier, with identity, permissions and discovery.
It is a good sign that the protocol relies on established building blocks such as OAuth, OpenAPI and MCP and explicitly provides for human approvals. If you want to understand how these pieces fit together in agent systems, our explainer on MCP, memory, skills and hooks covers the basics.
Several questions remain open. First, Poppy is a standard driven by Sierra, even if it is described as open; how independent its future development will be is not settled. Second, the number of design partners says little about real adoption beyond Shopify. Third, every automatically published interface shifts responsibility: merchants should check what their store says about itself and which actions an agent can actually trigger. Finally, the Muse integration covers Meta users for now; whether other large agent providers follow is open.
What merchants and developers should do now
- Shopify merchants: no setup is required. It still makes sense to open the automatically published file once and check that the store name and details are correct and that guest checkout works.
- Companies with their own APIs: Sierra’s implementation kit and validator are the starting point. Because the specification may still evolve, rolling it out in small steps is the safer route.
- Security and operations: approval rules, logging and permissions for agent access deserve the same rigour as any other API client.
Bottom line
Poppy 1.0 is less a technical revolution than an attempt to bring order: it bundles familiar standards into one protocol through which personal agents identify themselves to companies and learn what they are allowed to do. With Shopify and Meta Muse, it has reach from day one. Whether it becomes a widely accepted industry standard depends on how stable the specification stays and whether other agent providers come on board.




