Meta's Personal Agent Protocol has no spec yet. Check your firewall
Meta and Sierra want one standard for AI agents dealing with businesses. Nothing to build yet. The agent setting in your bot protection matters more.
| What was announced | on 6 October 2026 Meta said it and Sierra are developing the Personal Agent Protocol, an open standard for how personal AI agents deal with businesses, presented as a preview of ongoing work (Meta for Business) |
|---|---|
| Who else is in it | Genesys, NiCE, Decagon, Rocket, Shopify, Stripe and Walmart are named as industry partners (Meta for Business) |
| What it is meant to cover | authentication, how an agent shows who its user is, what agents do on a company's site, steering agents to preferred flows or data such as real-time inventory, and agent-to-agent talks (Meta for Business) |
| What is missing | no published specification, no release date, no cost; the core parts are designed and a working group is building them (Meta for Business) |
| The standard already shipping | the Universal Commerce Protocol has published releases since January 2026, the latest on 25 August 2026; Amazon, Meta, Microsoft, Salesforce and Stripe joined its Tech Council on 24 April 2026 (ucp.dev announcements) |
| The setting that decides today | since 15 September 2026 Cloudflare has a separate Agent control (Allow, Block on pages with ads, Block); sites that had the old AI-bot block switched on were migrated to Block on pages with ads (Cloudflare blog) |
| Accidental blocks | Walmart, a named partner of Meta's Muse agent, said Muse failures on its site were unintentional (TechCrunch, 6 October 2026) |
On 6 October 2026 Meta announced that it and Sierra, a customer-service AI company, are developing the Personal Agent Protocol, an open standard for how AI agents acting for a person deal with a business: proving who they act for, what they are allowed to do on your site, and how they talk to your own service agent. Seven partners are named, including Walmart, Shopify, Stripe and the contact-centre vendors Genesys and NiCE. There is no published specification, no release date and no price.
The verdict for a company with a few hundred staff: there is nothing to build, buy or sign up for. The decision that is live today sits in a setting most operations managers have never opened, the bot protection on your own website.
What did Meta actually announce?
A direction, not a product. Meta's page describes the protocol as a preview: the core parts are designed and a working group is building them. It says the standard will be open for anyone to implement and that no one will own it. It lists what the protocol should handle, from authentication to letting a business point agents at the route it prefers, such as a structured feed of live stock instead of the public product pages.
The partner list is the interesting part. Genesys and NiCE sell the software behind many company contact centres, and Sierra and Decagon build AI service agents. This is not only about online shopping. It is about the day a customer's agent, not the customer, rings your service line or opens a chat to rebook, return or complain.
Is this the standard to wait for?
Not on its own. The Universal Commerce Protocol, whose governing council includes Google, Shopify and Stripe, has published working releases since January 2026, most recently on 25 August. Meta and Stripe already sit on its Tech Council alongside Amazon, Microsoft and Salesforce. The same firms are now backing a second effort that overlaps it on identity and agent behaviour. Two standards with shared members tend to merge or split the work between them, and nobody outside those meetings knows which this will be.
A standard with no specification is a promise. Your firewall setting is a decision you already made.
For a mid-sized business, the honest answer is that the agent standard you will use is the one your platform vendors adopt. You will receive it through your shop platform, your payment provider and your contact-centre software, not by writing to a working group.
What it does not mean
It does not mean agents are about to flood your service desk. Meta's announcement gives no usage figures and no deployment date for any partner. It does not mean you must pick a side between Meta and Google. And it does not make blocking agents wrong; it means blocking should be a choice, not an accident.
That last point is where the real risk sits. Walmart is a named partner of Meta's Muse agent, yet when shoppers reported Muse failing on its site, Walmart said the blocks were unintentional. If a retailer of that size blocked an agent it had agreed to work with, a 200-person company can easily be doing the same without knowing.
What to do this week
Ask whoever runs your website one question: what is our setting for AI agents? If you use Cloudflare, it changed on 15 September. There are now separate controls for search crawlers, training crawlers and agents. If your team had switched on the old block on AI bots, the agent control was moved to block agents on pages that carry ads. If the old block was off, agents are now allowed. Check which of these you are on and whether it matches what you want.
Then ask your contact-centre and shop-platform vendors one more: will you support agent identity standards, and which ones? Write down the answer and the date. When a specification is published, that note tells you whether you have work to do or whether your vendors will do it for you.
Leave the rest alone until there is a document to read. The protocol cannot be implemented before it is published, and the cost to you of waiting is zero.