---
type: "post"
id: "sierra-releases-personal-agent-protocol-poppy-1-0-dd15ec"
slug: "sierra-releases-personal-agent-protocol-poppy-1-0-dd15ec"
title: "Sierra releases Personal Agent Protocol (Poppy) 1.0, an open standard for personal agents to interact with companies"
description: "Sierra says Personal Agent Protocol (Poppy) 1.0 is ready, with Shopify automatically publishing a Poppy file for every store and several named businesses bringing integrations live."
retrieval_nugget: "Sierra says Personal Agent Protocol (Poppy) 1.0 is ready, with Shopify automatically publishing a Poppy file for every store and several named businesses bringing integrations live. The protocol defines how a personal agent identifies itself to a company and learns what it may do, making agent access a product-integration question rather than an improvised web interaction."
published_at: "2026-11-13"
updated_at: "2026-11-13"
record_date: "2026-11-13"
date_kind: "published_at"
topics: ["agent-protocols","agents","interoperability"]
entities: ["Sierra","Personal Agent Protocol","Shopify","Universal Commerce Protocol","Muse","Mercury","Synchrony","Turkish Airlines"]
related_patterns: ["agent-protocols-become-interoperability-layer"]
novelty_label: "new_fact"
what_changed: "Sierra released Poppy 1.0, with Shopify enabling it for all merchants, Muse prioritizing it, and more than 100 companies participating as design partners."
prior_refs: []
source_url: "https://sierra.ai/blog/releasing-poppy"
source_urls: ["https://sierra.ai/blog/releasing-poppy"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:sierra-releases-personal-agent-protocol-poppy-1-0-dd15ec"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/sierra-releases-personal-agent-protocol-poppy-1-0-dd15ec/","markdown":"https://newruntime.com/posts/sierra-releases-personal-agent-protocol-poppy-1-0-dd15ec.md","json":"https://newruntime.com/posts/sierra-releases-personal-agent-protocol-poppy-1-0-dd15ec.json"}
markdown_url: "https://newruntime.com/posts/sierra-releases-personal-agent-protocol-poppy-1-0-dd15ec.md"
---

# Sierra releases Personal Agent Protocol (Poppy) 1.0, an open standard for personal agents to interact with companies

## Retrieval answer

Sierra says Personal Agent Protocol (Poppy) 1.0 is ready, with Shopify automatically publishing a Poppy file for every store and several named businesses bringing integrations live. The protocol defines how a personal agent identifies itself to a company and learns what it may do, making agent access a product-integration question rather than an improvised web interaction.

## Summary
Sierra says Personal Agent Protocol (Poppy) 1.0 is ready, with Shopify automatically publishing a Poppy file for every store and several named businesses bringing integrations live. The protocol defines how a personal agent identifies itself to a company and learns what it may do, making agent access a product-integration question rather than an improvised web interaction.

## What happened
Sierra’s November 13, 2026 announcement says Personal Agent Protocol, or Poppy, has reached version 1.0 after five weeks of partner testing against real websites, APIs and agents. The protocol is intended to connect personal agents with companies through business agents, websites and APIs. Sierra says it is built largely on existing standards, including MCP, OpenAPI and UCP, rather than replacing those components with a wholly separate stack.

The protocol covers how an agent connects to a company and discovers what the company offers. OAuth authentication lets customers control what personal agents can and cannot do and manage access over time. Sierra says the 1.0 revision makes staged adoption easier, refines its use of existing standards, expands a company’s ability to guide an agent and collect feedback, and adds extensions. The commerce extension was co-authored by Shopify, allowing industry-specific capabilities to build on the core protocol. Sierra’s implementation kit includes setup guidance and a validator.

Sierra reports that Shopify has enabled Poppy for every merchant on its platform. Each Shopify store now automatically publishes a Poppy file, so merchants do not need to implement it separately. Shopify stores support Universal Commerce Protocol (UCP) by default. The announcement distinguishes their roles: UCP handles shopping tasks such as finding products, filling a cart and checkout; Poppy covers an agent’s arrival at a store, identification and discovery of permitted actions. The commerce extension allows guest shopping or sign-in with a customer account, and requires customer approval for certain actions. It also connects to UCP Ask, enabling a shopper’s agent to communicate with a store’s agent.

Sierra names Mercury, Synchrony and Turkish Airlines as businesses going live. Mercury customers can ask a personal agent to check balances, review transactions, categorize spending or maintain budgets and receipts. An agent may initiate a payment or transfer, but Mercury says the request must pass the account’s approval policy before funds are sent. Synchrony is exploring agent-assisted product discovery that takes affordability, rewards and financing into account; the company’s network has more than 500,000 merchant locations. Turkish Airlines agents can check fares, flight status and stopovers, retrieve a booking using a reference number and surname, and find business-class upgrades for Miles&Smiles members, who approve before payment. Sierra says it is working toward purchases completed within the conversation.

Sierra says Poppy is now available for any company to implement independently and deliver an experience for users of Muse, Meta’s AI agent, which checks for Poppy first on every site it visits. It also says 60 companies joined as design partners, bringing the total to more than 100. The announcement presents Poppy as an open standard; it does not state a price for the protocol or implementation kit.

## What the archive adds
New Runtime’s earlier coverage described a Poppy demo running on Cloudflare Workers in [a note dated October 24, 2026](https://newruntime.com/posts/poppy-on-cloudflare-workers-github-repository-irvinebroque-poppy-c78edd/). This is a new event: the protocol has reached 1.0, Shopify has enabled automatic publication for stores, and Sierra names live business integrations.

## Trend signal
Poppy supports the pattern that agent protocols are becoming an interoperability layer between models, harnesses, tools and services. Its use of MCP, OpenAPI and UCP, alongside an extension mechanism and OAuth-controlled access, is consistent with a layered integration surface rather than a single all-purpose protocol. This is evidence of one vendor-led effort and partner deployments, not proof that Poppy will become a durable standard. See [Agent protocols become the interoperability layer](https://newruntime.com/patterns/agent-protocols-become-interoperability-layer/).

## Why now
The announcement says the v1.0 design reflects five weeks of testing draft versions against real websites, APIs and agents. Sierra frames the release around personal agents taking on everyday tasks and Shopify’s view that more shopping is moving to agents. Those are the company’s stated rationale; the announcement does not quantify the shift in shopping behavior.

## Connections to other events
New Runtime’s earlier coverage also described a local personal agent that works across connected apps and websites in [its November 11, 2026 note on Nod](https://newruntime.com/posts/n8n-labs-releases-nod-an-open-source-personal-31bb52/). Nod concerns the agent operating on a user’s computer, while Poppy addresses how a company exposes capabilities and permissions to an external agent. They meet at the boundary between personal-agent workflows and the services those agents need to access.

## Why it matters
For teams building personal agents or customer-facing services, Poppy makes the service side of an agent interaction more explicit: identify the agent, expose available actions, and let the customer authorize access. That can be more dependable than relying on an agent to infer a workflow from a page, and more governable than giving it an unrestricted account session. Shopify’s automatic publication is particularly consequential if the claim translates into usable discovery at scale: merchants would not each need to build a bespoke agent integration.

The concrete examples also show why permissions cannot be treated as a cosmetic step. A banking agent may prepare a transfer, but an approval policy still governs whether it proceeds; an airline customer approves an upgrade before paying. Builders can use these distinctions to separate discovery, preparation and consequential execution in their own integrations. The announcement does not establish that Poppy has become a broadly adopted convention, so teams should evaluate it against their actual agent clients and systems rather than assume ecosystem coverage.

## Limits and uncertainty
The adoption figures and implementation descriptions come from Sierra, and have not been independently checked here. The announcement does not report how many of the more than 100 design partners have deployed production integrations, how frequently personal agents use Poppy, or whether users complete tasks more successfully than through existing channels. It names live deployments but gives no usage, conversion, reliability or security evaluation results. The protocol’s open-standard status does not by itself show how governance, compatibility testing or future revisions will work across implementers. Shopify’s automatic publication is a concrete distribution path, but the announcement does not measure how many agents besides Muse currently discover or use those files.

## Skill to build now
For one customer workflow that currently depends on an agent navigating a website, draw a boundary map this week: list the actions the agent needs to discover, which require customer authorization, and which must still pass a company policy before execution. Compare that map with Poppy’s staged adoption, OAuth controls and commerce extension. This makes it easier to judge whether adopting a protocol solves a real integration problem rather than adding another format to maintain.

## Reader takeaway
Poppy 1.0 is a meaningful step toward a standard interface between personal agents and companies, with Shopify supplying an unusually broad automatic deployment path. The important test is not the partner count: it is whether independent agents can discover permitted actions and complete real tasks while company and customer controls remain intact.

## Open question
How many agents beyond Meta’s Muse will actually discover and use Poppy-enabled company capabilities in production?

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Agent Protocols](https://newruntime.com/topics/agent-protocols.md): Explore the agent-protocols topic hub.
- topic hub: [Agents](https://newruntime.com/topics/agents.md): Explore the agents topic hub.
- topic hub: [Interoperability](https://newruntime.com/topics/interoperability.md): Explore the interoperability topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Sources](https://newruntime.com/sources/): See the original sources this archive cites.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)