Where the Personal Agent Protocol fits among agent protocols
PAP covers one question the others leave open: has the customer allowed this agent to act on their account here, and how far? MCP moves tool calls. A2A lets agents talk. UCP and ACP handle shopping and payment. TAP proves an agent's identity. PACT, launched the same day as PAP, goes after the same consent problem.
That's a lot of acronyms for one shopping trip, and we think some of them will merge or fade. For now, here's how they line up based on what each project has actually published.
| Protocol | Backed by | Since | Covers | Overlap with PAP |
|---|---|---|---|---|
| PAP | Sierra, Meta | Oct 6, 2026 | Agent sign-in, customer consent (read-only or write), route choice | n/a |
| MCP Model Context Protocol | Anthropic | Nov 2024 | Tools and data an AI app can call | Low |
| A2A Agent2Agent | Google, now a Linux Foundation project | Apr 2025 | How two agents talk to each other | Some |
| UCP Universal Commerce Protocol | Google, with Shopify and retailers | Jan 11, 2026 | The shopping flow: discovery, checkout, after-sale | Some |
| ACP Agentic Commerce Protocol | OpenAI and Stripe | Sep 29, 2025 | In-agent checkout and payment tokens | Some |
| TAP Trusted Agent Protocol | Visa and Cloudflare | Oct 14, 2025 | Proving an agent’s identity on each request | High |
| PACT Personal Agent Consent & Trust Protocol | Decagon and Instinct | Oct 6, 2026 | Agent identity and customer authority, agent-to-agent | High |
Read them as layers
Picture a customer's agent arriving at a store. TAP-style signatures can tell the store which agent this is. PAP tells it which customer sent the agent and whether it may change anything. MCP or A2A carry the actual requests. UCP or ACP take over at the cart and the card.
That's the tidy version. In practice the borders are fuzzy: PAP lists payments as a future extension, UCP has its own discovery, and PACT tackles consent too. The pages below go into each seam.
The comparisons
- PAP vs MCP: Complementary. PAP decides whether the agent gets in and how far; MCP is one of the doors it can use.
- PAP vs A2A: Mostly complementary, with one overlap to watch: the "company agent" route.
- PAP vs UCP: Different layers with a shared border. Expect retailers to need both.
- PAP vs ACP: Complementary today. If PAP’s payment extension ships, Stripe will be the one deciding how much they overlap.
- PAP vs TAP: High overlap in purpose, low overlap in mechanism. A business may end up checking both.
- PAP vs PACT: Direct overlap. PACT is now an input to the PAP working group rather than a rival, at least on paper.
Sources
- Introducing Personal Agent Protocol · Sierra (Bret Taylor, Clay Bavor), Oct 6, 2026 · primary source
- Model Context Protocol · modelcontextprotocol.io · primary source
- Agent2Agent (A2A) Protocol · a2a-protocol.org · primary source
- Under the Hood: Universal Commerce Protocol (UCP) · Google Developers Blog · primary source
- Stripe powers Instant Checkout in ChatGPT and releases Agentic Commerce Protocol codeveloped with OpenAI · Stripe, Sep 29, 2025 · primary source
- Getting Started with Visa's Trusted Agent Protocol · Visa Developer · primary source
- Introducing the Personal Agent Consent & Trust Protocol (PACT) · Decagon, Oct 6, 2026 · primary source
- Meta's Personal Agent Protocol Signs Walmart Before It Has a Spec · BERI
pap.md is independent and not affiliated with Sierra, Meta or any PAP partner. Facts here come from the sources listed on each page.