# PAP vs A2A: Personal Agent Protocol and Agent2Agent

> A2A is about conversation between agents. PAP is about permission. One of PAP’s three routes is literally "talk to the company’s own agent", so the two are going to bump into each other.

Source page: https://pap.md/compare/pap-vs-a2a  
Last checked against sources: Oct 8, 2026  
pap.md is independent and not affiliated with Sierra, Meta or any PAP partner.

|  | PAP | A2A |
| --- | --- | --- |
| Question it answers | May this agent act for this customer here? | How do two agents exchange work? |
| Created by | Sierra and Meta | Google, donated to the Linux Foundation |
| Spec status | Not published | Published |
| Customer consent | Core of the design | Out of scope |
| Relationship | Agent-to-agent is one of three routes | Doesn’t reference PAP |
| First public | Oct 6, 2026 | Apr 2025 |

## What each one does

A2A gives agents a shared way to describe themselves, hand off tasks and stream results back. It doesn’t care whose credit card is on file. It cares that two agents built by different vendors can understand each other.

PAP, as announced, is narrower and more personal. A customer’s agent arrives at a business, maybe as a guest, maybe signed in, and the customer decides between read-only and write. The business decides what’s on offer.

## Where they meet

The third PAP route is the company’s own agent, used for tasks that need back-and-forth, like a warranty claim. That is agent-to-agent traffic. Sierra’s post doesn’t say which protocol carries it.

There’s a hint, though. Decagon’s PACT, published the same day, is built on A2A plus OAuth 2.0, and Decagon says it has joined the PAP working group. If PACT’s ideas make it into PAP, A2A comes along with them. That’s speculation until v0.1 is out.

**Bottom line:** Mostly complementary, with one overlap to watch: the "company agent" route.

## Quick answers

### Is PAP built on A2A?

The announcement doesn’t say so. It names OAuth for sessions and MCP and OpenAPI for APIs. A2A isn’t mentioned.

### Is Google part of PAP?

No. Google isn’t on Sierra’s or Meta’s partner list.

### Which PAP-related protocol uses A2A?

PACT, which Decagon open-sourced on October 6, 2026, is built on A2A and OAuth 2.0.

PAP's v0.1 spec isn't published yet, so the PAP column reflects the October 6, 2026 announcement only.

## Sources

1. [Introducing Personal Agent Protocol](https://sierra.ai/blog/introducing-personal-agent-protocol) · Sierra (Bret Taylor, Clay Bavor), Oct 6, 2026
2. [Agent2Agent (A2A) Protocol](https://a2a-protocol.org) · a2a-protocol.org
3. [Introducing the Personal Agent Consent & Trust Protocol (PACT)](https://decagon.ai/blog/introducing-the-personal-agent-consent-trust-protocol-pact) · Decagon, Oct 6, 2026