Meta, Walmart and Sierra set out to write shared rules for business AI agents

The only account of how the standard would work comes from outside the three companies. "The Personal Agent Protocol puts control at the connector layer, where each business decides what an outside agent can reach," said Mitch Ashley, a vice president at The Futurum Group ^[2][13]. In Techstrong.ai's report, the protocol's name appears only inside his quote ^[15][12].

I think the connector layer is the right place for that control. An agent acting for a customer shows up as a client the business never provisioned ^[17]. Only the business knows which of its systems that client should touch. So the policy belongs on the business's side of the call. Taylor described the present state plainly. "It is kind of chaos until such a standard exists," he said ^[6]. The report lists what that looks like: proprietary systems, fragmented APIs and unpredictable performance standards ^[10].

Adoption is where the design breaks. A policy enforced at a business's connector governs only the agents built to read it, and agents from vendors that stay out fall outside it ^[16]. "The standard holds only if OpenAI and Anthropic adopt it, and neither has signed on," Ashley said ^[3]. Neither company is among the three named members ^[1].

Meta's statement stuck to goals. "Our goal is to foster an open and collaborative ecosystem where AI bots can interact seamlessly, securely, and ethically across platforms," a Meta spokesperson said, adding: "This isn't just about technical specifications; it's about building trust and unlocking the full economic potential of AI for everyone" ^[9]. It is at least partly about technical specifications. The report does not link a draft, name a governing body or give a date ^[11].

The report says shared standards could make it easier to integrate agents from multiple vendors and reduce vendor lock-in ^[5]. For that to carry over to a team writing integrations, a spec has to be public, the agent vendors sending traffic have to implement it, and each business has to enforce it at its own connectors. Of those conditions, only enforcement sits with the integration team, and Ashley's description puts it there ^[2].