AI News

Sierra Releases Personal Agent Protocol Poppy 1.0, Shopify All Stores and Meta Muse First to Integrate

Shao MengUpdated Nov 14 10:08

AI summary

Sierra co-founders Bret Taylor and Clay Bavor announced the release of the Personal Agent Protocol Poppy v1.0, an open protocol jointly promoted by Sierra and partners including Meta. Enterprises publish a /.well-known/poppy.json file under their own domain to declare their entry point and login method; personal agents first start a session as a guest, and when an account is needed, the user authorizes via OAuth, so the same session can continue seamlessly across the web, API, and conversations. On the Shopify platform, every store has automatically published a Poppy file, and Meta's personal agent Muse has been enabled for all users; the official site, implementation toolkit, and GitHub repository still label the current text as draft 1.0, and fixes before finalization may not be backward compatible.

Quoted post

Sierra

@SierraPlatform

Today we’re releasing Personal Agent Protocol (Poppy) v1.0. It’s on for everyone who uses Muse, @Meta's AI agent, enabled for every merchant on @Shopify, and backed by more than 100 design partners. https://t.co/0CrPrTUWEy

View original

Today we’re releasing Personal Agent Protocol (Poppy) v1.0. It’s on for everyone who uses Muse, @Meta's AI agent, enabled for every merchant on @Shopify, and backed by more than 100 design partners. https://t.co/0CrPrTUWEy

View original post

Body · AI translation

Sierra Releases Personal Agent Protocol Poppy 1.0: Personal Agents Connect with Enterprises Upon Authorization, All Shopify Stores and Meta Muse Among First to Integrate

Sierra co-founders Bret Taylor and Clay Bavor announced the official release of the Personal Agent Protocol (Poppy) v1.0. This open protocol is jointly promoted by Sierra and partners including Meta. It addresses the current situation in which personal agents often can only click through web pages like humans when getting things done, and enterprises either block agents at the door or cannot tell whom they represent and what they are permitted to do. https://t.co/hxaTBlrLtR

How the Protocol Works

According to the official specification, enterprises publish /.well-known/poppy.json under their own domain, specifying which entry points and login methods they offer. Entry points can be websites, APIs (such as OpenAPI, MCP), or the enterprise's own agent. A personal agent first starts a session as a visitor and states who it is. When an account is needed, the user logs in and grants permission scopes on the enterprise's own page via OAuth, after which the same session can proceed seamlessly across the web, APIs, and conversation.

Some capabilities are available without logging in, so enterprises do not need to build a complete authorization service from the start. Version 1.0 places greater emphasis on phased integration than the initial draft and introduces an extension mechanism, so new capabilities do not require changes to the core protocol. The commerce extension co-authored with Shopify is used to connect with the Universal Commerce Protocol (UCP): Poppy handles discovering enterprises, stating identity, and completing login, while the specific shopping flow is left to UCP.

Deployments Announced This Time

According to Sierra, every store on the Shopify platform has automatically published the Poppy file, so merchants do not need additional development. Meta's personal agent Muse has enabled Poppy for all users and prioritizes looking for this protocol when visiting websites.

Two examples are already live. Mercury allows users to check balances, organize bills, and initiate transfers through personal agents, subject to the constraints of account approval rules. Turkish Airlines can query fares, flight status, and existing bookings; member upgrades require user confirmation before payment, and full ticket purchasing is still in progress. Synchrony's financing and offers integration is described in the blog post as being explored.

Sierra also said it has added 60 design partners, bringing the total to more than 100. Enterprises can use the official implementation toolkit, which includes a set of skills for coding agents and a command-line validator that checks whether a deployment is compliant. The specification and documentation are licensed under Apache 2.0.

The Specification Is Still a Draft

v1.0 is already usable, but the official site, implementation toolkit, and GitHub repository still label the current text as draft 1.0. The changelog states that this draft will continue to be revised until 1.0 is formally finalized, and fixes before then may still be backward incompatible. On the roadmap, features such as payment notifications, push, and attachments are not yet covered.

Source

Shao Meng