기본 콘텐츠로 건너뛰기

Poppy 1.0 Tutorial: Read the Agent File Shopify Publishes

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.json with 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.domain must 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) or irreversible (any change cannot be undone, like cancelling an order, sending a message or paying).
  • personal_data: true if 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:

  1. 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.
  2. The terms are approved, either by asking the user or on an instruction the user already gave the agent.
  3. 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.protocols have no description, 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.

Uploaded Image Uploaded Image Uploaded Image Uploaded Image Uploaded Image Uploaded Image

댓글

이 블로그의 인기 게시물

브루(Vrew) 요금제 정리: 무료 200크레딧으로 어디까지 쓸 수 있나

요약: 영상 자막 편집기 브루(Vrew)는 2026년 4월 22일부터 기능별 사용량 대신 '통합 크레딧' 하나로 요금을 매겨요. 무료 플랜은 매달 200크레딧이 들어오는데, 음성 분석(자동 자막)만 쓰면 최대 200분 분량이라 짧은 영상 몇 편은 충분하지만, 영상 초반의 Vrew 마크를 지우려면 유료 플랜이 필요해요. 이 글은 브루 공식 가격 페이지와 고객센터 공지를 2026년 10월 23일에 다시 확인해, 크레딧 계산법과 플랜 고르는 기준을 정리했어요. 목차 브루 요금 구조: 통합 크레딧이란 1크레딧으로 할 수 있는 일 무료 플랜으로 되는 것과 안 되는 것 유료 플랜 4종 비교표 월 구독·연 구독·기간 이용권, 무엇이 이득일까 상황별 추천: 학생·직장인·유튜버 크레딧이 모자랄 때: 사용 기록 지우개 업그레이드·환불 전에 알아둘 규칙 운영자 메모, 자주 묻는 질문 1. 브루 요금 구조: 통합 크레딧이란 예전 브루는 플랜마다 음성 분석 몇 분, AI 목소리 몇 자, 번역 몇 자처럼 기능별 한도를 따로 줬어요. 그런데 보이저엑스(브루 운영사)가 실제 이용 데이터를 보니 한두 가지 기능만 집중해서 쓰는 사람이 훨씬 많았다고 해요. 그래서 2026년 4월 22일 업데이트부터는 플랜마다 정해진 크레딧을 받고, 어떤 기능에 쓸지는 내가 정하는 방식으로 바뀌었어요. 플랜별 매달 지급량은 Free 200 · Light 2,000 · Standard 10,000 · Business 12,000크레딧 이에요. 공식 공지에 따르면 무료 사용자는 매달 1일에, 유료 사용자는 매월 결제일에 충전되고, 남은 크레딧은 다음 달로 넘어가지 않아요. 바뀐 뒤 무엇이 좋아졌나 공지에 나온 예시가 이해하기 쉬워요. Standard 플랜에서 AI 목소리만 쓰면 예전에는 최대 50만 자였지만, 지금은 1만 크레딧을 모두 AI 목소리에 몰아 쓸 수 있어 최대 100만 자가 돼요. 반대로 여러 기능을 골고루 쓰는 사람은 크레딧이 기능끼리 ...

에이닷 전화 vs 익시오: 통화 녹음·AI 요약, 내 통신사·폰에 맞는 앱 고르기

요약: 통화 녹음과 AI 요약을 쓰고 싶다면 먼저 내 통신사와 휴대폰 종류부터 확인해야 해요. LG유플러스 고객은 무료 앱 익시오, SKT 고객은 에이닷 전화가 가장 기능이 많고, 다른 통신사의 아이폰 사용자는 iOS에 들어 있는 기본 통화 녹음·전사 기능이 현실적인 선택이에요. 이 글은 2026-10-30에 SKT·LG유플러스·Apple 공식 페이지와 도움말을 직접 확인해 세 가지를 비교했어요. 왜 '앱 기능'보다 '내 조건'을 먼저 봐야 할까요 통화 요약 앱 비교 글을 보면 기능 목록부터 나열하는 경우가 많아요. 그런데 실제로 써 보려는 사람에게 가장 먼저 걸리는 건 기능이 아니라 이용 조건 이에요. 익시오는 LG유플러스 고객 전용이고, 에이닷 전화는 누구나 설치할 수 있지만 통역콜·baro 같은 기능은 SKT 고객에게만 열려 있어요. 아이폰은 운영체제 구조상 앱이 통화를 마음대로 녹음하기 어려워서, 통신사 앱이 안 되면 iOS 기본 기능에 기대야 해요. 그래서 이 글은 "어떤 앱이 제일 좋은가"보다 "내 통신사·내 폰에서 무엇을 쓸 수 있나" 순서로 정리했어요. 기능 차이는 그다음이에요. 한눈에 비교: 에이닷 전화 vs 익시오 vs 아이폰 기본 통화 녹음 구분 에이닷 전화 (SKT) 익시오 ixi-O (LG유플러스) 아이폰 기본 통화 녹음 (Apple) 누가 쓸 수 있나 통신사 구분 없이 앱 설치 가능. 단, 통역콜·baro·그룹통화 발신 등은 SKT 고객 전용 U+ 모바일 고객. 타 통신사, 만 14세 미만, 선불요금제 고객은 제한 (공식 사이트 FAQ상 알뜰폰 중 KB리브엠은 예외) 지원 국가·언어의 iPhone 사용자. 1명과 통화할 때만 녹음 가능 지원 OS·기기 Android 10 이상, iOS 16 이상 iOS 17 이상 iPhone 12 이상 / Android...

타입캐스트 vs 클로바더빙: 수익 나는 채널에 쓸 때 무료·유료 조건 비교

요약 타입캐스트와 클로바더빙은 둘 다 글만 입력하면 한국어 AI 목소리를 만들어 주는 서비스지만, 무료로 쓸 수 있는 범위가 꽤 다릅니다. 클로바더빙 무료는 매달 15,000자까지 쓸 수 있는 대신 수익이 생기는 채널에는 쓸 수 없고, 타입캐스트 무료는 처음에 주는 약 5분 분량의 다운로드로 끝나는 체험판에 가깝습니다. 광고 수익이 붙은 유튜브나 쇼핑몰 영상에 넣을 목소리라면 처음부터 유료 플랜 조건을 보고 고르는 편이 안전합니다. 왜 이 두 서비스를 같이 비교하나 쇼츠 내레이션, 수업 자료 더빙, 상품 소개 영상처럼 "내 목소리 대신 AI 목소리"가 필요할 때 한국 사용자들이 가장 많이 찾는 곳이 네오사피엔스의 타입캐스트 와 네이버의 클로바더빙 입니다. 기능 소개만 보면 비슷해 보이지만, 실제로 문제가 되는 건 음질보다 "이 목소리를 내 채널에 써도 되나" 입니다. 그래서 이 글은 기능 나열보다 무료 사용 범위, 출처 표기 의무, 유료 플랜 가격과 다운로드 한도를 중심으로 정리했습니다. 모든 수치는 2026년 10월 25일에 두 서비스의 공식 요금 페이지와 고객센터 도움말에서 직접 다시 확인한 내용입니다. 한눈에 보는 비교표 항목 타입캐스트 무료 타입캐스트 베이직 클로바더빙 Free 클로바더빙 Standard 월 요금 0원 9,900원 (연간 결제 시 10% 할인) 0원 19,900원 (네이버 클라우드 플랫폼에서 결제) 무료·포함 사용량 음성 생성·재생 무제한, 다운로드는 최초 3,000크레딧(약 5분) 1회 지급 월 30,000크레딧(약 60분) 월 15,000자, 다운로드 월 20회, 프로젝트 누적 5개 (매월 1일 갱신) 월 30,000자, 다운로드 월 40회, 프로젝트 누적 20개 쓸 수 있...