Blog post explains A2A protocol and implementation practices
11/22/2026 — 11/22, 18:19·1 sources (all)·1 reports (all)
Key takeaways
- A blog post by ZerekZhang on Blog Garden explains the A2A (Agent2Agent) protocol, covering how agents from different frameworks discover cap…
Background & analysis
On November 22, 2026, a post by ZerekZhang on the Chinese developer blog platform Cnblogs examined the A2A (Agent2Agent) protocol and the practical questions that come with deploying it. According to the post, A2A is an open interoperability protocol for agents. It was originally proposed by Google and is now hosted by the Linux Foundation. Its purpose is to let agents built on different frameworks and by different vendors discover each other's capabilities, delegate tasks, and exchange results, without the calling side needing to know how the other agent is implemented internally.
The post traces the protocol's origin to April 2025, when Google released A2A at Cloud Next. It describes the central shift as moving away from asking what interfaces another service exposes and toward asking what it can do, with capabilities kept opaque to the caller. The author contrasts this with REST, where a caller must know in advance which endpoints exist and what fields they expect, a premise that becomes hard to sustain when the other side is an agent that reasons and selects its own tools. The post uses the metaphor of a business card, an envelope, and a work order to explain how the protocol's components divide responsibilities, and it walks through what a real call looks like plus the steps needed to build an A2A service from scratch.
On the operational side, the article covers authentication and authorization, identity propagation, timeouts, and idempotency. It focuses on where identity should be placed, citing four hard facts about the SDK and noting that metadata does not reach the tool. The material contains no developments beyond this single post, so the account ends with its publication.
AI-generated from 1 reports · updated 30 minutes ago
- Heat index
- 98
- All sources
- 1
- All reports
- 1
- First seen
- 50 minutes ago
Reports on this story headlines open the original
A blog post by ZerekZhang explains the A2A (Agent2Agent) protocol, which lets agents from different frameworks discover capabilities, delegate tasks, and exchange results. It compares A2A with REST and MCP, then walks through authentication and authorization, identity propagation, timeouts, and idempotency, with steps for building an A2A service from scratch.
博客园AI score 56
Other stories people are talking about
- Heat index 1188RisingMaynard: Claude-assisted Riemann proof credible but must be understood22 sources
- Heat index 1015RisingAnthropic falls 8.5% on day two, closing the first week at a $1.6 trillion valuation21 sources
- Heat index 469Thinking Machines Lab Open-Sources Inkling 2 Mini with 32GB Model Card Recommendation10 sources
- Heat index 386SEC probes Nvidia accounting practices as shares post seven-week slide9 sources
- Heat index 331SurgeTesla begins rolling out FSD V15, Musk claims driving ability beats humans4 sources
How is heat calculated?About the methodHide
Heat counts how many independent sources covered a story in the last 48 hours: one source counts once no matter how many posts it published, decaying with a 24-hour half-life. What ranks first is what many people are talking about.
This page aggregates public feeds. Headlines and summaries are machine-organized and remain the property of the original authors; verify important facts at the source. If you believe a headline or summary infringes your rights, email the contact address in the footer with the page URL and basis of your claim, and we will remove or replace it after review.
- Surge
- Discussion rising fast
- New
- First report within 6 hours
- Rising
- Still gathering discussion

