Built with Muse Publish a workflow
Guides

What Is Poppy? How Muse's Personal Agent Protocol Works for You

Poppy is the reason a website will soon stop treating your Muse like a bot. It is an open protocol, version 1.0 released November 13, 2026, that lets your agent introduce itself to a business, say what it is allowed to do, and get let through instead of blocked. You do nothing: it is already on for every Muse user.

November 2026 ยท 18 min read
Advertisement
Get started

Poppy is on for every Muse user since November 13, 2026. Set up Muse today and redeem a code within 48 hours to claim the token bonus.

Get a free code
Yes, Poppy is already working for you, and you do not need to turn it on. Muse looks for Poppy first on every site it visits. If the site has a Poppy file, your agent identifies itself and gets the right access. If it does not, nothing changes. There is no setting, no install, and no cost.

What is Poppy, in plain terms?

Poppy is a handshake. Its full name is the Personal Agent Protocol, and it is an open standard for how your own AI agent works with a company on your behalf. The company publishes a small file, called poppy.json, at a standard address on its own website. That file says what the company offers, a website, its APIs, its own agent, and how to reach each of them. Your agent reads the file, introduces itself, and asks what it is allowed to do. The business answers with a clear, machine readable description of its services. That is the whole idea, and it is deliberately boring: Poppy is built largely on standards that already exist, including MCP, OpenAPI and UCP, instead of inventing a new stack.

Sierra, the company that built Poppy with Meta, announced it on October 6, 2026, published the first draft on October 9, and released version 1.0 on November 13, 2026. The frozen 1.0 specification itself is dated November 14, 2026, so keep the two dates apart: the announcement is November 13, the frozen spec is November 14. The spec is free and public at personalagentprotocol.org, under an Apache 2.0 licence, and any company can implement it on its own. The announcement is at the Sierra blog, and the Muse side of the story is at the Muse blog.

The reason Poppy exists is a problem every Muse user has already felt. Businesses cannot tell a personal agent acting for a real customer apart from unwanted automated traffic, so they block both. Amazon blocked Muse outright on September 20, 2026, and other sites quietly do the same. Poppy fixes the identification half of that problem. When your agent arrives at a site, it says who it is and asks what it may do, instead of looking like an anonymous bot. The business can then let it through, guide it down the path that works, and connect the website activity, API calls and business agent conversations in one session. You stay in charge throughout: you grant access, you manage it, and you can revoke it.

Advertisement

How does Poppy work when Muse visits a site?

It starts with the file. When Muse visits a site, it first looks for the Poppy file at the standard address, /.well-known/poppy.json. If the file is there, Muse reads what the company offers and how to reach it. If it is not there, nothing changes: Muse carries on the way it does today, in its own browser, with the same limits as before. Poppy adds a better path where one exists. It does not remove the old one where it does not.

Then comes identity. Your agent identifies itself with a client id, a public address that says which agent it is, and a signed, short lived session token with each request. As of November 2026, Muse is the only personal agent with a published Poppy client id, at muse.ai/poppy/agent.json, and it is the first personal agent to support the protocol. When a task needs your account, you sign in on the company's own page, through OAuth, the same way you sign in to any site. Your agent never handles your password. That detail matters: the agent acts for you without ever holding the keys to your account.

Then comes the session. Poppy connects your website activity, your API calls and your conversations with the company's own agent into one session, so the business sees one customer doing one thing, not three separate visits from three directions. Inside that session, the commerce extension, written with Shopify, lets the agent shop as a guest or signed in, and makes the agent ask you before certain actions. The extension also links to UCP Ask, so your agent can talk directly to the store's agent. The technical walkthrough is at the Arcjet explainer.

What is the difference between Poppy and UCP?

This is the question that confuses everyone, because the two protocols arrived together and both involve shopping. Sierra states the split in one line: UCP handles the shopping itself, like finding products, filling a cart, and checking out. Poppy handles what happens before that, when an agent shows up at a store, says who it is, and finds out what it is allowed to do. Poppy is the introduction. UCP is the purchase.

Think of it as a shop door and a till. Poppy is the door: the agent knocks, says who it is and who it works for, and the shop decides which rooms it may enter. UCP is the till: once the agent is inside and allowed to buy, UCP is the shared language for finding products, filling the basket and paying. Without Poppy, the agent is stopped at the door because the shop cannot tell it from a bot. Without UCP, the agent gets inside but has no standard way to buy. The two are complementary, not competing, and the commerce extension is the bridge between them.

The practical consequence for you is that Poppy changes nothing about how a purchase works, and everything about whether the purchase is possible at all. Your checkout still runs through UCP, Shop Pay or the store's own flow, with your approval before anything is charged. What Poppy changes is the step before: whether the store lets your agent in, whether it can see your account, and whether it can use the store's own agent instead of clicking around the website like a stranger. If a store has Poppy, Muse gets the guided path. If it does not, Muse gets the website, the same as today.

Which companies are actually live on Poppy?

Three companies are named as going live in Sierra's announcement, and they are the proof that Poppy is more than a paper standard. Mercury, the banking company, lets an agent check balances, review transactions, categorize spending, and work with budgets and receipts, and it can initiate a payment or transfer, routed through the account's approval policy first. Synchrony, the financing company, surfaces financing and rewards inside agent led shopping, across more than 500,000 merchant locations. Turkish Airlines lets an agent look up fares and flight status, check stopovers, and find a booking by reference number and surname, with Miles and Smiles business class upgrades approved before paying, and it is working on completing a purchase without leaving the conversation.

One honest caution belongs here: no announcement from Mercury, Synchrony or Turkish Airlines in their own names had appeared as of November 14, 2026. The live claims rest on Sierra's post alone. That does not make them false, but it means the guide cannot point you to a Mercury or Turkish Airlines page that confirms them. Treat the three as Sierra's word, and watch for the companies themselves to confirm. The design partner list is much longer, now more than 100 companies, with 64 new at version 1.0, including Affirm, Agoda, Delta Air Lines, Hyatt, Salesforce, SoFi, Twilio, Wayfair, Wix, Zoom, Intuit, Cisco, GoFundMe, HelloFresh, Lemonade and Manus. The original October partners were Meta, Genesys, Instinct, NiCE, Rocket, Shopify, Stripe and Walmart.

Two more names are worth separating from the live three, because the wording is future, not present. Muse's own blog says Muse can soon talk directly with the agent of BYLT, the clothing company. Hertz is running a pilot, through Decagon's Personal Agent Gateway, where an agent can look up, change and extend reservations. Soon and pilot are not live. The list of who is live today is three names long, and the list of who has signed up to build is more than 100 long. That gap is normal for a standard that is one week old, and it is the gap to watch over the next months.

What does Poppy mean for Shopify stores?

Shopify is the reason Poppy could matter fast. Every Shopify store supports UCP by default, and now automatically publishes a Poppy file, with no work from the merchant. Shopify powers businesses in more than 175 countries, so a single platform decision puts a Poppy file on millions of storefronts at once. A merchant does nothing, and a Muse user visiting any of those stores gets the identified path instead of the anonymous one.

For a shopper, that means the Shopify stores you already buy from are now, in principle, Poppy ready. Your Muse can identify itself to the store, find out what it is allowed to do, and use the store's own agent where one exists, instead of scraping the website. For a merchant, it means the agent traffic arriving at your store can be told apart from bot traffic, and given the right access, without you configuring anything. The stores that will feel the difference first are the ones whose customers already send agents: the early Muse shoppers, who are also the early Poppy users.

There is a limit to keep in mind. A Poppy file does not mean the store has built an agent of its own, or that every feature works through it. It means the store has published what it offers and how to reach it. The depth of what Muse can do there depends on what the store exposes, and that will vary store by store for a long time. Shopify made the file automatic. What each store puts in the file is still up to the store. If you run a Shopify store, the file is already there. If you shop on one, the file is already working for you.

What changes for you as a Muse user?

In the short term, almost nothing you can see. Poppy has no switch to turn on, no app to install, and no cost. It is on for everyone who uses Muse, and it works silently in the background: Muse looks for the Poppy file first on every site it visits, and uses it when it is there. There is no in app sighting of Poppy behaviour in Muse as of November 14, 2026, and no user facing step, cost or setting has been published. Do not look for a Poppy menu in your Muse settings, because there is not one. The guide has no 'how to turn Poppy on' section for exactly that reason.

What changes is what happens at the door of the sites you visit. Where a site has Poppy, your agent gets identified and let through, instead of being treated as a bot and blocked. Where a site has its own agent, your agent can talk to it directly. Where a site has an API, your agent can use it with your permission. None of that shows up as a new button. It shows up as fewer failures: fewer sites that refuse Muse, fewer checkouts that stall, fewer tasks that end with 'the site blocked me'. The improvement is measured in things that stop going wrong, not in things that appear.

The other change is control. Poppy gives you a clear record of what your agent was allowed to do, and a clear way to take it back. You grant access, you manage it, and you revoke it. That matters more as agents do more on your behalf, because the question stops being 'can my agent do this' and becomes 'who did my agent talk to, and what did I allow'. Poppy answers the second question in a standard way, instead of leaving each company to invent its own. If you care about what your agent does in your name, that standard is the feature.

What if you run a business and want Poppy?

Any company can implement Poppy itself. Sierra publishes an implementation kit with a validator, so you can check your work before going live, and you can adopt in stages, starting with the basics. The first stage is the file itself: publish poppy.json at the standard address, saying what you offer and how to reach it. Later stages add sessions, account authorization and the commerce extension. You do not need to be a design partner and you do not need Meta's permission. The standard is free, public and open.

The business case is the same problem, seen from the other side. Today you cannot tell a customer's agent apart from unwanted automated traffic, so you block both, and you lose the customer who sent the agent. Poppy lets you identify the agent, let it through, guide it down the path that works, and keep one session across the website, the APIs and your own agent. The alternative is to keep blocking agents and watch your customers' agents go to the competitor that lets them in. The companies that adopt first are the ones whose customers already use agents, which is why the first live names are a bank, a financing company and an airline: their customers send agents to do real tasks today.

If you run a business and want the full picture of how brands get on Muse, the three routes are covered in the companies using Muse guide: a reviewed connector, an eligible Shopify store, or the open web. Poppy is a fourth layer that sits across all three: it standardizes how Muse identifies itself to you, whichever route it arrives by. The Shopify route already includes it automatically. The connector and open web routes gain it when you publish the file. Start with the file. It is the cheapest step in the whole list, and it is the one that unblocks the rest.

What is still unknown about Poppy?

The honest list is short but important. First, which of the more than 100 design partners are actually live beyond the three named is unknown. Design partner means signed up to build, not live today, and the gap between the two lists is where most of the names sit. Second, whether any personal agent other than Muse supports Poppy yet is unknown: as of November 2026, no other agent has a published client id. Muse is the only agent on the standard today, which means Poppy's value currently depends on one agent and one platform's stores.

Third, what Poppy feels like inside Muse is unknown, because no in app sighting had been published as of November 14, 2026. The protocol is real and the file is real, but the user experience of it, what you see, what you approve, what the session looks like, has not been shown. Fourth, the live claims for Mercury, Synchrony and Turkish Airlines rest on Sierra's post alone, with no confirmation from the companies themselves yet. All four gaps will close over time, and this guide will be updated when they do. Until then, the fair summary is: the standard is live, the agent is live, the stores are filing in, and the experience is still to be seen.

The way to follow Poppy from here is simple. Watch the Shopify stores you already use: they have the file now, so the identified path is already available there. Watch the three live names for their own announcements. And watch whether a second agent publishes a client id, because that is the moment Poppy stops being a Muse feature and becomes a standard. Get a fresh muse referral code from the community pool if you are still waiting to get into Muse, and check the countries page for where Muse is live.

Frequently asked questions

What is Poppy?
Poppy is the Personal Agent Protocol, an open standard for how your own AI agent works with a company on your behalf. The company publishes a poppy.json file saying what it offers, your agent identifies itself, and the business lets it through instead of blocking it as a bot. Version 1.0 was released November 13, 2026.
Do I need to turn Poppy on in Muse?
No. Poppy is on for everyone who uses Muse, with nothing to install, enable, or pay. Muse automatically looks for the Poppy file first on every site it visits, and uses it when the site has one. There is no Poppy setting in Muse.
What is the difference between Poppy and UCP?
Poppy handles what happens before the shopping starts: the agent shows up, says who it is, and finds out what it is allowed to do. UCP handles the shopping itself: finding products, filling a cart, and checking out. The two are complementary, and the commerce extension links them.
Which companies use Poppy today?
Three are named as live: Mercury, Synchrony, and Turkish Airlines, named in Sierra's announcement. More than 100 companies are design partners, including Salesforce, Delta, Hyatt, Wayfair, Zoom, and Intuit. Every Shopify store automatically publishes a Poppy file.
Is Poppy only for shopping?
No. Shopping is the first use, through the commerce extension, but the protocol covers any company interaction: banking, travel, support, and more. Mercury is a bank, Turkish Airlines is travel, and the standard itself is general.
How can my business add Poppy?
Publish a poppy.json file at the standard address on your website, saying what you offer and how to reach it. Sierra publishes an implementation kit with a validator, and you can adopt in stages, starting with the basics. The standard is free and public.

Built with Muse is an independent community project. Not affiliated with or endorsed by Meta.