The Agent Web Just Got a Handshake: Poppy 1.0 Ships to Every Shopify Store

On November 13, 2026, Sierra shipped version 1.0 of Personal Agent Protocol — Poppy for short — and with it, quietly, one of the biggest install-base flips in the short history of agentic commerce: every Shopify store in more than 175 countries now automatically publishes a Poppy file, with zero work required from the merchant, and Meta's Muse agent — which millions of shoppers now run — checks for Poppy first on every site it visits. Poppy is the handshake layer of the agent web: a standard way for a visiting AI agent to say who it is and discover what it is allowed to do at your business. If you sell on Shopify, you just opted in by default. If you do not, the question is whether your site can speak the same handshake. Here is what shipped, how the protocol actually works, and what a small business in Temecula or Murrieta should do about it.
What Poppy Actually Is
Sierra, the AI customer experience company led by former Salesforce co-CEO Bret Taylor, first announced the protocol last month with design partners including Meta, Shopify, Stripe, and Walmart, then spent five weeks with partners testing drafts against real websites, APIs, and agents before cutting version 1.0. The idea is simple to state: when a personal agent — Muse, or whoever comes next — arrives at a company, the company should be able to tell it who it is talking to and what it is allowed to do, such as check an order or book a flight. Customers sign in through standard logins and decide what their agent can access, and can manage that access over time. Poppy is not a new silo: it is largely assembled from existing standards — MCP, OpenAPI, and UCP — with OAuth handling authentication, and it is designed so a company can adopt it in stages, starting with the basics and adding capabilities later.
What Shipped on November 13
Four things landed at once. First, v1.0 of the protocol is now available, with an implementation kit and a validator any company can run itself. Second, Shopify enabled Poppy for every merchant on its platform: every store automatically publishes a Poppy file, so merchants need no extra implementation. The division of labor matters here — every Shopify store already supports the Universal Commerce Protocol (UCP) by default, which handles the shopping itself: finding products, filling a cart, checking out. Poppy handles what happens before that, when an agent shows up at a store, identifies itself, and learns what it is allowed to do. Shopify co-authored the commerce extension that links the two: an agent can shop as a guest or sign in with the customer's account, must ask the customer before taking certain actions, and can talk directly to the store's own agent through UCP Ask.
Third, Poppy is now on for everyone who uses Muse, which automatically looks for Poppy first on every site it visits — a default behavior that instantly makes the protocol the path of least resistance for any company Muse's users touch. Fourth, 60 new companies joined as design partners, bringing the total past 100: Cisco, Delta Air Lines, HelloFresh, Hyatt, Intuit, Lemonade, Navy Federal Credit Union, Salesforce, SoFi, The Knot, Travelers, Turkish Airlines, Twilio, Wayfair, Wix, and Zoom among them. A few are already live in ways that sketch the range: Mercury lets personal agents check balances, review transactions, and even initiate a payment — routed through the account's existing approval policy before anything moves. Turkish Airlines lets an agent pull up fares, flight status, and a booking, and find business-class upgrades the customer approves before paying. Synchrony is exploring financing and rewards inside agent-led shopping across a network of more than 500,000 merchant locations.
How the Handshake Works Under the Hood
The mechanics are refreshingly concrete. A company publishes a poppy.json file at the standard /.well-known/ path on its domain over HTTPS, advertising which channels, capabilities, and sign-in options it offers — the company picks what to expose. A signed Session header identifies the visiting personal agent and a pseudonymous user; standard OAuth separately authorizes anything touching a real account. User IDs are stable at one company but opaque and different across companies, so businesses cannot match the same person across sites. Two security rules deserve attention from any owner nervous about agents: company content must be treated as data rather than instructions — a structural defense against prompt injection — and access tokens, session tokens, private keys, and authorization codes must stay out of the model's context entirely. Conversations label whether a person or an AI wrote each message and support handoff to a human. One honest caveat: Sierra's announcement calls this 1.0, but the specification itself is still labeled a draft that permits changes, including ones that break compatibility. The foundation has scale before it is fully settled.
Why This Week Matters
Zoom out and the pattern of the last month sharpens. Amazon, as we covered yesterday, is building walls — blocking outside agents, suing to keep them out, and trying to own the product data underneath them. The same week Poppy shipped, OpenAI began rolling out ChatGPT Wallet so its own agents can complete purchases a customer approves, paying with a network token instead of the real card number. And Google switched on its agent-friendly Universal Cart across Search and Gemini last month. In other words: one giant is enclosing, another is paying, and Sierra's coalition — Meta, Shopify, Stripe, Walmart, now a hundred more — is standardizing the front door. For businesses, standards wars are actually good news when your side wins: a handshake that works everywhere means agents stop being a per-platform integration project.
What This Means for a Temecula or Murrieta Business
- If you sell on Shopify, you are already speaking Poppy. Nothing to install — but do look at what your store exposes through it: current prices, real availability, clear policies, working contact paths. The handshake is only as good as the data behind it. An agent that arrives, identifies itself, and then reads a stale catalog still gives your customer a wrong answer.
- If you are not on Shopify, do not rush to implement. The kit and validator are public and any company can go live — but the spec is still a draft that allows breaking changes. Watch it, maybe prototype it, but do not pay for custom integration work against a foundation that can shift. Revisit when the spec firms up or when you see real agent traffic in your logs.
- Service businesses: your near-term agent play is still the answer layer. Poppy governs agents that arrive to transact. Before that, the agent has to find and trust you — which is the claim-your-profile, clean-data discipline we laid out when ChatGPT opened business listings, and the phone-readiness we covered when Muse started calling businesses. Same foundation, new front door.
- Put the handshake on your 2027 map, not this quarter's invoice. Muse checking for Poppy on every visit makes adoption cheap for big companies; for a local business, the meaningful date is when your customers' agents actually try to book or buy from you. Until then, the winning move is the unglamorous one: a fast, structured, accurate website that any visitor — human or agent — can read.
The Bottom Line
The agent web is getting its handshake, and this week it reached every Shopify store on Earth whether their owners noticed or not. That is how infrastructure arrives: silently, by default, all at once. Your counter-move is not to panic-implement a draft protocol — it is to make sure that whatever handshake wins, your business has something accurate and structured to shake with. That is the work we do every day for Temecula and Murrieta businesses: websites, AI employees, and data that stays clean enough for any visitor to read — the kind of foundation that pays off no matter which standard the agent web settles on. PepeWebTech builds AI employees from $397/mo and fast, SEO-ready websites — free setup, no contracts, cancel anytime.
Sources
- Sierra — Bret Taylor and Clay Bavor, "Releasing Personal Agent Protocol 1.0" (November 13, 2026) — primary announcement: v1.0 availability and implementation kit; Shopify enabling Poppy for every merchant in 175+ countries with automatic Poppy file publication and no merchant implementation; UCP handling shopping while Poppy handles agent identification and permissions; the Shopify-co-authored commerce extension with customer-approval gating and UCP Ask; Poppy on for all Muse users with Muse checking for Poppy first on every site; 60 new design partners bringing the total past 100 (Cisco, Delta, Intuit, Salesforce, Twilio, Wayfair, Wix, Zoom, et al.); live deployments at Mercury (approval-policy-routed payments), Synchrony (500,000+ merchant locations), and Turkish Airlines (approve-before-pay upgrades).
- The Next Web — "Sierra releases Poppy 1.0 as Shopify and Meta's Muse sign on" (November 13, 2026) — independent coverage confirming the release details; Muse described as set up by more than 10 million people and now looking for Poppy first on every site; Sierra identified as the AI customer service company led by former Salesforce co-CEO Bret Taylor; note that the specification remains a draft despite the 1.0 label.
- Unite.AI — "Sierra Releases Poppy 1.0 With Shopify and Meta Muse Support" (November 2026) — protocol mechanics from the draft specification: poppy.json published at /.well-known/poppy.json over HTTPS advertising channels, capabilities, and sign-in options; signed Session header with pseudonymous per-company user IDs; OAuth for account actions; company content treated as data rather than instructions; tokens, session tokens, private keys, and authorization codes kept out of model context; person-or-AI message labeling with human handoff; draft status permitting non-backward-compatible changes.