Overview
When an agent arrives at a store, the first thing that happens is not picking a product. It is introducing itself: who it is, who it speaks for, what it is allowed to do on this site. That layer went undefined for a long time, so every merchant guessed separately and effectively wrote custom logic for every agent. On Nov 13, Sierra turned that layer into a protocol: the Personal Agent Protocol, Poppy for short, version 1.0.
The boundary is drawn clearly. Poppy handles the handshake and the scope of access. The shopping itself stays with UCP, which still finds products, fills carts and takes payments. A commerce extension links the two, co-authored by Shopify: an agent can browse as a guest or sign in with the customer's account, sensitive actions must be confirmed with the user first, and it can reach UCP Ask to talk directly to the store's own agent.
Nothing was reinvented. Most of the protocol sits on MCP, OpenAPI and UCP, with OAuth for authentication. Users can narrow access at any time, and merchants can state their rules and collect feedback from agents inside the protocol. Version 1.0 changed three things from the draft: merchants can adopt in stages, the way existing standards are used was tightened, and an extension mechanism lets vertical industries build on the core without modifying it.
The adoption numbers are the most concrete part. Shopify publishes a Poppy file by default for every store across more than 175 countries, with no implementation work for merchants, which fills in the hardest part of a protocol launch. Meta's Muse is on for everyone and looks for Poppy first on every site it visits. Design partners grew from 40 to more than 100, adding Salesforce, Zoom, Intuit, Delta, Hyatt, Wayfair, Checkout.com, Twilio, SoFi and Wix among others.
Three live cases deserve the detail. Mercury lets a personal agent check balances, review transactions, categorise spending and keep budgets and receipts current, and can even initiate a transfer, provided the request passes the account's own approval policy first. Synchrony brings financing and rewards into agent-led shopping across more than 500,000 merchant locations. Turkish Airlines exposes fares, flight status and stopovers, pulls up a booking by reference number plus surname, and lets Miles&Smiles members have an agent look for business-class upgrades that the customer approves before paying.
Read alongside the wallet launched the same day, this forms a complete chain: Poppy answers who you are and what you may do, the wallet answers how money moves and how much. One is the door, the other the register. Without both, agent shopping stays a demo.
The limits are worth stating. The protocol carries no catalogue, inventory or settlement, which belong to UCP, and it offers no shared audit trail or liability model, so how a merchant records what an agent did is still their own decision. Personal agents outside Muse have to implement Poppy themselves to benefit from default publication.
Key Features
- Handshake and capability disclosure: An agent states who it is, which user it represents and what it can do before a merchant decides to allow or refuse, so no one writes custom logic per agent.
- OAuth with narrowing scope: Authentication runs through OAuth and users can adjust what an agent may do on a site at any time, so access is a continuing state rather than a one-time grant.
- Complementary to UCP, not overlapping: Poppy covers entry and permissions while UCP keeps handling products, carts and checkout. A Shopify co-authored commerce extension joins them and requires user confirmation for sensitive actions.
- Staged adoption and extensions: Merchants can ship the basics and add capability later, and verticals attach through extensions without touching the core. Version 1.0 introduced the extension mechanism, with commerce and finance as separate extensions.
- Default publication at platform scale: Shopify generates a Poppy file for every store automatically across more than 175 countries, requiring nothing from merchants and solving the cold start that usually kills a protocol.
- Implementation kit and validator: Official guidance plus a validator let any company implement on its own, producing files that already-supported agents such as Muse recognise immediately.
Use Cases
- Marketplaces publishing Poppy files for every merchant so agents can identify themselves on arrival
- Banks and payment firms exposing balance checks and payment initiation while keeping their own approval policies
- Airlines and hotels opening fares, bookings and upgrades for agent lookup, with the customer confirming before payment
- Agent vendors implementing once to reach every site that already supports the protocol
Pros
- Separates agent identity and permission from products and checkout instead of mixing all three
- Reuses MCP, OpenAPI, UCP and OAuth, so implementers learn nothing entirely new
- Default platform publication puts merchants live with zero work, which is the hardest part of any protocol
- Access can be narrowed at any time, making user control a standing setting rather than a switch
Pricing
The protocol is free and public, with the specification and implementation kit at personalagentprotocol.org and no licensing fee to adopt it. The real cost is engineering: merchants publish and maintain a Poppy file, define permission scopes and keep audit records, and financial institutions have to wire the protocol into their own approval policies.
Summary
It fills in the gatekeeping layer between agents and businesses: prove identity and scope first, then talk about transactions and payment. Ecommerce is already covered by Shopify publishing files by default, while finance and airlines just produced their first working examples. What to watch next is how auditing and liability get handled, since the protocol leaves both to merchants.
Version History
- 1.0 release (2026-11-13): Sierra released version 1.0 of the Personal Agent Protocol, Poppy, defining how personal agents announce themselves to businesses and query what they are allowed to do, leaving shopping to UCP. The specification builds on MCP, OpenAPI and UCP with OAuth for authentication, and users can narrow access at any time. Compared with the draft, 1.0 adds staged adoption, tighter use of existing standards and an extension mechanism, with the commerce extension co-authored by Shopify. Shopify publishes a Poppy file by default for every store across more than 175 countries, Meta's Muse looks for Poppy first on every site, design partners grew from 40 to over 100 with Salesforce, Zoom, Intuit, Delta, Hyatt, Wayfair, Checkout.com, Twilio, SoFi and Wix among the additions, and Mercury, Synchrony and Turkish Airlines are live.