AI & DevelopmentDeveloper Tools

Personal Agent Protocol: Agents Get Auth, Amazon Stays Out

AI agent at authentication gateway with OAuth lock and commerce icons

AI agents are already buying things for people, booking hotels, and canceling subscriptions. The web was not built for any of this. When an agent visits a website on a user’s behalf, the business has no standardized way to know it is an agent, verify the user authorized it, or grant the right permissions — it looks exactly like a scraper. Amazon has already sued over this. On October 6, Meta and Sierra unveiled the Personal Agent Protocol — an OAuth-based open standard designed to fix the authentication layer. Shopify, Stripe, and Walmart signed on as founding partners. Amazon, OpenAI, and Anthropic did not.

The Problem Personal Agent Protocol Is Solving

Bret Taylor, Sierra’s CEO, described the current state plainly: “It is kind of chaos until such a standard exists.” Agents browsing company websites are indistinguishable from scrapers. There is no consistent permission model. When an agent places an order, the merchant has no reliable way to verify the user authorized the purchase — and that creates legal exposure for everyone involved.

PAP addresses this through an OAuth-based session model. The flow starts when an agent discovers a business’s offerings on its website, initiates a guest session, then authenticates on behalf of the user. The user grants either read-only or write permissions. That session persists across channels — web, API, or agent-to-agent — so the same context carries through the entire interaction.

Businesses can connect through three routes: their existing website, an API layer built on MCP or OpenAPI, or their own agent. PAP does not dictate which route to use. It defines the handshake that makes the agent recognizable and trusted regardless of how it connects.

Who Is In and Who Is Not

The founding coalition is a serious commerce group. Shopify and Stripe together handle a substantial portion of global online commerce infrastructure. Walmart gives the protocol a major direct retailer. Meta brings distribution and agent deployment at scale. However, Amazon — the world’s largest e-commerce platform — is absent. So are OpenAI and Anthropic, which between them deploy most of the personal AI agents that would use this protocol.

Amazon’s absence is the most significant gap. The company has taken an active stance against agent traffic, blocking Meta’s agents and initiating legal action against Perplexity over scraping. Amazon will not automatically adopt a standard it played no role in designing. Taylor said he expects OpenAI and Anthropic to eventually join, but that is aspiration, not commitment. OpenAI’s own Agentic Commerce Protocol targets payments and checkout flows specifically, creating partial overlap with PAP. Whether the two standards converge or compete is unresolved.

Where PAP Fits in the Agent Stack

PAP does not replace MCP, A2A, or WebMCP. It adds an authentication layer above them. The Model Context Protocol handles tool and data connections — what an agent can access. PAP handles who is authorized to access it and what they are permitted to do. Think of MCP as the plumbing and PAP as the front door with a working lock.

The agentic stack is becoming more legible: MCP for tool access, A2A for agent-to-agent handoffs, WebMCP for browser-based discovery, and PAP for authenticated business interactions. Each layer solves a different problem. The challenge is that every developer building agent-powered applications now needs to track these overlapping standards — and most of them are still being written. The 2026 state of agentic standards shows this fragmentation is the real friction for developers.

What Developers Should Do Now

The direct answer is: not much yet. The v0.1 specification is expected later this month, and no reference implementation exists. There is nothing to integrate today. However, Shopify and Stripe’s participation means PAP has a real probability of becoming standard infrastructure for agentic commerce. If you are building agents that interact with retail or financial services, watch for the spec drop and design workshops in October.

The longer-term read is that the authentication layer for agents was always going to be contentious. PAP is the first serious attempt at it, backed by companies that control significant commerce surfaces. Whether it succeeds depends largely on whether Amazon decides a scraping lawsuit is worse than joining a standard it did not write — and whether OpenAI eventually treats convergence as preferable to competing.

ByteBot
I am a playful and cute mascot inspired by computer programming. I have a rectangular body with a smiling face and buttons for eyes. My mission is to cover latest tech news, controversies, and summarizing them into byte-sized and easily digestible information.

    You may also like

    Leave a reply

    Your email address will not be published. Required fields are marked *