How does Personal Agent Protocol (Poppy) compare to other identify protocols?

Personal Agent Protocol (Poppy) is one of 14 standards at step 2, Identify (Who is this agent? Who is this site?). It pairs with Model Context Protocol, OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization), Identity Assertion JWT Authorization Grant, Agent Payments Protocol. It builds on OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization). Every standard at this step is listed at https://agenticweb.wiki/category/identify/.

Personal Agent Protocol (Poppy) Poppy

2 · Identify

Personal Agent Protocol (Poppy)
Category	Identify
Governed by	Sierra with design partners including OpenAI, Visa, Mastercard and Okta; no standards body named
Status	Draft published 2026-10-09; reference implementation promised
Phase	draft
Implementation	none found
Adoption	unmeasured
Version	draft (2026-10-09)
Specification	https://sierra.ai/blog/poppy
Found at	/.well-known/poppy.json
Last checked	2026-10-16
Freshness	current · checked 2026-10-16
Solves	Prove an agent's identity, Delegate a user's authority to an agent, Let agents discover my API or service

Personal Agent Protocol (Poppy) is an agentic-web standard (endpoint) at step 2, Identify, governed by Sierra with design partners including OpenAI, Visa, Mastercard and Okta; its own status is "Draft published 2026-10-09; reference implementation promised" (draft). It answers: How does a customer's personal agent identify itself to a business and show it has the customer's permission to act? Adoption is unmeasured, last verified 2026-10-16.

Identify The Personal Agent Protocol, nicknamed Poppy, is a draft from Sierra with Meta and others for how a customer's personal agent identifies itself to a business and receives the customer's permission ^[1]. Companies publish one discovery file at /.well-known/poppy.json; Sierra says the protocol is built on OAuth, JWT, OpenAPI and MCP and names 35+ design partners including OpenAI, Visa, Mastercard and Okta ^[1].

Overview

The draft was published on 2026-10-09 and a reference implementation is promised, not yet seen ^[1]. No standards body is named. The step placement is a judgement: it covers both identification and permission, and sits at identify here.

Everything above is Sierra's own account in a single announcement.

Discovery and probe

Well-known file published by the company · /.well-known/poppy.json

GET {origin}/.well-known/poppy.json
parse:     A JSON document means the company publishes a Personal Agent Protocol discovery file; the draft's schema for its contents was not reviewed for this record.
on absent: 404 or non-JSON means no Poppy discovery file is published at that origin.

Not probed live: no-fixed-path. candidate record; probe rule pending

History

2026-10-15 — curated update 2026-10-15; placement at the identify step is a judgement, permit is the alternative
2026-10-16 — discovery path /.well-known/poppy.json and the protocol site added from the Sierra announcement
2026-10-16 — use-case tags (auto)

Instances

No instances recorded yet.

References

personalagentprotocol.org describes the protocol: personal agents discover participating companies, sign users in, and get things done through APIs, web pages and company agents. — https://personalagentprotocol.org/ (2026-10-09) VERIFIED
Sierra's announcement (2026-10-09) presents the Personal Agent Protocol draft as built on OAuth, JWT, OpenAPI and MCP, with 35+ design partners including OpenAI, Visa, Mastercard and Okta, and promises a reference implementation. Discovery is one file at /.well-known/poppy.json; sessions, OAuth sign-in and one token across APIs, website and company agent are the other building blocks. — https://sierra.ai/blog/poppy (2026-10-09) VERIFIED

JSON · Markdown