Sierra published version 1.0 of the Personal Agent Protocol, nicknamed Poppy, on November 13. Sierra says the standard is already switched on for every Shopify merchant and for everyone who uses Muse, Meta’s AI agent.

Poppy answers a question that gets harder as consumers hand errands to software: what happens when an assistant acting for a person shows up at a company’s front door? The protocol lets a company say what it offers and what an agent may do there. The customer, not the agent, decides which permissions to grant, and can change them later. Authentication runs through OAuth.

Sierra’s announcement says Poppy is built largely from parts that already exist: MCP, OpenAPI, and UCP, the Universal Commerce Protocol. That choice lowers the cost of adoption. A company with an API description and an MCP server is most of the way there, and Sierra says its implementation kit includes a validator for checking the work. The first draft appeared about five weeks before the release, and the 1.0 text reflects what design partners learned testing it against real sites, APIs, and agents.

Three changes stand out. Adoption can be phased: a company implements the basics first and layers on capabilities later. Companies can send guidance to a personal agent and collect feedback from it. And extensions let an industry build on the core without altering it. The first one, a commerce extension, was co-written with Shopify.

The Shopify piece is the largest distribution event in the announcement. Shopify stores operate in more than 175 countries, and each one now publishes a Poppy file automatically, so merchants need no extra work. Sierra describes the division of labor with UCP this way: UCP runs the shopping itself, while Poppy covers the moment before, when an agent arrives, identifies itself, and learns its limits. The commerce extension lets an agent browse anonymously or log in under the customer’s account, and it forces the agent to ask before certain actions.

Muse supplies the demand side. Sierra says Meta’s agent looks for a Poppy file before anything else, whatever site it lands on. A protocol needs both halves to matter, and here one company’s agent and one platform’s merchants are covered on day one.

The partner list grew from eight founding names (Meta, Genesys, Instinct, NiCE, Rocket, Shopify, Stripe, and Walmart) to more than 100 with 60 additions, including Delta Air Lines, Intuit, Salesforce, SoFi, Twilio, and Zoom. Three partners are live. Mercury lets customers ask an agent to check balances, categorize spending, or start a payment, with the bank’s own approval policy still gating the request. Turkish Airlines lets agents check fares, flight status, and stopovers, and members approve business-class upgrades before paying. Synchrony is still exploring how agents could surface financing across its network of more than 500,000 merchant locations.

All of this comes from Sierra’s own post. Sierra announced the standard, so the adoption figures are self-reported, and the post offers no usage numbers for Muse or for any live partner. “Design partner” also says nothing about how much of a company’s catalog or account surface agents can reach.

The stake is who writes the rules of agent commerce. If a company’s login, permissions, and approval prompts are defined by a protocol that Sierra published and Meta’s agent already honors, rivals will either adopt it or push a competing one. Teams that run a storefront, booking flow, or account portal should check what a Poppy file would expose to agents before the first customer’s assistant asks for it.

Reported from Sierra’s blog post “Releasing Personal Agent Protocol 1.0,” by Bret Taylor and Clay Bavor, published November 13, 2026.