Poppy, the protocol between a personal agent and a company
The cut that interests me here is the personal agent arriving at a company, with discovery, identity and account access on the same thread. That is the cut of Personal Agent Protocol, or Poppy, in the protocols index.
What the protocol describes
On the canonical site, the introduction presents Poppy as an open protocol for how personal agents and companies work together. A company uses it to declare how personal agents can interact with it. A personal agent uses it to sign in safely and get access to a person's account, limited to what that person and the company agree to.
The specification widens the same cut: the protocol 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 interactions across APIs, web browsing and conversations with the Company Agent. The introduction lists five principles: Built on existing standards, with OAuth, JWTs, HTTPS, OpenAPI and MCP wherever they fit; Controls, not policy; Secure and private; Progressive adoption; Extensible. The introduction also states that the protocol defines something new only where no standard covers the need.
Version, stewardship and the two attributions
There is a tension here that I leave in the open, with both attributions, and without a verdict of my own. Sierra, in the post «Releasing Personal Agent Protocol 1.0», states that v1.0 of the protocol is now available. On the canonical site, the specification opens with the sentence «This is draft version 1.0», starting from the 0.4 release candidate, and it can include fixes that are not backward compatible. The Path to 1.0 page asks implementers to build against the 1.0 draft, the latest version, and writes that no new features are added until 1.0 is published. The changelog titles the current version Draft 1.0 and says the list grows until 1.0 is published. The README of the canonical repository states that the specification is a draft. The official poppy.json example uses "protocol_version": "1.0", and the spec, in section 3.1, says this draft is 1.0.
The canonical home of the documentation and the kit is personalagentprotocol.org and the repository https://github.com/personal-agent-protocol/personal-agent-protocol. The specification and documentation, including their examples, are licensed under the Apache License 2.0. The license, according to the site itself, does not cover the names Personal Agent Protocol and Poppy, the logo, or the design of the site. Path to 1.0 and the roadmap still list areas the draft does not cover yet, including payments, push notifications and attachments. The official implementation path is the spec, the guides and the company kit at /kit/company.
How to use it: the flow in the specification
I follow the flow the spec describes. A Company MUST publish its poppy.json document at https://{domain}/.well-known/poppy.json over HTTPS. Redirects only over HTTPS; the document counts only if the final URL has the path exactly /.well-known/poppy.json and no query. The organization.domain field must be the host that served the document. At least one channel, among agent, apis or web, is required. Adoption can be progressive: a company can start with the website only, with APIs only or with the agent only.
If the company offers an account, it must have an OAuth issuer. Without an issuer, it can offer signed-out sessions. The issuer is found through protected resource metadata at https://{organization.domain}/.well-known/oauth-protected-resource. Account access is plain OAuth, as the spec describes it. There is no separate step to start a Session: the first request with a new sid starts it. The Personal Agent declares the session with the Poppy-Session header, a JWT signed per request. Signed-out requests carry only the session header. Signed-in requests carry the session header and the access token. Poppy-Version also travels, and Poppy-Extensions when extensions are in use.
The interaction channels are the website, OpenAPI or MCP APIs, and conversations with the Company Agent. In the APIs, the types defined in this version of the spec are openapi, pointing to an OpenAPI 3.0 or 3.1 description, and mcp, pointing to a remote MCP server endpoint, using the Streamable HTTP transport and MCP version 2025-06-18 or later. Poppy Sessions are independent of MCP's transport lifecycle. The layers in table 1.1 of the spec are Discovery, Operator recognition (with Web Bot Auth recommended), Sessions, Account access (OAuth) and Interaction channels.
There are optional extensions in this 1.0 draft, including ucp. The official Universal Commerce Protocol extension, on the protocol site, describes the fit this way: this protocol finds the Company, identifies the Personal Agent and a pseudonymous User, and signs the User in; UCP is the business protocol for how a Personal Agent shops once it is there. UCP's Business, Platform and Buyer are, in that extension, this protocol's Company, Personal Agent and User. The protocol changelog records that Personal Agents choose their Companies, and that implementing Poppy does not require using it with every Company that publishes poppy.json.
An official example
The example below comes from the official specification, section 3, at https://personalagentprotocol.org/docs/1.0/spec.md. The source presents it as an example document, poppy.json, published by the Company. The spec itself warns that the examples use example.com for the Company and agent.example for the Personal Agent, and that tokens, keys and codes in the examples are shortened placeholders, not real values.
{
"protocol_version": "1.0",
"organization": {
"name": "Example Company",
"domain": "example.com",
"logo_uri": "https://example.com/logo.png"
},
"auth": {
"scopes": {
"orders:read": "See your orders, returns, and bookings. Needed to track an order or find one to change",
"orders:write": "Exchange or return items, and change bookings. Needed for any change to an order",
"addresses": "See and change your saved shipping addresses. Not needed to enter an address at checkout",
"poppy:browser-sign-in": "Use the website signed in, with the other access you approve"
},
"scope_hints": {
"orders:read": { "changes": "none", "personal_data": true },
"orders:write": { "changes": "irreversible", "personal_data": true },
"addresses": { "changes": "reversible", "personal_data": true }
}
},
"agent": {
"protocols": [
{
"type": "poppy",
"endpoint": "https://api.example.com/poppy/conversations",
"description": "Anything about your orders, returns, account, and our products"
}
]
},
"web": {
"browser_session_endpoint": "https://example.com/poppy/browser-session"
},
"tasks": {
"endpoint": "https://api.example.com/poppy/tasks"
},
"apis": [
{
"type": "openapi",
"url": "https://api.example.com/openapi.json",
"description": "Orders, returns, and exchanges"
},
{
"type": "mcp",
"url": "https://mcp.example.com/mcp",
"description": "Product search and sizing"
}
]
}
The following excerpt is the official request-headers example in section 5.2 of the same specification («The Session header»), labeled in the source as «Request headers: Personal Agent → Company». In that source, the example includes the access token in the Authorization header. The tokens remain truncated, as in the source.
Poppy-Session: eyJ0eXAiOiJwb3BweS1zZXNzaW9uK2p3dCIs…
Poppy-Version: 1.0
Authorization: Bearer eyJhbGciOi…Qp4w
The official example with the Poppy-Extensions header is in section 3.4 («Versions») of the same specification, also labeled «Request headers: Personal Agent → Company»:
Poppy-Session: eyJ0eXAiOiJwb3BweS1zZXNzaW9uK2p3dCIs…
Poppy-Version: 1.0
Poppy-Extensions: "operations";v="3", "links";v="1"
Relation to MCP, OpenAPI and UCP
The official introduction places Poppy on existing standards, OAuth, JWTs, HTTPS, OpenAPI and MCP, wherever they fit. The spec leaves each API's schema to that API, and requires every listed API to accept the session header and, when there is account access, the access tokens, and to enforce the scopes. The fit with UCP is in the official extension I cited above.
I will not collapse Sierra's announcement and the canonical site's draft language into a single verdict. The operational flow I follow is the one in the specification, and the index is where this page sits on the map.