Meta and Sierra's Personal Agent Protocol Wants to Be the Handshake Between AI Agents and Every Business

On October 6, 2026, at Sierra Summit in San Francisco, Sierra co-founders Bret Taylor and Clay Bavor announced the Personal Agent Protocol (PAP) — a new open standard co-developed with Meta that defines how AI agents authenticate with and operate on behalf of users inside third-party businesses. Shopify, Stripe, Walmart, Rocket, Genesys, and Instinct signed on as founding partners. OpenAI, Anthropic, Amazon, and Google did not.

The Problem PAP Is Solving

If your AI agent can book flights, file returns, or check your bank balance, it needs a way to log into those services as you. Today there's no standard for this. Each company builds its own integration, or there is none at all. PAP attempts to solve this the same way OAuth solved web login a decade ago: give every party — the user, the agent, and the business — a shared handshake they already understand.

The protocol separates interactions into tiers. A guest-mode request — "Is this item in stock?" or "What's your return policy?" — needs no authentication at all. Once a task requires account access, the user signs in through a standard OAuth flow and explicitly grants the agent either read-only or read-write permissions. The business then picks how it exposes its systems: proprietary APIs, open APIs built on OpenAPI and the Model Context Protocol (MCP), or its own customer-service agent.

What PAP Is Not

The announcement was careful to define scope. PAP is an interaction layer, not a payments protocol. It governs who the agent is, what it's allowed to do, and how it declares its intent. Settlement — how money moves — stays on existing financial rails. Sierra has listed payments support as a future extension, alongside push notifications and more granular permission controls.

The v0.1 specification had not been published as of the announcement. It is due later in October 2026. A few sources describe PAP as "live" based on the announcement, but most coverage is clear that what went live was the announcement, not the spec itself.

The Elephant in the Room: Who's Missing

The founding partner list is notable as much for who isn't on it as who is. Analysis from beri.net points out that OpenAI, Anthropic, Amazon, and Google being absent is a significant structural problem. If the most widely used personal AI agents run on infrastructure from companies outside the standard, those agents have no incentive to implement PAP's flows. Businesses that build PAP-compliant systems may find only a fraction of agents capable of using them.

Sierra and Meta are betting that Shopify, Stripe, and Walmart on the partner list create enough gravitational pull to draw the absent players in. It's a reasonable theory — merchants with those distribution platforms cover a significant share of e-commerce — but it's still a theory. The history of competing protocol proposals in tech suggests that critical mass is far from guaranteed.

Why It Matters Anyway

Even with those caveats, PAP is tackling a real and increasingly urgent problem. AI agents are already purchasing items, managing subscriptions, and filing requests on behalf of users in production environments. Right now, the security and permission model underneath those actions varies by vendor and by platform, and users often have no visibility into what access they've actually granted. A standardized, OAuth-rooted protocol — even an imperfect one — is better than the current patchwork.

The v0.1 spec, once published, will be the real test. Whether PAP becomes the HTTPS of AI agent commerce or another well-meaning proposal that fragments further depends on whether the major AI platforms decide to show up.