Personal Agent Protocol (PAP): What It Is
TL;DR
Personal Agent Protocol (PAP) is a proposed open standard for personal agents to interact with businesses on a user’s behalf. Sierra announced it with Meta on October 6, 2026. PAP is not a finalized or universally adopted standard.
- Under the announced design, an agent discovers a business through its website, starts a guest or signed-in session, and receives OAuth-based access that the user controls. The business chooses whether the agent uses its website, API, or company agent.
- As of October 13, 2026, Sierra’s announcement described the v0.1 specification and reference implementation as planned publications, not released materials.
- We treat more detailed permissions, push notifications, and payment extensions as proposals. Sierra did not announce them as live PAP capabilities.
What Personal Agent Protocol is
Sierra and Meta announced Personal Agent Protocol (PAP) on October 6, 2026. Sierra describes PAP as an open standard they are developing with partners at Genesys, Instinct, Rocket, Shopify, Stripe, and Walmart. The proposed standard defines how a personal agent could interact with a business on a customer’s behalf.
Sierra says anyone can implement PAP. We treat the announcement as a proposal to develop a shared standard, not evidence that PAP has been ratified or widely deployed.
Why Sierra and Meta are proposing it
Personal agents lack a consistent way to find out how a business accepts requests, obtain a user’s permission, and carry out a task on that user’s behalf. Sierra and Meta’s PAP proposal aims to give participating businesses and agents a shared way to handle those steps while leaving each business in control of how agents interact with it.
Sierra’s announcement includes comments from Tony Bates of Genesys, Shawn Malhotra of Rocket Companies, Mani Fazeli of Shopify, and Kevin Miller of Stripe. Those contributors bring perspectives on customer service, commerce, and payments. We see their participation as evidence of interest in a common approach, not evidence that PAP is finalized or deployed across their businesses.
How the announced design works
A personal agent would begin on a business’s website. In Sierra’s announced design, the website lets the agent discover what the business offers and how to reach it. The agent could then start a guest session. For example, it could check product availability or ask about a returns policy without accessing the customer’s account.
Account-specific tasks would require a signed-in session. Sierra says the customer could sign in on the business’s page or use credentials already set up with their personal agent. The customer would decide whether to grant read-only access or allow the agent to make changes. Sierra describes the session as built on OAuth, an established way to authorize access, and says it could carry across channels. A question asked before sign-in and an order change made afterward could remain part of the same visit.
Once authorized, the agent would use a route the business makes available. Sierra describes three options. The agent could use regular website pages, connect through an API, or work with the company’s own agent for a task that needs conversation, such as a warranty claim. Under the announced design, the consumer controls the access granted to the personal agent, while the business sets the parameters for what that agent can do.
What’s confirmed versus what’s still proposed
As of October 13, 2026, Sierra and Meta had announced PAP’s proposed design, not a finalized standard. Sierra’s October 6 announcement names Genesys, Instinct, Rocket, Shopify, Stripe, and Walmart as collaborators. It describes how an agent could discover a business through its website, start a guest or signed-in session, receive OAuth-based authorization, and use a route chosen by the business. The announcement does not establish that businesses have deployed PAP.
Sierra said it planned to publish a v0.1 specification later in October and a reference implementation to help developers get started. Its announcement does not show either as released, and it provides no later status update. Readers should therefore treat the announced flow as a design proposal rather than a published implementation requirement.
Sierra also described three possible additions using the word “could.” More detailed permissions could limit specific actions. Push notifications could alert an agent when an order ships or a flight changes. Payment extensions could let an agent complete a purchase without sharing card information. Sierra did not present any of these as live PAP capabilities.
Where Skyfire’s KYA and Agentic Wallet fit as a complementary layer
Skyfire’s KYA and Agentic Wallet address a separate part of agentic commerce from the OAuth-based access described in PAP. PAP’s announced design lets a consumer authorize a personal agent to access a participating business. KYA establishes an agent-specific identity and supports transaction-level authorization. Agentic Wallet addresses payment authorization when an agent makes a purchase.
A business evaluating agent purchases may need to answer two different questions. What may the agent read or change in a customer account? Which agent is requesting a payment, and may it make that transaction? PAP’s proposed OAuth flow addresses the first question. Skyfire’s identity and payment-authorization tools address the second.
We do not claim compatibility, a partnership, or an integration between Skyfire and PAP. Business and product leaders should evaluate these as distinct considerations rather than assume either one supplies the other’s controls.
FAQs
Is PAP a finalized standard? No. Sierra’s October 6, 2026 announcement describes a proposed open standard developed with Meta and collaborators. Sierra said it planned to publish a v0.1 specification and a reference implementation, but the announcement does not show either as released. As of October 13, their publication remains unconfirmed.
Who can implement PAP? Sierra says PAP is open for anyone to implement and invites others to help develop it. An open invitation does not establish that businesses have adopted the proposed design.
Does PAP handle payments today? The announcement does not identify payments as a live PAP capability. Sierra describes an extension that could let an agent complete a purchase without sharing credit card information. That extension is a proposal.
How does PAP relate to OAuth? PAP’s announced design uses OAuth to authorize a session when an agent needs account access. The customer decides whether the agent receives read-only or write access, while the business sets parameters for what the agent can do. OAuth handles delegated access in that design. It does not, by itself, verify the agent’s identity or authorize a payment.
Is Skyfire part of PAP? Sierra’s announcement does not name Skyfire, and we have not verified a PAP partnership, integration, or compatibility. We offer Skyfire’s KYA and Agentic Wallet as separate agent-identity and payment-authorization tools for commerce workflows, not as PAP features.
The takeaway for business and product leaders
We recommend treating PAP as a planning input, not an integration commitment. You can identify where customers might ask personal agents to act on their behalf and which access decisions your product would need to support.
Before committing development resources, review the v0.1 specification and reference implementation if Sierra publishes them. Sierra’s October 6 announcement said both were planned, but it did not show either as released. As of October 13, 2026, the announcement alone cannot tell you how businesses will implement PAP or how widely they will adopt it.