Personal Agent Protocol: Meta, Sierra and Walmart set sign-in rules for your AI agent
The Personal Agent Protocol (PAP) is an open standard announced by Meta and Sierra on October 6, 2026 that defines how a consumer's personal AI agent authenticates with a business's website or APIs and what it is allowed to do. Walmart, Stripe, Shopify, Genesys, Rocket and Instinct are named partners. Sessions are built on OAuth: an agent can start as a guest to check stock or a returns policy, and once the customer signs in, the customer chooses read-only or write access. The v0.1 specification is due later in October. Paying without sharing card details is a planned extension, not part of the first spec. OpenAI and Anthropic are not on the partner list
The three lines
- What — rules for a personal AI agent to sign in and act at a business; OAuth sessions, guest → read → write
- Who — led by Meta and Sierra; Walmart, Stripe, Shopify, Genesys, Rocket, Instinct as partners
- Not yet — v0.1 spec later in October; payments, fine-grained permissions, push alerts come later
Key questions
- What is the Personal Agent Protocol
- **An ID-and-permissions standard for AI agents acting on a shopper's behalf.** | Item | Detail | |---|---| | Announced | October 6, 2026, Meta and Sierra | | Covers | Authentication, consumer control, business visibility into agent activity | | Built on | OAuth sessions | | Openness | Anyone can implement it | | First spec | v0.1, later in October |
- Can AI agents make purchases with Personal Agent Protocol
- **Not in v0.1; payments are a future extension.** | Level | What the agent can do | |---|---| | Guest | Check stock, read returns policy | | Signed in, read | View orders | | Signed in, write | Change orders, file claims | | Future payments | Complete purchases without sharing card details | A separate Visa-led agent payments protocol already exists; Stripe and Shopify are in both.
- Personal Agent Protocol vs MCP
- **MCP connects AI to tools; PAP governs who uses that connection, and with what rights.** | | MCP | PAP | |---|---|---| | Focus | Linking AI to tools and data | Identity and permissions of consumer agents | | Relation | PAP can use MCP or OpenAPI as a business's API route | Adds authentication and sessions | | Led by | Anthropic | Meta and Sierra |
Online stores cannot tell whether a visitor is a person or an AI. Some block agents outright; others unknowingly give a disguised agent the same powers as a human. The Personal Agent Protocol, announced by Meta and customer-service AI company Sierra on October 6, 2026, tries to replace that gray zone with rules. Walmart, Stripe and Shopify signed on. PAP defines what identity a personal AI agent presents when it enters a business on your behalf, and how far it may go.
1. What it governs: from guest to write access
Bret Taylor, Sierra's co-founder and OpenAI's chairman, is leading the effort. He says companies today have no reliable way to know whether they are dealing with an agent or a human. The design rests on two sentences: consumers decide what access their agents get; companies decide what agents may do.
| Level | What the agent can do | Who approves |
|---|---|---|
| Guest | Check availability, read returns policy | Automatic, within company limits |
| Sign-in | Customer signs in on the company's page or uses credentials stored with the agent | Customer |
| Read access | View orders and account details | Customer's choice |
| Write access | Change orders, file warranty claims | Customer's choice |
Sessions run on OAuth, the same standard behind "Sign in with Google." A session persists across channels, so a question asked before sign-in and an order change made later count as one visit. Businesses choose how agents reach them: their website, their APIs using standards such as MCP and OpenAPI, or their own agent for conversational tasks.
2. Who joined, and who didn't
| Partner | Role or statement |
|---|---|
| Meta, Sierra | Co-leads |
| Walmart | Retail partner |
| Stripe | "A customer relationship doesn't start or end at checkout." (Kevin Miller, head of payments) |
| Shopify | Agents and merchants working together on questions, purchases and returns |
| Genesys | Brands need a trusted way to know who an agent represents (CEO Tony Bates) |
| Rocket | Agents moving from home search to financing |
| Instinct | Joining the effort |
OpenAI and Anthropic are not listed. On payments, a Visa-led agent protocol already exists, and Stripe and Shopify participate in both. The "agent standards" landscape is splitting into lanes: tool connections (MCP), agent-to-agent messaging (Google's A2A), payments (the Visa camp), and now consumer identity and permissions (PAP).
3. Timeline and what's missing
| Item | Status |
|---|---|
| Announcement | October 6, 2026 |
| v0.1 spec | Later in October |
| Next | Design workshops; developer reference implementation |
| Fine-grained permissions | Future extension |
| Push notifications (flight delays, shipments) | Future extension |
| Payments without sharing card details | Future extension — not in v0.1 |
What exists today is a design direction. Only the spec will show which permission units are defined and how businesses identify an agent.
4. What remains unconfirmed
- Some reports say PAP is already published; Sierra's post says the spec arrives later in October.
- Some coverage frames PAP as a response to Amazon blocking Meta's shopping agent; the companies have not said so.
- Whether OpenAI, Anthropic, Google or Amazon will adopt PAP is open. A standard without the largest platforms may cover only half the market.
- Who bears responsibility when an agent with write access places a wrong order has not been addressed.