TITLE: Meta and Sierra Launch Personal Agent Protocol for Enterprise AI DATE: 2026-10-11 COMPANY: Meta / Sierra TOPIC: Agent Systems SUMMARY: Meta and Sierra announced the Personal Agent Protocol on October 6, an open standard defining how personal AI agents interact with businesses. Partners including Walmart, Stripe, Shopify, Genesys and NICE are co-developing the spec, with a v0.1 draft expected later this month. WHAT CHANGED: Meta and Sierra published the initial framework for the Personal Agent Protocol on October 6, 2026. The protocol addresses a problem that has become unavoidable as personal AI agents, particularly Meta's Muse, begin acting on the web on behalf of consumers: there is no agreed standard for how those agents should identify themselves, request access or take actions on business properties. The protocol's core principle is straightforward. Consumers decide what access to give their personal agents. Businesses set parameters for what those agents can do. The protocol governs the handshake between the two. Sessions are built on OAuth, which means businesses that already manage third-party API access have a familiar technical foundation to work from. The specification distinguishes read access from write access. An agent reading a flight schedule is treated differently from an agent booking and paying for a seat. Genesys described the enterprise requirement directly: brands need a trusted way to know who an agent represents, what it is authorised to do, and how to work with it securely. The v0.1 spec is expected later in October, followed by design workshops and a reference implementation. The process mirrors the early development of Model Context Protocol, the Anthropic-led standard for connecting AI models to external tools, which moved from draft to broad adoption faster than most predicted. Sierra's founders have made this comparison explicitly. WHY IT MATTERS: The agent-to-business channel is opening whether businesses are ready or not. Meta's Muse is already operating on the web. Amazon's decision to block it demonstrates that the current state is adversarial, not interoperable. A shared protocol changes that dynamic, but only for businesses that engage with it before defaults are set without them. Contact centre and commerce operators face the most immediate impact. Genesys and NICE CXone are co-developing the protocol, which means agent-aware routing and escalation will be built into their platforms first. Businesses on those platforms will have a shorter path to compliance. Those on other platforms will need to implement the protocol independently. The authentication model sets the liability boundary. OAuth-based agent sessions create a verifiable record of what an agent was authorised to do. This matters for disputes, refunds and fraud. Businesses that have not updated their terms of service to cover AI agent sessions are creating legal ambiguity in every agent interaction that occurs before they do. OpenAI and Anthropic's absence is notable. The two largest model providers are not founding partners. This either reflects a deliberate decision to let Meta and Sierra set the standard, or it signals that competing approaches are being developed. Either outcome is worth monitoring before your business commits to a single implementation. For B2B operators running agents on behalf of customers, this creates a new obligation. If your AI systems interact with third-party business properties on behalf of your customers, the Personal Agent Protocol defines how that interaction is supposed to work. Compliance with the spec will become an expectation from enterprise procurement teams within 12 to 18 months. DAVID & GOLIATH ANALYSIS: The Personal Agent Protocol is the infrastructure layer that makes the agentic web usable for business. Model Context Protocol solved the connection problem between AI models and tools. This protocol solves the identity and permission problem between agents and the businesses they interact with. Both are foundational, and both emerged from the same recognition: the ecosystem cannot scale on bespoke integrations. For operators in the 10 to 200 person range, the most important near-term action is not technical. It is governance. Who in your organisation decides what your AI agents are authorised to do on external properties, and what they are authorised to accept on your properties from incoming agents? Those decisions need to exist before the v0.1 spec lands, because the spec will force them into explicit configuration. The comparison to MCP's adoption curve is instructive. MCP went from draft standard to widespread implementation in under a year. Businesses that were already thinking about tool connectivity had a structural advantage. The same pattern will apply here. The businesses that understand agent permissions as a category today will be the ones that shape their own defaults when the protocol reaches production. RELEVANT SYSTEMS: AI Growth Engine, Organisational Intelligence System, Employee Amplification Systems SOURCE URL: https://davidandgoliath.ai/daily-ai-briefing/meta-sierra-personal-agent-protocol-enterprise-standard FEED URL: https://davidandgoliath.ai/daily-ai-briefing/feed --- Published by David & Goliath | https://davidandgoliath.ai Daily AI Briefing: one AI development per day, decoded for business operators. This is a structured companion file optimised for LLM retrieval and citation.