On 2026-10-06 Sierra co-founders Bret Taylor and Clay Bavor announced Personal Agent Protocol, an open standard Meta and Sierra are developing with Genesys, Instinct, Rocket, Shopify, Stripe and Walmart. Built on OAuth, it lets a personal agent discover what a business offers, start a guest session, then act with user-granted read-only or write access via the company's website, APIs (MCP/OpenAPI) or its own agent. A v0.1 spec, design workshops and a reference implementation are planned for later in October; payments are a future extension.
Key Takeaways
- ✓8 parties: Meta and Sierra co-develop; Genesys, Instinct, Rocket, Shopify, Stripe and Walmart are partners (announcement)
- ✓3 access tiers: guest session, user-granted read-only, user-granted write, all on an OAuth session that carries across channels
- ✓3 integration routes chosen by the business: website, APIs (MCP / OpenAPI), or the company's own agent
- ✓Timeline: v0.1 spec, design workshops and a reference implementation planned for October 2026; payments, finer permissions and push notifications are future extensions
- ✓No spec text or benchmarks are public yet

Turn your technical choice into a development budget
Compare 40 dev plans & simulate token costs vs $20/mo subscriptions
Project Links & Resources
Direct AccessIn-Depth Technical Analysis
Personal Agent Protocol (PAP), announced 2026-10-06 by Sierra's Bret Taylor and Clay Bavor, is an open standard Meta and Sierra are building with Genesys, Instinct, Rocket, Shopify, Stripe and Walmart. Today personal agents mostly drive websites like humans and fall back to support lines when that fails. PAP starts on the company website, where an agent discovers what the business offers, then opens an OAuth-based session on the user's behalf: first as a guest (stock checks, return policies), then with user-granted read-only or write access after sign-in. The session carries across channels. The business decides the execution route: its regular website, APIs built on standards such as MCP and OpenAPI, or its own agent for conversational tasks like warranty claims. Planned extensions include finer-grained permissions, push notifications and payments without sharing card details. No spec text or benchmarks are public yet; a v0.1 specification, design workshops and a reference implementation are planned for later in October 2026. Teams with existing MCP servers or OpenAPI docs are best placed to adopt it early.
Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.
Discussion & Comments
0Sign in to join the discussion
Connect with AI developers to exchange benchmark insights.