Steward
Sierra and Meta, with more than 100 listed design partners; specification and repository under the Apache License 2.0 (personalagentprotocol.org)
Status
Version 1.0 published, draft 1.1 in progress since 2026-11-17; early live use reported by Sierra (Muse, Shopify stores, several named companies); the core specification does not cover payments yet
Latest version
Personal Agent Protocol 1.0 (announced 2026-11-13; the changelog dates the frozen 1.0 text 2026-11-14) ()
Primary source
Personal Agent Protocol specification (version 1.0) (external link)

What it is

Personal Agent Protocol (PAP), Poppy for short, defines how a personal agent acting for one user works with a company on that user’s behalf. It covers discovery, identity, account access, and interaction through the company’s APIs, its website or its own agent. Source [1] A company publishes a poppy.json document at /.well-known/poppy.json, which tells agents how to start sessions, how users sign in, and which APIs and company agent it offers. Source [1]

The agent then sends a Poppy-Session header on every request to the company’s APIs and protocol endpoints. The header holds a JSON Web Token (JWT) that the agent signs for that one request. It names the session and a user ID that differs at each company, so companies cannot match one user across sites. The agent signs it with a short-lived delegated key, which a key from the agent’s published jwks_uri vouches for. Source [1] Account access is separate and uses OAuth: the user approves access on the company’s own page (Direct Sign-In) or on any device with a link and a code (Device Sign-In), and signed-out use needs no OAuth server at all. Source [1] Sierra describes the protocol as built on OAuth, JWTs, HTTPS, OpenAPI and the (MCP). Source [2]

Operator identity reuses Web Bot Auth. A personal agent should also sign each request that carries the session header with an RFC 9421 HTTP Message Signature, so that bot defenses can recognize the operator before the request reaches the company’s application. That signature must cover poppy-session and, when present, authorization. The specification treats it as compatibility support: a missing operator signature does not make a session invalid. Source [1, 3]

Version 1.0 lists six : Browser Control, Disclosures, Links, Mediated Sign-In, Operations and UCP. Source [4] The core specification does not cover payments yet: the roadmap in the project’s introduction names payments, push notifications and attachments among the areas it does not cover, and the project plans to remove the transitional Mediated Sign-In extension, in which the agent signs in with the user’s own credentials, on 2027-03-17 (as of 2026-11-21). Source [4, 5] A company that uses the UCP extension takes payment through UCP checkout instead. Source [6]

Status

Sierra announced the protocol on 2026-10-06 as an open standard it is developing with Meta, with Genesys, Instinct, Rocket, Shopify, Stripe and Walmart as industry partners. Source [7] On 2026-10-09 it published draft 0.1 under the short name Poppy and named 35 more design partners, among them Adyen, Cloudflare, Mastercard, OpenAI, PayPal and Visa. Source [2, 8] Drafts 0.2 (2026-10-24), 0.3 (2026-11-04) and 0.4 (2026-11-10, the release candidate) followed, each frozen at its own URL. Source [4, 8]

Sierra announced version 1.0 on 2026-11-13. The project’s changelog gives 2026-11-14 as the publication date of the frozen 1.0 text and describes it as 0.4 with the fixes that implementers needed. Source [8, 9] In its 1.0 post Sierra says that Shopify has turned Poppy on for every merchant, so every Shopify store publishes a Poppy file, and that Meta’s Muse agent now looks for Poppy first on every site it visits. It names Mercury, Synchrony and Turkish Airlines among the design partners going live, and it added 60 design partners, for more than 100 in total, including Affirm, Checkout.com, Global Payments and Salesforce. Source [9] These are Sierra’s statements about its partners’ products.

On 2026-11-17 the project started draft 1.1, which it labels unfinished and not meant for implementations yet; 1.0 stays the version to build against. Source [4, 8, 10] Its changelog so far adds rules for replacing a user ID, listed tasks in feedback and the offline_access scope, and a recommendation that a personal agent also sign its requests to the company’s authorization server endpoints with its Web Bot Auth operator signature, covering content-digest. Source [8]

The project’s Path to 1.0 page, updated 2026-11-14, listed 103 design partners that agreed to be listed: four personal agents (Instinct, Manus, Meta and OpenAI) and 99 companies. Source [11] On 2026-11-16 the project folded that page and its roadmap into the introduction, which now has one alphabetical list of 102 design partners and no longer separates personal agents from companies; Instinct is the one name no longer listed, and the project gives no reason (as of 2026-11-21). Source [5, 12] A design partner takes part in shaping the specification; the list does not show that a partner has implemented it. The GitHub repository was created on 2026-10-14 under the Apache License 2.0 and had no tags or releases on 2026-11-21. Source [13]

How it relates to the eight

UCP is the one protocol of the eight that PAP builds on. PAP’s ucp divides the work: PAP finds the company, identifies the personal agent and a pseudonymous user, and signs the user in, while UCP is the business protocol for the shopping once the agent is there. UCP’s business, platform and buyer are PAP’s company, personal agent and user. The agent reads the at /.well-known/ucp next to poppy.json and sends the session header on its UCP requests, and one RFC 9421 signature can serve both protocols when it covers the components that each one requires. The extension also lets a company list UCP’s Ask as a way to talk to its agent. Source [6] Sierra says Shopify co-authored this commerce extension. Source [9]

No relation to ACP is documented. The 1.0 specification, its UCP extension, its changelog and Sierra’s three posts never mention the Agentic Commerce Protocol (searched 2026-11-14). Source [1, 2, 6, 7, 8, 9] The overlap is organizational. Stripe, one of ACP’s two founding maintainers, was among PAP’s first industry partners; Meta, which co-develops PAP, holds a seat on ACP’s technical steering committee; and OpenAI is a listed design partner. Source [5, 7, 14, 15]

Visa and Mastercard are design partners as well, but the 1.0 specification names none of Visa TAP, Mastercard Agent Pay, MPP, x402, AP2 or ERC-8004 (searched 2026-11-14). The core specification leaves payment out for now; through the UCP extension, payment runs in UCP checkout. Source [1, 2, 5, 6] Separately, mppx, the TypeScript software development kit (SDK) for MPP, added a Poppy identity provider in 0.19.1 (2026-11-16): its server verifier checks the agent’s Poppy-Session token, its delegation and the agent’s published keys before it issues any payment challenge. That is a feature of the SDK, not part of the MPP or PAP specifications. Source [16]

Status history

Relations at a glance

How Personal Agent Protocol (Poppy) relates to each protocol
ProtocolRelationNote
UCPComplementsPAP's ucp extension, which Sierra says Shopify co-authored, lets PAP find the company, identify the agent and a pseudonymous user and sign the user in, while the shopping itself (catalog, cart, checkout, orders and Ask) runs over UCP.
Agentic Commerce Protocol (ACP)Same stewardNo documented technical relation, and PAP never names ACP. The overlap is organizational. Stripe, an ACP founding maintainer, was among PAP's first partners; Meta co-develops PAP and holds an ACP steering committee seat; OpenAI is a listed PAP design partner.

Back to the orbit

Sources

  1. Personal Agent Protocol specification (version 1.0) (external link)Personal Agent Protocol project (Sierra and Meta with design partners). Specification, primary source. Published . Accessed .
  2. Sharing a draft of Personal Agent Protocol (external link)Sierra. Announcement, primary source. Published . Accessed .
  3. draft-ietf-webbotauth-httpsig-protocol-01: HTTP Message Signatures for automated traffic (external link)IETF Web Bot Auth working group. Standard, primary source. Published . Accessed .
  4. Personal Agent Protocol documentation index (llms.txt) (external link)Personal Agent Protocol project. Documentation, primary source. Accessed .
  5. Introduction (Personal Agent Protocol) (external link)Personal Agent Protocol project. Documentation, primary source. Accessed .
  6. UCP extension (Personal Agent Protocol 1.0) (external link)Personal Agent Protocol project. Specification, primary source. Accessed .
  7. Introducing Personal Agent Protocol (external link)Sierra. Announcement, primary source. Published . Accessed .
  8. Personal Agent Protocol changelog (external link)Personal Agent Protocol project. Documentation, primary source. Accessed .
  9. Releasing Personal Agent Protocol 1.0 (external link)Sierra. Announcement, primary source. Published . Accessed .
  10. [md] Start draft 1.1, and default readers and the kit to the latest published version (#201) (external link)Personal Agent Protocol project (GitHub). Repository, primary source. Published . Accessed .
  11. Path to 1.0 (Personal Agent Protocol) (external link)Personal Agent Protocol project. Documentation, primary source. Accessed .
  12. [md] Fold Path to 1.0 and the roadmap into the introduction, and archive 0.1 and 0.2 (#199) (external link)Personal Agent Protocol project (GitHub). Repository, primary source. Published . Accessed .
  13. personal-agent-protocol/personal-agent-protocol (external link)Personal Agent Protocol project (GitHub). Repository, primary source. Published . Accessed .
  14. Agentic Commerce Protocol (ACP) README (external link)OpenAI and Stripe (agentic-commerce-protocol GitHub organization). Repository, primary source. Accessed .
  15. Agentic Commerce Protocol (ACP) Governance (external link)Agentic Commerce Protocol project. Repository, primary source. Published . Accessed .
  16. mppx CHANGELOG.md (identity changes in 0.16.0 to 0.20.1) (external link)wevm. Repository, primary source. Accessed .

Source details

    Loading the index.

    Enter open Esc close ? shortcuts