Sierra and Meta announce Personal Agent Protocol for business interactions
The AMW Read
The proposed standard meaningfully expands Sierra's role in agent interoperability and could affect business access across the agent segment, although deployment and adoption remain unproven.
Named counterparties: Instinct, Rocket
Sierra and Meta announce Personal Agent Protocol for business interactions
Sierra and Meta announced Personal Agent Protocol on October 6, an open standard for personal AI agents to interact with businesses. They are developing it with Genesys, Rocket, Shopify, Stripe, Walmart, and other participants. Sierra plans to publish the v0.1 specification this month, alongside design workshops and a developer reference implementation. The protocol would let agents discover a business's services and connection methods, then start a session on a user's behalf. Users determine access permissions, while businesses set the conditions for agent actions.
The initiative addresses a practical constraint in the agent market: autonomous systems need businesses to recognize and authorize their actions. Sessions would build on OAuth, connecting guest inquiries and authenticated tasks within one interaction. Businesses could route agents through websites, APIs using MCP or OpenAPI, or their own conversational agents. This places interoperability and orchestration alongside task execution as competitive considerations. Meta says some businesses block personal agents over traffic spikes, abuse, liability, and customer relationships; a shared protocol could help address those concerns, but the announcement does not establish adoption or production reliability.
For builders and investors, the concrete checkpoint is whether the v0.1 specification makes permission boundaries and business-controlled routing implementable across those connection methods. User-selected read or write access is part of the proposed approach. More granular permissions, push notifications, and payments without sharing credit card information remain possible extensions. The specification and reference implementation will offer evidence of technical feasibility; participation by named companies alone does not demonstrate deployment.
