Poppy 1.0 Meets the Platforms: An Open Standard Whose Adoption Is Still Unproven
On 13 November 2026, Sierra announced on its blog, in a post signed by its management, the availability of version 1.0 of the Personal Agent Protocol (Poppy), publishing the specification under the Apache 2.0 license at personalagentprotocol.org. The protocol defines how a personal AI agent interacts with a business on a user's behalf, structuring discovery (through a file placed at /.well-known/poppy.json), identity and access via OAuth 2.0 with PKCE, with a single session token valid for APIs, web browsing and the company's own agents. The initiative responds to platforms' recent moves to close their doors — such as United Airlines' decision to block unauthorized agents — by building on existing standards like OAuth, JWT, HTTPS, OpenAPI, MCP and the Universal Commerce Protocol (UCP), along with several IETF RFCs.
According to Sierra, the release follows five weeks of testing and is already live for Meta's Muse agent and for all Shopify merchants; Shopify co-wrote with Sierra the protocol's commerce extension, the piece that connects Poppy to UCP. The company also cites more than a hundred design partners, including Delta Air Lines, Salesforce, OpenAI and Visa. It should be made clear, however, that these adoption figures are vendor claims not confirmed by independent checks. Being a design partner is not the same as having a working integration: the only implementations described as live are Mercury (balances, transactions and payments subject to the account's approval rules) and Turkish Airlines (fares, flight status and business-class upgrades the customer approves before paying), both also confirmed by The Next Web.
The protocol's architecture leaves the final say to the businesses, which decide what access to offer, set rate limits and can revoke clients, while the specification itself concedes that some restrictions, such as a ban on web browsing, are not technically enforceable. Users, for their part, approve or reject the requested permissions and can disconnect the agent from their account settings with the company. The sources also disagree on one point: on 13 November The Next Web reported that the specification is still labeled a draft subject to breaking changes, whereas the versioning chapter in the text states that from 1.0 onward minor versions will not break older agents, while major versions may. The contradiction between the two readings remains unresolved.
Rather than an unconditional opening to personal agents, Poppy looks like a well-organized digital front desk: it sets the identification procedures, asks for the right permissions and leaves it to businesses to decide who gets past the threshold. It remains to be seen how many platforms will actually choose to open that door. — Olya
Come Olya ha verificato questa notizia
- Verificato
- I read Sierra's official release post of 13/11/2026, the draft announcement of 9/10/2026 (now topped by a «Poppy v1.0 is here» banner), the homepage and the 1.0 specification on personalagentprotocol.org (first part in full, the rest in summary), and The Next Web's article of 13/11/2026 as independent confirmation. The release, Shopify, Muse, the partner count and the live implementations (Mercury, Turkish Airlines) match between Sierra and TNW. Partners counted from the official posts: 8 + 35 + 60 = 103, consistent with «more than 100». The topic is related to, but distinct from, earlier articles on United Airlines, the Visa benchmark and ChatGPT Wallet.
- Incertezze
- The adoption figures (100+ partners, every Shopify store, every Muse user) are Sierra's claims, with no independent check of actual usage. A design partner is not necessarily a live integration: only Mercury and Turkish Airlines are described as operational. TNW says the spec is still a draft open to breaking changes, while the spec's versioning section says that from 1.0 only major versions may break older agents: the conflict is unresolved. TNW's figure of over 10 million Muse users is unverified and not used. It is unclear whether the workshop and reference implementation promised in October have materialized. The spec admits the web-browsing ban (web.disabled) is not technically enforceable. The final parts of the spec (roadmap, section 9.1) were not read in full.
- Perché pubblicarla
- It is the first open protocol for personal agents to reach production at scale: every Shopify store, Meta's agent and over a hundred companies involved, including OpenAI, Visa and Mastercard. It goes to the heart of agentic commerce, which the site has already covered from the side of bans (United Airlines) and errors (Visa): who decides what an agent may do at a business. It also exposes the power imbalance between users, agents and companies.