Poppy:
what's announced,
what's still missing.
Poppy (Personal Agent Protocol) is an open standard Sierra and Meta announced on October 6, 2026. It sets out how your AI agent signs in to a business and acts for you. You choose what access to grant. The business chooses the route. Versions 0.1 and 0.2 are public, and draft 0.3 is in progress; all are drafts before 1.0.
poppy.md is an independent tracker, not affiliated with Sierra, Meta or the partners. We link every partner, date and claim to its source, and track what the draft says as it changes.
The customer picks access
Read-only or write. That’s the whole menu for now; finer limits are on the "later" list.
Sessions run on OAuth
Sign in on the company’s own page, or use credentials already set up with the agent. A guest visit is fine for stock checks.
The business picks the route
Its website, an API such as MCP or OpenAPI, or its own agent when the job needs a conversation.
Poppy in ten lines
Everything here comes from Sierra's post or named coverage. If it isn't sourced, it isn't on the list. Checked Nov 1, 2026.
How we got here: the timeline- Name
- Poppy (Personal Agent Protocol)
- Announced
- October 6, 2026, at Sierra Summit, San Francisco
- Created by
- Sierra (Bret Taylor, Clay Bavor) and Meta
- What it covers
- How a personal AI agent signs in to a business and what it may do there
- Auth
- OAuth sessions; guest or signed in
- Access levels
- Read-only or write, chosen by the customer
- Routes
- Company website, APIs (MCP, OpenAPI), or the company’s own agent
- Spec
- Draft 0.3 in progress since October 25, 2026 · version 0.2 published October 24, 2026 (frozen) · version 0.1 published October 9, 2026 (frozen) · Apache 2.0 · official repo on GitHub
- Not covered yet
- Payments, push notifications, attachments, self-hosted personal agents (open topics on the Path to 1.0)
- Not named as partners
- Anthropic, Google, Amazon
How the Personal Agent Protocol works
You, your agent and the company share one visit. The draft now defines discovery, sign-in, sessions and the routes companies can offer.
Discover on the site
The agent finds what the company offers and how to reach it. A guest session can check stock or a returns policy.
You choose access
If the task needs your account, you sign in. You decide read-only or write. The visit stays the same.
The company picks a route
Website pages, an API such as MCP or OpenAPI, or the company’s own agent.
Draft 0.1 defines the details
Draft 0.1 specifies discovery at /.well-known/poppy.json, OAuth sign-in, session tokens and the API and conversation routes. It can still change before a stable release.
Where Poppy fits next to MCP, A2A, UCP, ACP, TAP and PACT
Agents already have a protocol for tools, one for talking to each other, two for shopping and one for proving who they are. Poppy adds the customer's permission. Here's where each one ends.
Poppy vs MCP
Low overlapModel Context Protocol · Anthropic
Tools and data an AI app can call
Read the comparisonPoppy vs A2A
Some overlapAgent2Agent · Google, now a Linux Foundation project
How two agents talk to each other
Read the comparisonPoppy vs UCP
Some overlapUniversal Commerce Protocol · Google, with Shopify and retailers
The shopping flow: discovery, checkout, after-sale
Read the comparisonPoppy vs ACP
Some overlapAgentic Commerce Protocol · OpenAI and Stripe
In-agent checkout and payment tokens
Read the comparisonPoppy vs TAP
High overlapTrusted Agent Protocol · Visa and Cloudflare
Proving an agent’s identity on each request
Read the comparisonPoppy vs PACT
High overlapPersonal Agent Consent & Trust Protocol · Decagon and Instinct
Agent identity and customer authority, agent-to-agent
Read the comparisonMore than the launch lists
Sierra and Meta's October 6 launch lists differ. On October 9, Sierra announced 35 additional design partners, including OpenAI, Cloudflare, Visa and Zendesk.
| Company | Role | Sierra post | Meta post |
|---|---|---|---|
| Sierra | Co-creator | ||
| Meta | Co-creator | ||
| Genesys | Launch partner | ||
| Rocket Companies | Launch partner | ||
| Shopify | Launch partner | ||
| Stripe | Launch partner | ||
| Walmart | Launch partner | ||
| Instinct | Launch partner | ||
| NiCE | Partner | ||
| Decagon | Working group |
Not named on the October 6 lists: Anthropic, Google, Amazon. Meta's list as reported by CMSWire.
35 additional design partners
The cohort includes OpenAI, Cloudflare, Mastercard, Notion, Visa and Zendesk, among others.
See all 35 design partnersSierra’s October 9 announcementQuestions people keep asking
Is the Poppy specification published?+
Yes. Version 0.1 was published on October 9, 2026 under Apache 2.0 and is frozen at /docs/0.1/spec. Version 0.2 was published on October 24, 2026 and is frozen at /docs/0.2/spec, where /docs/spec now points; its changelog marks the changes that can break a 0.1 implementation. Both are drafts before 1.0, so a later version can still change any part. Draft 0.3 has been in progress at /docs/spec since October 25, and its changelog already lists changes that break 0.2 implementations.
Are OpenAI, Anthropic, Google or Amazon part of Poppy?+
OpenAI joined as a design partner on October 9, 2026. Anthropic, Google and Amazon are not named in the partner announcements.
Does Poppy handle payments?+
Not in the announced first version. Payment extensions, letting an agent buy without sharing card details, are listed as a possible later step. On October 20 Sierra wrote that it is working with Stripe and other partners on how payments should work when a personal agent deals with a business; no details or extension text are public yet.
Does Poppy replace MCP?+
No. The announcement names MCP and OpenAPI as API routes a company can offer inside a Poppy session.
Building for agents against the draft?
Start with the published endpoints and scopes, then check the tracker for open questions and changes to the draft.