Sierra released version 1.0 of Personal Agent Protocol on 13 November, with Shopify publishing a Poppy file for every store on its platform and Meta’s Muse agent now looking for one first on every site it visits. The protocol is the most concrete attempt yet to separate three questions KYA practitioners keep conflating: who operates the agent, which agent is this, and what is it allowed to do here.
What happened
Sierra published v1.0 of Personal Agent Protocol — Poppy — with an implementation kit that includes a validator. Shopify has enabled it for every merchant on its platform, so stores publish the file automatically and merchants implement nothing. Shopify co-authored the protocol’s commerce extension, which lets an agent shop as a guest or sign in with the customer’s account and makes the agent ask the customer before taking certain actions.
Meta’s Muse, which more than 10 million people have set up according to The Next Web, now looks for Poppy first on every site it visits. Sierra says 60 more companies joined as design partners, taking the total past 100, including Delta Air Lines, Intuit, Salesforce and Zoom. Mercury, Synchrony and Turkish Airlines are named as live: Mercury lets an agent check balances, review transactions and initiate a payment or transfer, with the request still going through the account’s approval policy; Turkish Airlines lets an agent check fares and find business-class upgrades that the customer approves before paying.
The mechanism is worth reading in the specification rather than the announcement. A company publishes a JSON document at /.well-known/poppy.json describing its channels, capabilities and sign-in options. The agent then sends a Poppy-Session header on every request: a JWT it signs, naming the session and a user ID. The signing key is a short-lived delegated key, and a delegation signed by a key in the agent operator’s jwks_uri vouches for that key.
The user ID is a pairwise pseudonym. It is stable at one company, so the company recognises a returning user, and opaque and different at every other company, so two companies cannot match users. Account access is standard OAuth, and the specification maps sign-out to revoking the refresh token. For bot defences, it recommends a Web Bot Auth signature so an edge can authenticate the operator before application logic runs.
Why it matters for KYA
Poppy draws a line that most agent deployments blur. Operator recognition — what a CDN or WAF does when it sees a signed request — is not session identity, and neither is authorization. The specification says so directly: operator recognition alone does not verify Session claims, authorize account access, or decide whether the company accepts the request. That is the correct architecture, and it is unusual to see a vendor write it down.
The delegation chain is the part that matters for verification. A session JWT signed by a key that is itself vouched for by the operator’s published JWKS can be checked by the relying party without a shared secret or a phone call. It answers which agent is acting, for which pseudonymous user, with what key material — the three facts a User-Agent string can never supply. It also gives revocation somewhere to happen: the operator can stop vouching for a delegated key.
Read the privacy design carefully, though. The human principal stays pseudonymous. The company learns a stable pseudonym, not a legal person, so accountability in a Poppy session rests on the agent operator — the party whose JWKS signs the delegation — rather than on the user. For KYA that is defensible, because the operator is the entity you can contract with, audit and cut off. It also means a Poppy session is not a KYC record, and a merchant should not treat it as one.
The second limit is governance. Poppy is Sierra’s protocol, published with design partners, not a standards-body project. It is called version 1.0 while the specification still labels itself draft 1.0 and warns that fixes may include changes that are not backward compatible. Procurement should read that literally, and should ask what happens to a merchant’s implementation if the delegated-key format changes.
The third limit is scope enforcement. The protocol carries the claim about what an agent may do; OAuth scopes and the company’s own policy enforce it. The interesting failure mode is the gap between the two: a session that describes a narrow task and a token that permits a wider one. Poppy is a good identity layer, not a substitute for authorization design.
What to watch
- Whether other agent platforms adopt poppy.json as a discovery convention, or treat it as one more proprietary file.
- Whether the delegated-key chain gets profiled by a standards body — IETF WIMSE or OpenID — or stays Sierra-defined.
- Whether revocation propagates: sign-out kills the refresh token, but a delegated key that has already minted sessions needs an expiry story.
- Whether merchants log the pairwise user ID next to the operator identity. The pair is what makes the audit trail useful six months later.
Sources
- Sierra, “Releasing Personal Agent Protocol 1.0”, 13 November 2026 — sierra.ai
- Personal Agent Protocol, specification draft 1.0 — personalagentprotocol.org
- The Next Web, “Sierra releases Poppy 1.0 as Shopify and Meta’s Muse sign on”, 13 November 2026 — thenextweb.com
Know Your Agent (KYA) explains agent identity, verification and accountability. This is an explainer, not legal or compliance advice — see our Sources & methodology. New to KYA? Start with What is Know Your Agent? and the glossary.