Summary: Personal Agent Protocol 1.0, nicknamed Poppy, is a published standard for how a personal AI agent finds a company, says who it is acting for, and learns what it may do there. Shopify says every store on its platform now publishes a Poppy file automatically. This tutorial shows what that file contains, how to read each field, and one thing we noticed when we fetched real store files on November 17, 2026: they still declare version 0.4, not 1.0.
If you run a Shopify store, you did not have to do anything to get this file. If you build agents, it is the first thing your agent can read at a store before it touches a cart. Either way, it is worth ten minutes to understand what it says about your store, because it describes how much an agent is allowed to do and which actions count as serious.
What Poppy is, in one paragraph
Sierra published version 1.0 of the protocol in mid-November 2026, and the official changelog describes 1.0 as "0.4 with the fixes implementers needed." The protocol sits between two extremes that exist today: a company blocking every agent, or an agent acting with the person's full account access. Poppy gives the company a middle ground. It publishes a machine-readable document that lists its channels (a company agent, APIs such as OpenAPI or MCP, or the website), the scopes of account access an agent can request, and optional extensions. According to Sierra's announcement, Shopify co-authored a commerce extension that links Poppy to the Universal Commerce Protocol (UCP): UCP handles the shopping itself, while Poppy handles the step before it, when an agent arrives and finds out what it may do.
Step 1: Find the file
The spec fixes the location. A company must publish the document over HTTPS at:
https://{domain}/.well-known/poppy.json
To look at one yourself, open that URL in a browser for any Shopify store's main domain, or run this in a terminal (replace the domain):
curl -sL https://www.example-store.com/.well-known/poppy.json | python3 -m json.tool
Two rules from the spec matter when you check the result:
- Redirects are allowed, but the final path must be exactly
/.well-known/poppy.jsonwith no query string. An agent must ignore a document that ends up anywhere else, so an uploaded file somewhere on the domain cannot speak for the company. organization.domainmust match the host that served the file. A copy of the file on another domain is not valid for the original store.
Not every store answered. One large brand we tried returned an HTML error page instead of JSON; we did not confirm why. If you see HTML instead of JSON, the file is not being served at that domain.
Step 2: Read the fields, top to bottom
Here is what we got back from three Shopify stores (Allbirds, Kylie Cosmetics and Tentree) on 2026-11-17. All three had the same shape, so we use one as the example, shortened only by line breaks:
{
"protocol_version": "0.4",
"organization": {"name": "Allbirds", "domain": "allbirds.com"},
"auth": {
"scopes": {"dev.ucp.shopping.checkout:manage": "Lets the agent prepare checkouts ... the buyer completes the purchase. ..."},
"scope_hints": {"dev.ucp.shopping.checkout:manage": {"changes": "irreversible", "personal_data": true}}
},
"agent": {"protocols": [{"type": "ucp", "endpoint": "https://allbirds.com/.well-known/ucp"}]},
"web": {},
"extensions": {"ucp": [{"version": "1"}]}
}
protocol_version
Required. The 1.0 spec says the document follows a version written as major.minor, and an agent uses the document only if that version is compatible with one it implements. The catch is in section 3.4: two versions are compatible when they share the major version and, before 1.0, the same minor version. So a file that says "0.4" is not compatible with an agent that implements only 1.0. An agent built strictly to the 1.0 text, and only to it, should not use these store files as they stand. This is likely a transition state (the 1.0 text was published only days ago), so recheck before you rely on it.
organization
Required. The display name and domain. The only thing to check is that the domain equals the host you fetched, for example allbirds.com for the file served at allbirds.com, and www.tentree.com for the one at www.tentree.com.
auth.scopes and auth.scope_hints
This is the part that describes how much an agent can do. Each scope is a named piece of account access with a plain-language description. The store files list a single scope, dev.ucp.shopping.checkout:manage, whose description says it lets the agent prepare checkouts while the buyer completes the purchase, and that most stores allow guest checkout without it.
scope_hints rates each scope with two required fields, defined in spec section 4.7:
changes:none(nothing changes),reversible(every change can be undone, like editing a saved address) orirreversible(any change cannot be undone, like cancelling an order, sending a message or paying).personal_data:trueif any action shows or changes contact details, addresses or payment methods.
The store files mark checkout as irreversible with personal data, which is the most cautious rating available. The spec adds two rules agent builders should code in: treat any unknown changes value as irreversible, and remember that hints are the company's claims, not the user's approval.
agent.protocols
Lists the conversation endpoints of the company's own agent. The store files point to type ucp at /.well-known/ucp. When we fetched that URL, it returned a UCP profile dated 2026-08-25 with older supported versions listed. One detail: the 1.0 changelog makes a description required on each entry (so an agent can decide which endpoint fits a task). The 0.4 store files have no description, which matches their version label.
web and extensions
web is an empty object in the store files. Under the spec, without a browser_session_endpoint an agent browses the site as an ordinary signed-out visitor, unless web.disabled is set, which asks agents not to browse at all. extensions lists ucp version 1 only. The separate operations extension, which we cover next, was not listed.
Step 3: Understand when the customer must approve
Poppy's core spec handles scopes. Approval of a specific action, such as an exchange with a price difference, lives in the operations extension (version 3). Its flow is simple:
- The agent makes its request as usual. The company does not perform it, and instead returns an "operation": the exact terms in plain language and as JSON.
- The terms are approved, either by asking the user or on an instruction the user already gave the agent.
- The agent repeats the request with the approval. The company performs only what that revision of the terms describes, or declines and performs nothing.
The extension guarantees two things: an approval covers the exact terms, and a retry with the same approval never performs the action twice. Sierra's post says the Shopify-co-authored commerce extension also makes the agent ask the customer before certain actions. Because the store files we read did not list the operations extension, treat any checkout as the buyer's own final step, which matches the scope description.
Step 4: Validate a non-Shopify implementation
If you run your own site and want to publish Poppy yourself, the official Company implementation kit has two parts: a skill for coding agents (implement-personal-agent-protocol) and a command-line validator that acts as a test personal agent. It needs Node 22.18 or later, a deployment reachable over HTTPS (a test environment is recommended because the validator starts real sessions and sends test messages), and an HTTPS URL you control for the test agent's public files. The skill works in five steps: survey (GET requests only), design (you approve scope before any building), build in milestones with check --milestone, verify with check --design plan/design.md, and report. The kit notes that a company offering only its website stops after publishing poppy.json without auth.
Poppy file vs. UCP profile vs. OAuth metadata
A store now exposes several well-known files, and they answer different questions. All three below returned HTTP 200 on the stores we checked.
| File | What it tells an agent | Who defines it | Seen on Shopify stores (2026-11-17) |
|---|---|---|---|
| /.well-known/poppy.json | Who the company is, channels it offers, scopes and how risky each one is, extensions | Personal Agent Protocol spec (1.0 published; stores still on 0.4) | Yes, version 0.4, one checkout scope rated irreversible |
| /.well-known/ucp | The shopping services: products, cart, checkout, and supported UCP versions | Universal Commerce Protocol (Shopify supports it by default, per Sierra) | Yes, profile version 2026-08-25 |
| /.well-known/oauth-protected-resource | Which authorization server issues access for the domain (standard RFC 9728 metadata) | OAuth standard, referenced by Poppy section 3.2 | Yes (HTTP 200) |
The short version: poppy.json is the front door and the rulebook, UCP is the shop counter, and the OAuth metadata names who hands out access.
Editor's note
Who it's for: Shopify merchants who want to know what agents are told about their store, and developers building shopping or support agents who need a dependable first read at a company.
Who it's not for: anyone expecting a ranking or SEO effect. Nothing in the spec or Sierra's post says the file affects search.
Gotchas we verified:
- The store files say
"0.4". Under spec 3.4, an agent that implements only 1.0 must not treat that as compatible. Support 0.4 too, or wait for stores to update. - 0.4 entries in
agent.protocolshave nodescription, which 1.0 requires. Do not fail hard on a missing description if you accept 0.4 files. - Getting HTML instead of JSON means no Poppy file is served at that exact domain. Try the store's main shop domain before concluding it has none.
- Scope hints are the company's claims. Your agent still needs the user's own decision before anything marked irreversible.
Related reading on lightmind24: agent payments are a different layer, compared in ChatGPT Wallet vs Google Wallet in Gemini. Poppy's skill index uses the same SKILL.md idea explained in Agent Skills: One SKILL.md for Claude Code, Cursor, Copilot, and if your agent drives a real browser, see our Chrome DevTools MCP tutorial.
Screenshots of the official Sierra post and Poppy docs, plus our own table of the store files, are at the end of this post.
FAQ
Do I need to add anything to my Shopify store?
No. Sierra's announcement says every Shopify store now publishes a Poppy file automatically, so merchants do not need extra implementation.
Can an agent buy something just because the file exists?
The file only describes what can be requested. The store files we read rate the checkout scope as irreversible with personal data, and its description says the buyer completes the purchase. Specific approvals of exact terms come from the separate operations extension.
Is version 0.4 a problem?
For merchants, not directly. For agent builders, yes: by the 1.0 spec's compatibility rule, 0.4 and 1.0 are not compatible, so an agent must implement 0.4 to use these files today.
Read the file once for your own store: it is the clearest statement of what agents are being told about you.
Last verified: 2026-11-17
Sources:
Sierra: Releasing Personal Agent Protocol 1.0
Personal Agent Protocol specification, version 1.0
Personal Agent Protocol: Operations extension
Personal Agent Protocol: Company implementation kit
Personal Agent Protocol: Changelog
Store files: allbirds.com, www.kyliecosmetics.com and www.tentree.com /.well-known/poppy.json, fetched 2026-11-17
Image credits: screenshots of the official Sierra blog and personalagentprotocol.org docs; store-file table by lightmind24.
lightmind24 is an independent review site, not affiliated with Sierra, Shopify or the Personal Agent Protocol project.
댓글
댓글 쓰기