Free store auditFeaturesAgent RevenueHow detection worksStrategiesPricingFor agenciesBlogSign inStart free
← All posts

Shopify shipped the Personal Agent Protocol. Here's what merchants can and can't control

2026-11-18 · 7 min read · Tactical

Since 13 November 2026, Shopify's Online Store domains serve a Personal Agent Protocol discovery file at /.well-known/poppy.json, which points personal agents to the store's UCP profile. We asked Shopify in its developer forum what merchants and apps can do about the agents that arrive this way. Shopify's staff answered plainly: the store's Agentic settings don't cover a personal agent individually, there's no API for those settings and none planned, and nothing documented marks an order as coming from a protocol session. This post quotes those answers, explains the protocol's moving parts in plain words, and says what a store on each platform should do this week.

What Shopify turned on

The Personal Agent Protocol ("Poppy" for short) is an open standard for how a person's AI assistant works with a business. Version 1.0 gives a store a discovery file, where it says how agents should work with it, and gives a personal agent a signed session on each request it makes, which the store can check.

Shopify announced it in our thread: Online Store domains now serve the discovery file, and it points personal agents to the store's UCP profile. The protocol covers discovery, the agent's identity and sign-in; carts, checkout and orders go through UCP (the Universal Commerce Protocol). Shopify also points out that agents can use UCP without the Personal Agent Protocol, so a UCP order on its own doesn't show the protocol was involved.

We fetched the file from two Shopify stores on 18 November. Both declare protocol_version 0.4, the last draft before 1.0. Both list UCP as the way in and say nothing about the store's own rules. Neither names a tasks endpoint, the one place the protocol gives a store for its policy.

What Shopify's staff said

We opened the thread, How will Personal Agent Protocol sessions surface to apps?, on 9 October with three questions: how orders are marked, whether apps can see the session, and what merchants can control. A member of Shopify's staff answered on 13 and 16 November. What they said, with their exact words in quotes:

  • On merchant controls. The settings in Sales channels > Agentic apply to the agentic channels a merchant manages there. A personal agent that reaches a store through the protocol isn't one of those channels, "so those settings don't give merchants a way to control it individually today."
  • On an API. "There's also no public Admin API that reads or manages those agentic channel settings, and there aren't plans to make them available to apps at this time."
  • On orders. "Nothing documented today marks an order as coming from a Personal Agent Protocol session, whether that's a channel, a note attribute or an order field." What an app can read is who the order is attributed to (Order.sourceName, Order.app, Order.attribution), not which protocol the agent used.
  • On the session. The session ID travels in a request header between the agent and the store. "There's no documented way for apps to get it through webhooks, the Admin API or Customer Events."

Two fair points from the same answers. Shopify says orders placed through personal AI agents show in the admin attributed to the agent, so a merchant isn't blind to who placed them. And Shopify says it's working on ways for the developers who build agents to attribute orders to them, with no date yet. Shopify also asked for use cases in the thread; if you want a control, that's the place to say so.

The protocol in plain words

Four parts matter to a store.

Part What it does What it can't do
The discovery file, /.well-known/poppy.json Says who the store is, where agents sign customers in, and which APIs or agents it offers. organization.domain must be the host that serves the file, after any redirects. Make an agent do anything.
web.disabled A yes or no in the file: it asks agents not to browse the site; nothing in the protocol enforces it. Stop an agent that browses anyway.
The tasks endpoint, with excluded_tasks Lists what the store doesn't want agents to do, each with what to do instead. This is where a store's policy lives. Stop an agent that ignores it.
The Poppy-Session header A signed identity on each request a personal agent makes through the protocol, from a key the agent's operator vouches for. A store can check it on each request. Reach an app on Shopify: per Shopify's answer above, there's no documented way for apps to get it.

The short version: poppy.json lets you ask. Enforcing takes something in the request path, code that sees each request before your store answers it, checks the session and applies your rules.

Protocol sessions are one new kind of agent visit. Crawlers and agent browsers, which send no session, aren't going away, so the protocol doesn't replace knowing what those are doing on your store.

What to do this week

On Shopify

  1. Look at your file. Open https://yourstore.com/.well-known/poppy.json, or run the free scanner: it reads the file and says whether it declares any policy.
  2. Use Sales channels > Agentic for what it covers: the named AI channels Shopify manages there. Per Shopify, it doesn't cover a personal agent arriving through the protocol.
  3. Watch the admin's order attribution. Orders from personal AI agents show attributed to the agent. Nothing marks them as protocol sessions, so don't read a UCP order as one.
  4. Ask for the control you need, in the thread. Shopify asked for use cases.

On WooCommerce

Nobody serves a discovery file for you, and an agent that looks for one finds nothing. That's fine. Before you publish one, decide what you don't want automated: checkout on a limited release, bulk add-to-cart, anything that needs a person. Then list those as excluded tasks, each with an alternative. Don't set web.disabled unless you also offer an API or your own agent instead: the spec allows it only then.

On a headless store or your own stack

You can serve the file yourself; the scanner hands you a minimal valid one. Checking sessions takes server code that fetches each agent's keys from the address it names, which needs the same safeguards as any server fetching a URL a stranger supplies: no redirects, no private addresses, timeouts, a size cap. Read what the spec requires before you build it.

What we're building

On WooCommerce, our plugin (1.6.0, in beta) verifies a Personal Agent Protocol session, attributes an order placed in it to the agent with an evidence record, and can serve your discovery file with your rules listed as tasks agents are asked not to do. We've tested it on our own test store, not yet on a merchant's. A Cloudflare connection verifies sessions only, and our npm middleware doesn't verify them yet. Enforcing the rules is Tactical Gate, in private beta: Observe mode first, enforcement with design partners. Join the beta. How it works, and what it stores: Personal Agent Protocol docs.

On Shopify we can't do any of this, for the reasons Shopify gave above.

What we don't know yet

  • Whether Shopify will extend its Agentic settings to protocol agents. The answer today is no, with no plans for an API; the thread is open.
  • When Shopify's file moves to 1.0. As served on 18 November it declares 0.4.
  • How quickly agents adopt the protocol instead of driving a browser, which sends no session at all.

Questions

Can a Shopify merchant control personal agents that use the Personal Agent Protocol?

Not individually, today. Shopify's staff said on 16 November 2026 that the Sales channels > Agentic settings apply to the agentic channels a merchant manages there, and a personal agent arriving through the protocol isn't one of them. There's no public Admin API for those settings, and no plans to offer one to apps.

Does Shopify mark orders placed in a Personal Agent Protocol session?

No. Shopify's staff said nothing documented today marks an order as coming from a protocol session. Orders from personal AI agents show in the admin attributed to the agent, without saying which protocol it used.

What is poppy.json?

The Personal Agent Protocol's discovery file, served at /.well-known/poppy.json. It tells a personal agent who the store is, where to sign customers in, and which APIs or agents the store offers. A store's policy goes at the tasks endpoint the file names, as excluded tasks.

Does web.disabled stop agents from browsing?

No. It asks agents not to browse the site with a browser, and the spec allows it only when the file offers an API or the store's own agent instead. Nothing in the protocol enforces it.

See how AI agents are using your store

Free tier, 5-minute install.

Start free →
[email protected]
How detection worksDrop WatchReadiness scannerAgent revenuePricingStrategies comparedPerformancePrivacyTerms