ChengRang

Poppy

AI Platforms Free

Sierra released version 1.0 of the Personal Agent Protocol, Poppy, on Nov 13, 2026: it defines how a personal agent announces itself when it arrives at a business, and what it is allowed to do there, leaving the actual shopping to UCP. Built largely on MCP, OpenAPI and UCP, with OAuth for authentication, so customers can narrow what an agent may do at any time. Shopify publishes a Poppy file for every store by default, Meta's Muse looks for Poppy first on every site, more than 100 design partners are involved, and Mercury, Synchrony and Turkish Airlines are already live

SierraAgent ProtocolOAuthShopifyUCP
Visit Poppy

Disclaimer: Review content represents our editorial team's views and experience, not commercial recommendation or investment advice. Product info and pricing may change; refer to official sources.

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

Use Cases

Pros

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

Category
AI Platforms
Pricing
Free
Tags
Sierra · Agent Protocol · OAuth
Website

Related Tools