Poppy 1.0: a valid discovery file is not a verified company.
Sierra expands its personal-agent protocol. Domain identity, browser scope and rollout claims still need their own checks.

Concept photo: programming code on a screen, by luis gomes / Pexels. Illustrates programmable tools, not a Poppy product screenshot. Used under the Pexels license, which permits article, RSS and social reuse. No endorsement implied.
The welcome mat can be genuine and still sit outside the wrong shop. That is the useful warning inside Poppy's latest documentation: a company name in a discovery file is not proof that the domain belongs to that company.
Sierra announced Personal Agent Protocol 1.0 on November 13, saying Shopify now publishes a Poppy file for every store and Meta's Muse looks for the protocol first. Poppy gives personal agents a common way to discover a company's APIs, website and company agent. The opportunity is less guesswork at the front door. The remaining job is knowing whose door it is.
A valid file is not a verified brand
The current specification ties discovery to the HTTPS host serving the well-known file, checks that its declared domain matches, and links an OAuth issuer back to that domain when account sign-in exists. Those are useful consistency checks. They do not turn a familiar-looking company name into an identity certificate.
The official changelog's lookalike-domain clarification is unusually direct: a lookalike can pass every discovery check. Choosing the company the user actually meant remains the personal agent's responsibility. For an operator, that means resolving the destination before sign-in or disclosure, rather than trusting the logo, display name or successful discovery response.
Three different kinds of permission
Poppy also separates recognition of the agent operator, continuity of a session, and access to a customer account. The specification says operator recognition alone neither verifies session claims nor authorizes account access. OAuth handles account authorization separately. Treating those layers as one green badge would erase the distinction the protocol is making.
Browser access deserves its own check. The documented web.unscoped flag means the website does not apply the company's other scopes: browser sign-in can give the account's full access there. A narrowly scoped API connection therefore is not automatically evidence of an equally narrow signed-in website. Check the actual channel and consent being requested.
Read the rollout verbs
Sierra's examples do not all mean the same thing. Its announcement says Mercury payment or transfer requests go through the account's approval policy before sending. Turkish Airlines customers can approve upgrades, while completing a purchase inside the conversation is still being developed. Synchrony's description concerns work exploring financing and rewards. Those are different stages, not a blanket claim that every announced partner supports every transaction.
There is a version wrinkle, too. Sierra calls this a 1.0 release; the specification fetched for this review still calls itself draft 1.0, and the changelog says it is in progress. The Next Web also notes that mismatch. Record the revision actually implemented rather than assuming the announcement makes every document final.
This is a documentation-led review, not a GigSoul interoperability test. Poppy can make a company's interfaces easier to find. Before an agent acts, the checklist is still concrete: right domain, right account, right channel, and the user's approval for the actual job.


