Products#MCP#Ecommerce

Sierra releases Personal Agent Protocol 1.0, on for every Shopify merchant

Sierra released Personal Agent Protocol 1.0 on November 13: an open agent protocol on MCP, OpenAPI and UCP, with Shopify and three launch partners live.

Sierra announcement banner reading Releasing Personal Agent Protocol 1.0 over a blurred field of orange poppies

Sierra shipped version 1.0 of the Personal Agent Protocol — Poppy for short — on November 13, 2026: an open specification for how a customer’s AI agent connects to a company’s website, APIs and business agent, published at personalagentprotocol.org together with an implementation kit and a validator. Per Sierra’s announcement the same day, Shopify has enabled Poppy for every merchant on its platform, Mercury, Synchrony and Turkish Airlines are live, and the design-partner roster now tops 100 companies.

Key points

  • Poppy v1.0 lives at personalagentprotocol.org and is built largely from existing standards — MCP, OpenAPI and UCP — with OAuth sign-in and the customer in control of what agents may do.
  • Per Sierra’s blog, every Shopify store now publishes a Poppy file automatically, so merchants do no extra implementation work.
  • Meta’s AI agent Muse looks for Poppy first on every site it visits; Mercury, Synchrony and Turkish Airlines are live, and 60 new design partners bring the total past 100.

Background

Poppy is a month old. On October 6, Meta and Sierra introduced the Personal Agent Protocol with an initial group of design partners — Meta, Genesys, Instinct, NiCE, Rocket, Shopify, Stripe and Walmart — and on October 9 they published the first draft alongside 35 more partners, a list that included Bank of America, OpenAI, Visa and United Airlines. By Sierra’s account, version 1.0 reflects five weeks of those partners testing the drafts against real websites, APIs and agents.

The problem it targets is easy to recognize. Companies facing AI agents have had two options: wall them out, as Amazon does with Muse (we covered that standoff, and Walmart’s counter-moving Agent Gateway, in an earlier entry), or let an agent sign in as the user and inherit every permission that account holds. The protocol’s own site diagrams both extremes — blocked at the door, or full access after sign-in — and positions Poppy as the middle path: the agent identifies itself, the company decides what it may do, and the customer approves the sensitive steps.

The facts

Version 1.0 ships three things. The specification itself defines discovery: a company publishes a /.well-known/poppy.json file, and sign-in runs over OAuth with scopes, token revocation and sessions. Sierra’s own wording on permissions: with authentication through OAuth, “customers control what personal agents can and can’t do, and can manage their access over time.” The implementation kit has two parts — a coding-agent skill called implement-personal-agent-protocol that walks an agent through surveying a company’s systems, writing a design and building in milestones, and a validator that acts as a test personal agent against the finished deployment. The spec page itself, meanwhile, is still labeled Draft 1.0.

The Shopify piece is the biggest single deployment. Per Sierra’s blog, every Shopify store already speaks UCP by default; each store now also publishes a Poppy file automatically, with no extra work for merchants. The division of labor is explicit — UCP handles the shopping itself (finding products, filling a cart, checkout), while Poppy handles what happens before that: an agent arriving at a store, saying who it is, and learning what it’s allowed to do. The commerce extension Shopify co-authored 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 connects to UCP Ask so the shopper’s agent can talk to the store’s agent directly. This follows Shopify opening its billion-listing catalog to any AI agent in October.

The first three live partners split the work sensibly:

PartnerLive nowBoundaries
MercuryCheck balances, review transactions, categorize spending, keep budgets and receipts currentPayments and transfers must pass the account’s approval policy
SynchronyBring financing and offers into agent-led shoppingStill exploring
Turkish AirlinesCheck fares, flight status, stopovers; pull up a booking with reference number and surnameUpgrades require customer approval; in-conversation purchase in development

On ecosystem numbers: Sierra announced 60 new design partners, bringing the total to more than 100 — the list includes Affirm, Delta Air Lines, Intuit, Salesforce, Wayfair, Wix and Zoom. As for Muse, Sierra says Poppy is now on for everyone who uses it, and that Muse — Meta’s AI agent, which drew more than 3.4 million downloads in under three weeks — automatically looks for Poppy first on every site it visits.

What others say

Confirmation from Meta’s side is indirect: Meta for Business’s October post confirms the protocol is developed by Meta and Sierra together, and that Muse is Meta’s product, but Meta has made no separate statement on 1.0 as of press time. The partners’ own descriptions are measured — Mercury conditions payments on its approval policy, Synchrony calls the shopping scenario an exploration, and Turkish Airlines admits in-conversation purchase is still in development. No independent media analysis of the 1.0 release had surfaced by November 14, either: everything here about launch scope and permissions traces to Sierra’s and personalagentprotocol.org’s own descriptions, and shopify.dev’s UCP documentation didn’t mention Poppy when we checked on November 14 — so the “every merchant” claim remains Sierra’s framing, not Shopify’s documentation.

Our take

For anyone building integrations, Poppy’s real offer is replacing “write one integration per site” with “implement one spec,” on a stack most teams already run — OAuth, OpenAPI and MCP are all established, and UCP is already the default on Shopify. Distribution, usually the hardest part of a new protocol, was solved on day one: Muse looks for Poppy first, and every Shopify store publishes the file automatically. Few standards get that kind of cold start.

Three catches are worth tracking. The docs themselves still say Draft 1.0, so breaking changes are possible. “Every merchant enabled” comes from Sierra’s announcement — Shopify’s own documentation had yet to mention Poppy as of November 14, so real coverage needs Shopify’s confirmation. And the security ceiling depends on how each company configures scopes: the protocol provides the mechanism, but “customers control permissions” is Sierra’s design intent, not an audited outcome. Only three partners are live; the other hundred-odd companies are design partners, not deployments.

How to try it

Companies should read the spec at personalagentprotocol.org/docs/1.0/spec, then use the implementation kit: install the implement-personal-agent-protocol skill in your coding agent to do the build, and run the validator, which acts as a test personal agent against your deployment. Developers who just want the shape of the interface can skip the blog post and read the discovery-file fields and OAuth chapters directly.