Field intelligence for AI-first professionalsVol. II · Nº 195 · Monday, November 16, 2026
← Phantom Notes
Nº 191AI AgentsNovember 13, 20264 min read

Every Shopify Store Now Tells AI Agents What They May Do. Merchants Did Not Opt In, the Only Big Agent Reading It Is Meta's Muse, and the Spec Leans on IETF Drafts.

Sierra released version 1.0 of Poppy, its Personal Agent Protocol, on November 13: a way for a personal agent to discover a company, identify itself, sign in through OAuth, and act through APIs, web browsing, or the company's own agent, built on MCP, OpenAPI, and UCP. Shopify turned it on for every merchant, so each store now auto-publishes a Poppy file; Meta's Muse looks for Poppy first on every site it visits; Mercury, Synchrony, and Turkish Airlines are going live, with Mercury allowing agents to initiate payments subject to the account's approval policy; and 60 new design partners bring the total past 100. Merchants got it by default, the only named consumer agent is Muse, live deployments are a handful, and the spec cites IETF and community drafts that can still change. We read Sierra's post and the spec.

By T.W. Ghost


Sierra released Poppy version 1.0 today, November 13, 2026, under Bret Taylor and Clay Bavor. Poppy, the Personal Agent Protocol, is how a personal agent discovers a company, identifies itself, signs in on your behalf through OAuth, and then acts, through the company's APIs, by browsing its website, or by talking to the company's own agent. It is built on MCP, OpenAPI, and UCP. The launch comes with distribution most protocols never get: Shopify enabled Poppy for every merchant, so each store now publishes a Poppy file automatically, and Shopify co-authored the commerce extension, which supports guest or signed-in shopping, requires the agent to ask the customer before certain actions, and connects to UCP Ask. On the agent side, Meta's Muse "automatically looks for Poppy first on every site it visits." Mercury, Synchrony, and Turkish Airlines are going live, and 60 new design partners bring the total past 100.

Now the shape of it. Shopify merchants did not opt in; the protocol arrived on their stores as a default. The only consumer agent named as a reader is Muse; OpenAI, Google, Anthropic, and Amazon are not on the partner list we read, and we found no statement on whether ChatGPT's dots read Poppy files. Live use is three companies against more than a hundred partners. The spec describes 1.0 as "0.4 with the fixes implementers needed" and cites an IETF OAuth draft, the CIMD draft, and a draft Agent Skills discovery proposal at version 0.2.0, so the identity layer rests on documents that can still change. And money is in scope: Mercury's integration lets an agent initiate a payment or transfer, gated by the account's approval policy rather than by the protocol. We read Sierra's post and the 1.0 spec. Here is what held up.


What Shipped

Poppy 1.0 (Sierra, November 13, 2026)
What it doesDiscover a company; identify the agent; OAuth sign-in; act via APIs, web browsing, or the company's agent
Built onMCP, OpenAPI, UCP
ShopifyEnabled for every merchant; each store auto-publishes a Poppy file; Shopify co-authored the commerce extension
Commerce extensionGuest or signed-in shopping; agent must ask the customer before certain actions; connects to UCP Ask
Agent readerMeta's Muse looks for Poppy first on every site it visits; Muse set up by more than 10 million people (press)
Going liveMercury (balances, transactions, initiate payment or transfer via account approval policy); Synchrony (exploratory); Turkish Airlines (fares, status, bookings, upgrade search)
Partners60 new design partners; total above 100, including Delta, Intuit, Salesforce, Zoom, Wayfair, Stripe from the original group
Spec1.0 is "0.4 with the fixes implementers needed"; roadmap lists uncovered areas; cites draft-ietf-oauth-rfc7523bis, the CIMD draft, and a draft Agent Skills discovery proposal (0.2.0)
Draft statusTNW says the spec is "still labelled a draft" and allows breaking changes; not found in the spec text we read

Default-on for merchants. A Shopify store owner who has never heard of Poppy now publishes a file telling agents what they may do there. Shopify chose for them.

One major agent. Muse. No OpenAI, no Google, no Anthropic, no Amazon on the list. OpenAI built a wallet the same day; Sierra and Meta built the front door, and the two are not connected in anything we read.

Three live, a hundred signed. Partners are logos. Live integrations are Mercury, Synchrony, and Turkish Airlines, one of which lets your agent start a bank transfer.

Built on drafts. The identity pieces cite IETF and community drafts. Version 1.0 is a commitment by Sierra; the documents under it have not made the same commitment.


Verified vs Unconfirmed: The Scorecard

ClaimVerdict
v1.0 released Nov 13, 2026; Taylor and BavorVerified (Sierra blog)
Shopify default-on; auto-published files; co-authored extensionVerified (vendor)
Commerce extension behavior; UCP AskVerified (vendor)
Muse looks for Poppy firstVerified (vendor)
Muse 10 million usersPress only (TNW)
Mercury, Synchrony, Turkish Airlines scopeVerified (vendor)
60 new partners; total above 100Verified (vendor)
"0.4 with the fixes"; draft referencesVerified (spec)
Spec labelled a draft; breaking changes allowedPress (TNW); not found in the spec text we read; held
ChatGPT dots read Poppy filesNo statement found

What To Do

Read your store's Poppy file if you run on Shopify, because an agent will; the extension says agents must ask before certain actions, and you should know which.

Skip treating 1.0 as finished, on the spec's own description of itself and the drafts it cites, and skip assuming any agent but Muse reads it until another one says so.

The frontier is elsewhere: the banks that blocked agents are now being asked to publish rules for them, and the Meta model behind Muse's reading is covered in Muse Ember. Our model comparison has the current standings side by side.


Sources


*Not sure whether your agent should be reading other companies' rules or writing your own? Take the free 2-minute quiz and get matched. Then read about the payment rail launched the same day without a protocol: ChatGPT Wallet.*

Which model should you be using?

Three minutes, twelve questions, one defensible answer.

Take the quiz →