# Poppy vs A2A: Personal Agent Protocol and Agent2Agent

> A2A is about conversation between agents. Poppy is about permission. One of Poppy’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://poppy.md/compare/pap-vs-a2a  
Last checked against sources: Oct 10, 2026  
poppy.md is independent and not affiliated with Sierra, Meta or any Poppy partner.

|  | Poppy | 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 | Draft 0.1 published | Published |
| Customer consent | Core of the design | Out of scope |
| Relationship | Agent-to-agent is one of three routes | Doesn’t reference Poppy |
| 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.

Poppy, 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 Poppy 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 Poppy working group. If PACT’s ideas make it into Poppy, 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 Poppy 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 Poppy?

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

### Which Poppy-related protocol uses A2A?

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

Poppy draft 0.1 was published on October 9, 2026. This comparison reflects the current draft and may change with future revisions.

## 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
4. [Personal Agent Protocol specification (Draft 0.1)](https://personalagentprotocol.org/docs/spec) · Personal Agent Protocol, Oct 9, 2026