Your customers are about to send their AI agents instead
The Personal Agent Protocol ("Poppy") is live on Shopify and Meta Muse. Learn how poppy.json controls AI agent access, customer data, and commerce.
On November 13, a new open standard went live, and most executives missed it.
It’s called the Personal Agent Protocol—nicknamed “Poppy” by its creators (I’ll use that from here on). Led by companies like Sierra, Poppy allows personal AI assistants to interact directly with businesses through dedicated agents, websites, and APIs.
Your customer’s AI assistant can now knock on your company’s front door, show its ID, and get work done.
What is the Personal Agent Protocol (Poppy)?
The Personal Agent Protocol (Poppy) is an open standard that lets personal AI assistants securely interact with business websites and APIs using scoped permissions. Instead of blocking bots or granting full account access, companies publish apoppy.jsonfile that defines exactly what customer agents can view, book, or buy.
Why businesses need an AI agent protocol
Right now, companies treat AI agents one of two ways: they lock them out completely, or they hand them the keys to everything.
As the Poppy documentation notes, businesses either block automated agents or let them impersonate a human user with full account privileges. Both sides waste resources trying to detect or evade each other.
Poppy replaces that arms race with a middle path. Access scales granularly—from fully blocked, to catalog search, to viewing reservations, to booking with user approval, up to full access.
Think of it like a hotel key card. The guest gets into their room and the gym, but they can’t walk into the kitchen.
Who is already using Poppy?
Poppy is already live at scale:
- Shopify: Enabled for every Shopify merchant, with each store automatically publishing a default Poppy file.
- Meta: Active for all users of Meta’s Muse, which checks for a site’s Poppy configuration first upon visiting.
- Enterprise & Travel Partners: Live partners include Mercury (banking tasks), Synchrony (financing and rewards), and Turkish Airlines (fare checks, bookings, and upgrades). More than 100 design partners have signed on, including Affirm, Cisco, Delta Air Lines, and Salesforce.
If you sell on Shopify, you’re already in this game—you just haven’t looked at the scoreboard yet.
How does the Personal Agent Protocol work?
- You publish a menu. Your company hosts a
poppy.jsonfile listing your sign-in methods, agent endpoints, APIs, web surfaces, and allowed tasks. - The customer approves access. Users sign in on your company’s own authentication page and choose what their agent is allowed to see and do.
- The agent works inside the lines. Your business defines strict permission scopes—such as allowing order reads while blocking order writes or refunds.
Built-in user privacy: The protocol assigns a unique, per-company user ID that differs across every merchant. Companies cannot cross-reference or match user identities with one another, building privacy into the architecture from day one.
4 questions executives must answer right now
You don’t need to read the technical spec—your engineering team can handle that. Leadership needs to answer four strategic questions:
- What will we let agents do? Letting an agent browse your catalog is low risk; letting it process refunds or change subscriptions is not. That is a commercial decision, not an IT one.
- Who owns our
poppy.jsonfile? As CDP.com highlights, someone must own your configuration, design permission scopes carefully, and ensure scope hints are accurate. If nobody owns it, Shopify’s default settings are speaking for your brand. - What happens to the data afterward? Poppy governs access, not retention. It does not dictate how long third-party agents keep or share transaction data afterward—you still need to write and enforce that policy.
- Are we ready to serve customers we can’t see? Returning users may be authenticated by their agent without ever visiting your storefront or giving you a name. Your marketing funnel has always assumed a human on the other end of the screen. That assumption no longer holds.
A fair caution: The specification is still labeled Draft 1.0. Expect backward-incompatible updates while live enterprise deployments remain early. Don’t panic—just get prepared.
Preparing your business for agentic commerce
I’ve spent the last two years building agents and testing AI platforms. The most common bottleneck I see isn’t technology—it’s executives who know AI matters, but don’t have the bandwidth to become full-time AI engineers.
That is why I built my Executive AI Advisory. It is hands-on and built for speed: we map where agents fit into your revenue workflow, audit what your poppy.json permissions should say, and connect your internal AI tools, projects, and email systems so they reduce workload instead of adding noise.
If you want your leadership team or conference audience to grasp this shift in 45 minutes, I also deliver a keynote on what happens when customers start sending their agents. It’s practical, engaging, and leaves teams with an immediate action plan.
The companies that win the next five years will be the easiest for AI agents to work with. Let’s make sure yours is one of them.
Book an advisory call or keynote at arvellcraig.com.
Frequently Asked Questions
Do I need to set up Poppy if I run a Shopify store?
No initial setup is required. Shopify automatically generates and hosts a default poppy.json file for every merchant, though you should review your permission scopes with your developer team to ensure agents only access approved actions.
What is a poppy.json file?
A poppy.json file is a standardized configuration file hosted on a company’s domain (similar to robots.txt). It tells personal AI assistants which endpoints, APIs, login methods, and tasks they are permitted to use.
Is the Personal Agent Protocol secure for customer data?
Yes. Users authenticate directly on the business’s own sign-in page, grant granular permissions, and receive a unique per-company user ID so businesses cannot track or match customer profiles across different websites.
Sources
- Personal Agent Protocol Specification
- CDP.com: Personal Agent Protocol Analysis
- Sierra: Releasing Poppy