Introducing Personal Agent Protocol

Open the original

Short summary

Meta and Sierra are releasing an open standard called Personal Agent Protocol that lets AI agents interact directly with businesses through APIs and websites instead of clicking through forms. It balances consumer control, company visibility, and agent efficiency by letting customers decide what access their agents get and companies set limits on what those agents can do.

  • Personal agents currently waste time navigating websites and forms like humans do; direct API connections through this protocol could complete tasks in seconds with proper security.
  • The protocol uses OAuth for authentication and lets customers control whether agents get read-only or write access to their accounts, with companies deciding which access routes (website, API, or company agent) to offer.
  • Seven major companies including Shopify, Stripe, Walmart, and Genesys are already partnering on development, with a v0.1 spec coming this month and reference implementation to follow.

Full summary

Meta and Sierra just announced Personal Agent Protocol, an open standard they're building with partners like Shopify, Stripe, Walmart, and Genesys. The protocol defines how AI agents interact with businesses on behalf of consumers. Right now, most personal agents navigate websites and apps the same way humans do—clicking through forms, waiting for pages to load. That's slow and unreliable. A direct connection between agent and company could complete the same task in seconds. The protocol needs to work for everyone involved: consumers want speed and trustworthiness, brands need visibility and control over what agents can do, and agent builders need consistent, efficient access. The protocol runs on OAuth, the standard authorization system already used across the web. A personal agent starts by discovering what a company offers, then initiates a session on the user's behalf. The customer decides whether the agent gets read-only or full write access to their account. From there, the agent can work through three routes the company chooses: the website itself, direct APIs built on standards like MCP and OpenAPI, or a conversation with the company's own agent for complex tasks like warranty claims. The session persists across channels, so actions before and after login stay connected as one visit. The customer stays in control at every step—they're the ones granting permission. Sierra and Meta plan to release the v0.1 spec later this month and host design workshops with interested companies. They're also publishing a reference implementation to help developers build it out. Future versions could add granular permissions for specific actions, push notifications when orders ship or flights delay, and payment extensions that let agents complete purchases without exposing credit card details. The whole idea is straightforward: as personal agents handle more daily tasks, companies need secure, clear pathways to work with them without sacrificing the trust customers expect.

Ask about this article