Featured:MeloLab– Create songs and background music with AI.

Sierra Personal Agent Protocol (Poppy)

Poppy 1.0 lets personal agents work with companies through business agents, websites and APIs. Learn what the release includes, how it uses MCP, OpenAPI, UCP and OAuth, and how to implement it.

Type:
AI Tool
Sierra Personal Agent Protocol (Poppy) product preview
Contents

What is Sierra Personal Agent Protocol (Poppy)?

Poppy 1.0 lets personal agents work with companies through business agents, websites and APIs. Learn what the release includes, how it uses MCP, OpenAPI, UCP and OAuth, and how to implement it.

Updated ·

Sierra Personal Agent Protocol (Poppy) 1.0: What It Is and How to Implement It

Announcement date:

Poppy is the name of version 1.0 of the Personal Agent Protocol from Sierra, now available. It defines how personal agents interact with companies through business agents, websites and APIs, and it is largely built on existing standards such as MCP, OpenAPI and UCP, with OAuth handling authentication so customers can control what an agent may do. Any company can implement Poppy on its own using an implementation kit that includes a validator, and Shopify stores already publish a Poppy file automatically.

Social artwork announcing the release of Personal Agent Protocol 1.0
Publisher announcement artwork; not a product interface screenshot.

What Poppy 1.0 includes

Poppy is a protocol for the interaction layer between a customer's personal agent and a company. Rather than inventing a new stack from scratch, it is largely built with existing standards like MCP, OpenAPI and UCP, so teams can map it onto tooling they may already know.

Version 1.0 is the first generally available release. Compared with the initial draft, it was changed to make staged adoption easier: a company can start with the basics and add capabilities over time instead of implementing everything at once.

  • Version 1.0 of the Personal Agent Protocol, called Poppy, is now available.
  • Poppy enables personal agents to interact with companies through business agents, websites and APIs.
  • The protocol is largely built with existing standards such as MCP, OpenAPI and UCP.
  • Staged adoption is supported: start with basics, add capabilities over time.

Extensions and the Shopify commerce extension

Version 1.0 introduced extensions, which let an industry build on the core protocol without changing it. The example given in the release is a commerce extension co-authored by Shopify.

For teams evaluating Poppy, extensions are the place to look for domain-specific behavior such as commerce, rather than expecting the core protocol to cover every vertical.

  • Extensions were introduced in 1.0 so industries can build on the core protocol without modifying it.
  • The commerce extension was co-authored by Shopify.

How Poppy relates to MCP, OpenAPI, UCP and OAuth

Poppy is described as largely built with existing standards like MCP, OpenAPI and UCP. In practice that means the protocol leans on established conventions for describing and exposing capabilities rather than replacing them.

Authentication is handled through OAuth. That gives customers control over what personal agents can and cannot do, and lets them manage that access over time. For implementers, this is the part to design carefully: the customer, not the company, is the party granting and revoking agent permissions.

  • MCP, OpenAPI and UCP are the existing standards Poppy is largely built with.
  • OAuth handles authentication and lets customers manage agent access over time.

Implementing Poppy with the kit and validator

With v1.0, any company can implement Poppy on its own. Sierra provides an implementation kit that walks through setup and includes a validator to check the work.

A sensible starting sequence is to adopt the basics first, confirm them with the validator, and then layer on extensions or additional capabilities. The staged-adoption design of 1.0 exists precisely so that companies do not need a full rollout on day one.

  • Any company can implement Poppy on its own with v1.0.
  • The implementation kit walks through setup and includes a validator to check your work.
  • Start with the basics, validate, then add capabilities over time.

What Shopify stores and Muse users get today

Every Shopify store now automatically publishes a Poppy file, so merchants do not need to do any extra implementation. For merchants, that means the protocol surface is already present without a separate project.

Poppy is also enabled for everyone who uses Muse, Meta's AI agent, which automatically looks for Poppy first on every site it visits. Companies that implement Poppy are therefore addressing a client that already checks for it.

  • Every Shopify store automatically publishes a Poppy file; no extra merchant implementation is required.
  • Poppy is on for everyone who uses Muse, Meta's AI agent.
  • Muse automatically looks for Poppy first on every site it visits.

Design partners and early examples

60 new companies are joining as design partners, bringing the total to more than 100. Two published examples show the kind of tasks personal agents can perform.

Mercury customers can ask a personal agent to check balances, review transactions, categorize spending, or initiate a payment or transfer, with Mercury ensuring the request goes through the account's approval policy before anything is sent. Turkish Airlines personal agents can check fares, flight status and stopovers, pull up a booking with a reference number and surname, and find business-class upgrades that customers approve before paying.

  • 60 new design partners join, for a total of more than 100.
  • Mercury: balances, transactions, spending categories, and payments or transfers subject to the account's approval policy.
  • Turkish Airlines: fares, flight status, stopovers, booking lookup by reference number and surname, and business-class upgrades approved before payment.

Pricing and availability status

Poppy 1.0 is described as now available, and the implementation kit is offered to companies that want to adopt it. The supplied material does not state pricing for the protocol or the kit, so cost should be treated as unknown here rather than assumed to be free or paid.

The protocol is also not presented as a finished, frozen specification: 1.0 introduced extensions and staged adoption, and the design-partner program suggests continued evolution.

  • Pricing for Poppy or the implementation kit is not stated in the available material.
  • Treat the protocol as evolving; check current documentation before committing to a design.

Questions

Is Poppy the same thing as the Personal Agent Protocol?

Yes. Poppy is the name used for version 1.0 of the Personal Agent Protocol, which is now available.

Do I need to replace MCP or OpenAPI to use Poppy?

No. Poppy is largely built with existing standards like MCP, OpenAPI and UCP, so it is intended to work alongside them rather than replace them.

Do Shopify merchants need to do anything to support Poppy?

According to the release, every Shopify store now automatically publishes a Poppy file, so merchants do not need any extra implementation.

Who controls what a personal agent can do with my account?

Authentication goes through OAuth, which lets customers control what personal agents can and cannot do and manage that access over time. In the Mercury example, requests such as payments or transfers still pass through the account's approval policy.

Original sources

  1. sierra.ai — Original source 1 ↗

Tool Info

Has this tool changed? Help us keep it up to date

See also: related tools and guides

Loading reviews…

Sierra Personal Agent Protocol (Poppy) Reviews

Not rated yet0 user reviews

Do you recommend Sierra Personal Agent Protocol (Poppy)? Leave a comment below!

Your rating
0 / 2000

Loading reviews…

Categories

FOR PRODUCT BUILDERS

Built something useful? Help people find it.

Start with your website. Add your logo, screenshots and product details to a listing you can keep up to date.

Verify your website badge for a free listing.