MapGraphSeamsCalendarIntroductionDisclosureMethodFor agents and tools

Updated weekly, new versions on Mondays · Corrections: open an issue

Personal Agent Protocol (PAP, "Poppy"), published by Sierra with Meta

Industryspecificationcore entry

Verified 2026-10-13. Status as of 2026-10-13. All entries.

Seams: S1S3S4

Status

Draft 0.1 of the specification is published at personalagentprotocol.org (announced 2026-10-06, draft published 2026-10-09; the pages read on 2026-10-13 are marked "Updated Oct 12, 2026"), under the Apache License 2.0 with the names and the logo excluded; a further 35 design partners were named on 2026-10-09. Governance is worded two ways, not reconciled here. Sierra, 2026-10-06: "an open standard Meta and Sierra are developing along with industry partners at Genesys, Instinct, Rocket, Shopify, Stripe, and Walmart". Decagon, 2026-10-06: "join the Personal Agent Protocol working group announced by the team behind Meta's Muse to help shape an industry standard". No standards body or governing organisation is named in the pages of the site read on 2026-10-13.

Relevance

Discovery is one well-known document: "A Company MUST publish its poppy.json document at https://{domain}/.well-known/poppy.json over HTTPS". The well-known URL "MAY redirect" to where the document is hosted, and "Personal Agents MUST follow redirects, and every redirect MUST be to an HTTPS URL"; the UCP specification says the opposite for its profile (see seam S1). poppy.json is not in the Internet Assigned Numbers Authority (IANA) well-known URI registry (not found in the registry XML, 2026-10-13).

The agent is identified by a URL: "A Personal Agent's client_id MUST be an HTTPS URL that returns its metadata document", which carries a jwks_uri and a token_endpoint_auth_method of private_key_jwt; the Company can register, allow-list, block or revoke client ids. The operations extension, section 8 ("What a confirmation proves"), says what a confirmation does not show: "It doesn't prove that the User saw the terms or approved them." The announcement of 2026-10-06 says the protocol "defines how personal agents interact with businesses": it "starts on the website, where a personal agent can discover what the company offers and how to reach it", the session "is built on OAuth", and the customer decides whether the agent has read-only or write access.

Context, not part of the protocol: Retail Insight Network reported on 2026-09-23 that Shopify and Meta partnered so that Meta's assistant Muse can complete purchases across Shopify's merchants through Shop Pay.

Committed next

Boundary

The Path to 1.0 page lists as areas "the draft doesn't cover yet": payments ("How a personal agent makes payments in a way that fits the protocol, including how that works with existing payment protocols."), push notifications and attachments ("such as receipts, return labels, product images, or forms for the user to fill in").

Sources

Overlaps

Universal Commerce Protocol (UCP), Model Context Protocol (MCP), core specification

Neighbours in the map

Neighbours of Personal Agent Protocol (PAP, "Poppy"), published by Sierra with Meta in the map Each circle is an entry of the map and links to its page; the colour is the kind of body behind it, a filled circle is a core entry and a dashed circle a context entry. The entry in the middle, with the entries it overlaps and the entries named by the same seams. Overlaps (3)Share a seam (29)Model Context Protocol (MCP), core specification (Linux Foundation, context)Model Context Protocol Personal Agent Consent & Trust Protocol (PACT), published by Decagon with Instinct (Industry, core)Personal Agent Consent… Universal Commerce Protocol (UCP) (Industry, core)Universal Commerce Prot… W3C AI Agent Protocol Community Group (W3C, core)W3C AI Agent Protocol C… S1 DNS for AI Discovery (DNS-AID, draft-mozleywilliams-dnsop-dnsaid) (IETF, context)DNS for AI Discovery S1 IETF DAWN, Discovery of Agents With Names (proposed WG) (IETF, core)IETF DAWN S1 A2A protocol, agent discovery (Linux Foundation, core)A2A protocol S1 AI Catalog (Agent Card Working Group) (Linux Foundation, core)AI Catalog S1 Agent2Agent (A2A) protocol, core specification (Linux Foundation, context)Agent2Agent S1 MCP Server Cards (ext-server-card, SEP-2127) (Linux Foundation, core)MCP Server Cards S1 Agentic Resource Discovery (ARD) (Independent, core)Agentic Resource Discov… S1 schema.org vocabulary for products, offers, sellers and lodging (current release) (Independent, context)schema.org vocabulary f… S1 Shopify, MCP surfaces for buyer agents, developers and merchants (Industry, context)Shopify S1 S4 W3C Agentic Web Working Group (draft charter) (W3C, core)W3C Agentic Web Working… S3 WebMCP (Draft Community Group Report, Web Machine Learning CG) (W3C, context)WebMCP S3 IETF Web Bot Auth (webbotauth WG) (IETF, core)IETF Web Bot Auth S3 IETF agentproto (Agent Communication Protocols WG) (IETF, core)IETF agentproto S3 x402 (Linux Foundation, core)x402 S3 S4 Browser vendor positions on WebMCP (WebKit, Mozilla, Chrome, Edge) (Independent, core)Browser vendor position… S3 S4 OpenID Foundation AuthZEN Working Group (agent authorization drafts AARP and COAZ) (Independent, context)OpenID Foundation AuthZ… S3 Agentic Commerce Protocol (ACP) (Industry, core)Agentic Commerce Protoc… S3 S4 KYAPay (Skyfire) (Industry, core)KYAPay S3 Mastercard Agent Pay (Industry, core)Mastercard Agent Pay S3 Visa Trusted Agent Protocol (TAP) (Industry, core)Visa Trusted Agent Prot… S3 IETF vcon (Virtualized Conversations WG) (IETF, core)IETF vcon S4 Payment HTTP Authentication Scheme (draft-httpauth-payment, Tempo Labs and Stripe) (IETF, context)Payment HTTP Authentica… S4 AAIF Agentic Commerce Working Group (AAIF, core)AAIF Agentic Commerce W… S4 EMILIA Protocol (individual drafts and open-source gate) (Independent, context)EMILIA Protocol S4 Agent Payments Protocol (AP2) (Industry, core)Agent Payments Protocol S4 EMV Agentic Payments Framework for Specifications (draft for public feedback) (Industry, core)EMV Agentic Payments Fr… S4 FIDO Alliance agentic authentication and payments work (Industry, context)FIDO Alliance agentic a… S4 Verifiable Intent (Industry, core)Verifiable Intent S4 Personal Agent Protocol

Solid lines: overlaps declared by one of the two entries. Dashed lines, coloured by seam: entries named by the same seam (S1 to S4) in the seams note. Every node is a link.

Evidence and coverage

Read
On 2026-10-13: the specification, the operations extension, the extensions page, the Path to 1.0 page, the home page and the licence page of personalagentprotocol.org (each marked "Updated Oct 12, 2026" where the page carries a date), the Sierra blog of 2026-10-09, the Decagon blog of 2026-10-06 and the IANA well-known URI registry XML. On 2026-10-08: the Sierra announcement of 2026-10-06 in full, one trade article on it and one on the Shopify and Meta agreement.
Not read
The sections of the specification beyond the discovery, agent identity and confirmation texts quoted, the PACT specification, any Meta publication on the protocol, the TechRepublic article on Meta's Muse (not retrievable on 2026-10-08).
Not found
Not found, 2026-10-13: poppy.json in the IANA well-known URI registry XML; a standards body, foundation or working group in the pages of the site read (home, specification, extensions, operations, Path to 1.0, licence); UCP, A2A and Web Bot Auth in the same pages.