Technický PRŮVODCE

Agent2Agent (A2A) Protocol

The Agent2Agent (A2A) protocol is an open standard that lets AI agents built by different vendors on different frameworks find each other, describe what they can do, and hand tasks back and forth over ordinary web technologies.

Poslechněte si tento návodAI-vyprávěný · ~3 min

Na této stránce4 min čtení
  1. Přehled
  2. Hluboký ponor
  3. Real-World Implementace
  4. The Future of Agent2Agent (A2A) Protocol
  5. Uvedení do praxe
  6. Pokračujte v objevování
  7. Často kladené otázky

Přehled

It complements the Model Context Protocol: MCP connects an agent to tools and data, while A2A connects an agent to other agents.

Hluboký ponor

Google announced A2A in April 2025 with a large group of technology partners. The project was later contributed to the Linux Foundation so that it could be governed in the open. The protocol builds on familiar standards: HTTP for transport, JSON-RPC 2.0 for message structure, and Server-Sent Events for streaming updates. Discovery starts with an Agent Card, a JSON document that an agent usually publishes at a well-known URL. It gives the agent's name, a description, its service endpoint, the skills it offers, the input and output types it accepts, and how clients should authenticate. A client agent reads the card to decide whether this remote agent suits the job. Work is organized around tasks. A client sends a message made of parts, which can be text, files or structured data. The remote agent can create a task that moves through defined states such as submitted, working, input-required, completed, failed or canceled. Results come back as artifacts. For work that takes minutes or hours, the client can stream progress or register a webhook for push notifications instead of holding a connection open. A2A treats remote agents as opaque. The client does not see the other agent's prompts, tools, memory or model, only what it advertises and returns. Vendors can therefore cooperate without exposing their internals. People often assume A2A and MCP compete. They answer different questions. MCP describes how an agent calls tools and reads resources, which are usually well-defined functions with structured inputs and outputs. A2A describes how an agent works with another autonomous agent that has its own reasoning and may need several exchanges to finish. A single system can use both. Another misconception is that A2A handles trust on its own. It declares how to authenticate, but organizations still have to decide which agents to trust and what to share with them.

Real-World Implementace

A company's travel assistant finds a partner airline's booking agent by reading that agent's Agent Card, sees that it offers a 'rebook flight' skill, and sends it a task instead of scraping the airline's website.

A hiring coordinator agent passes candidate sourcing to one vendor's recruiting agent and background checks to another's. It tracks each as a separate A2A task with its own status.

A long-running research task sent to a specialist agent returns 'input-required' partway through. The client agent asks the user to clarify and sends the answer back on the same task.

Inside one agent, MCP connects it to a database and a file store. A2A is what that same agent uses to delegate a subtask to a separately owned agent whose inner workings it cannot see.

The Future of Agent2Agent (A2A) Protocol

A2A is still relatively young, and its specification and SDKs have changed noticeably since launch. Adoption depends on whether enough vendors publish agents that are actually useful to call, and on whether registries and trust frameworks develop to help agents find reliable partners. Open questions include how to handle billing, reputation and accountability when one company's agent acts on another's instructions. It seems reasonable to expect A2A and MCP to be used side by side, while the details of how cross-organization agent networks will look in practice remain uncertain.

Uvedení do praxe

Proč na tom záleží

  • Cena a rozpočet. Rozhodnutí o architektuře zvyšují výkon a provozní náklady po mnoho let.
  • Jasnější rozhodnutí. Technické vzdělání pomáhá týmům vybrat ten správný stack, nejen ten nejnovější.
  • Kontrola kvality. Lepší konstrukční volby snižují výskyt problémů se spolehlivostí ve výrobě.

Pozor na

  • Optimalizace jednoho benchmarku může skrýt širší systémové slabiny.
  • Náklady na infrastrukturu a údržbu jsou často podceňovány.
  • Mezery v zabezpečení a pozorovatelnosti se mohou zvětšovat, jak se systémy stávají složitějšími.

Další kroky

  1. Před implementací definujte cíle latence, kvality a nákladů.
  2. Benchmark za realistických podmínek zatížení a dat.
  3. Monitorování chyb, posunu a dopadu na uživatele.
  4. Před škálováním připravte cesty vrácení zpět a reakce na incidenty.

Pokračujte v objevování

Newsletter zdarma

Získejte denní přehled o AI

Tři ověřené příběhy ze světa AI každý všední den ráno, psané srozumitelnou angličtinou. Navždy zdarma, bez reklam.

Jeden e-mail každý všední den. Odhlásit se můžete jedním kliknutím. Vaši adresu nikdy neprodáváme ani nesdílíme.

Otestujte se

Take the Agent2Agent (A2A) Protocol quiz

Okamžitá zpětná vazba ke každé odpovědi a sdílitelný certifikát s ověřitelným ID po absolvování kurzu.

Spustit kvíz

Podpořte bezplatnou AI vzdělávání. AI Understanding je nezisková organizace 501(c)(3) — žádné reklamy, žádná platba za přístup, nikdy. Darujte

Často kladené otázky

What is Agent2Agent (A2A) Protocol?

The Agent2Agent (A2A) protocol is an open standard that lets AI agents built by different vendors on different frameworks find each other, describe what they can do, and hand tasks back and forth over ordinary web technologies. It complements the Model Context Protocol: MCP connects an agent to tools and data, while A2A connects an agent to other agents.

What is the main purpose of the A2A protocol?

A2A standardizes discovery and task exchange between independent agents, whoever built them.

How does A2A relate to MCP?

They solve different problems and can run in the same system: tool access through MCP and agent collaboration through A2A.

What is an Agent Card?

Client agents read the Agent Card to discover what a remote agent can do and how to connect to it.

Which standards does A2A build on?

A2A deliberately uses common web standards so it fits into existing infrastructure.

What does the 'input-required' task state mean?

The task pauses until the client sends a follow-up message on the same task, often after asking the user.