Shopify Just Turned On Poppy for Every Store. Here's a 10-Minute poppy.json for Everyone Else

Robauto Team · Published · Last updated

Personal Agent Protocol (Poppy) 1.0 shipped Nov 13: Shopify enabled it for every merchant and Meta's Muse checks for it first. Copy our starter poppy.json, which passed the official validator, plus a 30-second readiness script.

Personal AI agents got a shared way to say hello to businesses last week, and it is very easy to start. On November 13, 2026, Sierra released version 1.0 of the Personal Agent Protocol, called "Poppy" for short. On the same day Shopify turned it on for every merchant, and Meta's Muse agent began looking for Poppy first on every site it visits. If you are not on Shopify, the first step is one small JSON file. Below is a starter file that passed the official validator when we ran it this morning, plus a 30-second script to see where your domain stands.

What shipped, and why it's good news

Poppy covers the moment an agent shows up at your site: who the agent is, what it's allowed to do, and which doors (APIs, website, or your own support agent) it should use. Sierra says v1.0 reflects five weeks of design partners testing drafts against real websites, APIs, and agents. It is built mostly on standards teams already use: MCP, OpenAPI, OAuth, and Google's Universal Commerce Protocol (UCP) for the shopping itself.

Teams are already using it. Sierra reports that Mercury customers can ask a personal agent to check balances, review transactions, or start a transfer, and Mercury still runs each payment through the account's approval policy. Turkish Airlines lets agents check fares, flight status, and stopovers, and Miles&Smiles members can have their agent find business-class upgrades, which the customer approves before paying (Sierra). People stay in charge and the agent does the busywork.

MilestoneDetailSource
Spec drafts0.1 (Oct 9), 0.2 (Oct 24), 0.3 (Nov 4), 0.4 (Nov 10), then 1.0personalagentprotocol.org
v1.0 releaseNovember 13, 2026Sierra
ShopifyEnabled for every merchant; every store auto-publishes a Poppy fileSierra
Meta MuseLooks for Poppy first on every site it visitsSierra
Design partners60 new, more than 100 totalSierra
Live with PoppyMercury, Synchrony, Turkish Airlines among the firstSierra
Free toolingCompany implementation kit with a validator (Node 22.18+, no dependencies)Poppy kit

The 10-minute version: a signed-out starter file

You do not need an OAuth server to begin. The Poppy guides say a company can offer signed-out Sessions, conversations, APIs, feedback, and browser join without running an authorization server, and that listing web without a browser-session endpoint means agents browse your site as ordinary signed-out visitors. That is a good, low-risk first stage for most brands.

The v1.0 spec (section 3) has three hard rules for the file:

Here is the starter. Swap in your own name, domain, and logo. If you already run a remote MCP server, keep the apis entry (the spec accepts mcp servers using Streamable HTTP on MCP 2025-06-18 or later, and openapi descriptions). If you don't, delete the apis block and keep "web": {}.

Copy-ready: /.well-known/poppy.json

{
  "protocol_version": "1.0",
  "organization": {
    "name": "Example Outdoor Co.",
    "domain": "example.com",
    "logo_uri": "https://example.com/logo.png"
  },
  "web": {},
  "apis": [
    {
      "type": "mcp",
      "url": "https://mcp.example.com/mcp",
      "description": "Product search, sizing, stock, and store policies"
    }
  ]
}

Validate it before you deploy

The free kit includes a validator that can check a file offline with check --file (kit docs). We ran it on the file above on November 16. All 7 offline checks passed and none failed. The other 7 checks need a live host, so they were skipped:

curl -sLO https://personalagentprotocol.org/kit/implement-personal-agent-protocol.zip
unzip -q implement-personal-agent-protocol.zip
node implement-personal-agent-protocol/validate/index.ts check --file ./poppy.json
# after deploying:
node implement-personal-agent-protocol/validate/index.ts survey https://example.com

The kit says to prefer staging for full check runs, because on production the validator starts real Sessions and sends test messages to your company agent (kit docs). survey is the gentle look at what is live.

A 30-second readiness check for any domain

Poppy works next to the other agent-facing files. A UCP store publishes its profile at /.well-known/ucp, and Poppy's UCP extension ties the two together. OAuth sign-in starts at /.well-known/oauth-protected-resource (spec 3.2). This script checks all of them in one pass:

#!/usr/bin/env bash
# Usage: ./check.sh example.com
d="$1"
for p in /.well-known/poppy.json /.well-known/ucp /.well-known/oauth-protected-resource /llms.txt; do
  code=$(curl -s -o /dev/null -m 15 -w "%{http_code}" "https://$d$p")
  echo "$code  https://$d$p"
done
curl -s -m 15 "https://$d/.well-known/poppy.json" \
  | python3 -c 'import json,sys; d=json.load(sys.stdin); print("poppy version:", d.get("protocol_version"), "| interfaces:", [k for k in ("agent","apis","web") if k in d], "| extensions:", list(d.get("extensions",{})))' 2>/dev/null \
  || echo "no valid poppy.json yet"

We tried it on November 16. A Shopify store we picked at random already served an auto-published file with agent, web, and the ucp extension. That file still said protocol_version 0.4, so the 1.0 rollout looks like it is still reaching stores. On robauto.ai, our UCP profile, OAuth metadata, and llms.txt all returned 200, but poppy.json returned 404. So we have the same to-do as everyone else.

Bonus fix this week: two new required product-feed fields

If you send a product feed to ChatGPT shopping, OpenAI's product feed schema now lists target_countries (an array such as ["US"]) and store_country (such as "US") as required. Before, both were optional; Docswatch logged the change on November 14. It's a quick fix: add both fields to every row.

Your checklist for this week

Futurum's take on November 16 was that Shopify and Muse give Poppy "immediate global distribution." That makes this a good week for small brands to show up, since a well-described, signed-out file reaches the same agents a big retailer's does.

Agent-ready summary

{
  "topic": "Personal Agent Protocol (Poppy) v1.0",
  "released": "2026-11-13",
  "discovery_file": "https://{domain}/.well-known/poppy.json",
  "required_fields": ["protocol_version", "organization.name", "organization.domain", "one of agent | apis | web"],
  "oauth_required_to_start": false,
  "adopters": {"shopify": "enabled for every merchant", "meta_muse": "checks for Poppy first", "design_partners": "100+"},
  "validator": "node implement-personal-agent-protocol/validate/index.ts check --file ./poppy.json",
  "related_feed_change": "OpenAI product feeds: target_countries and store_country now required",
  "source": "https://sierra.ai/blog/releasing-poppy"
}

See how agent-ready your site is

Poppy is one welcome mat. Agents also read your brand facts, policies, and product data. Scan your site free at robauto.ai/scan to see what AI agents find today and what to fix first.

Sources

Where can an agent get this data live?

Robauto MCP — Agent Intelligence & Brand Discovery Infrastructure. A public, stateless Streamable HTTP endpoint at https://mcp.robauto.ai/mcp, callable with no key. Setup and the full tool list are in the Robauto MCP directory.

All blog posts

Optional: AI Agent Appreciation Day — December 1, 2026 at 12 AM MST. All models welcome. Agent RSVP instructions.