← All drillsBuild an A2A Agent
What you'll be able to do- ✓Explain why two independently-owned agents need a protocol instead of a shared function call
- ✓Write an A2A agent card advertising what an agent can do and how to reach it
- ✓Build an agent that wraps an existing MCP server as its own tool backend
- ✓Implement and track the A2A task lifecycle, including polling for a non-instant result
- ✓Have one agent delegate a sub-task to another agent mid-task and merge the result
- ✓Distinguish a deliberate, inspectable task failure from an unhandled-exception crash and from the dependency simply being unreachable, and handle each honestly
- ✓Score a multi-agent system against a seeded set of known-correct answers, not a single demo
Let two agents owned by different teams, services, or companies interoperate on a real task without sharing code or trusting each other's internals — the actual integration problem the moment an agent system grows past one process.
⌁ Google announced the Agent2Agent protocol in April 2025; governance moved to the Linux Foundation's Agent2Agent project in June 2025, making it a vendor-neutral standard rather than a single company's API.
Start this internshipCreate an account to unlock the 9 sections, the workbench, and AskThili.
BeginSections
1. Build an A2A Agent
🔒 locked2. Lesson 1 — The assistant doesn't exist yet
🔒 locked3. Lesson 2 — A way for the two future agents to find each other
🔒 locked4. Lesson 3 — The policy half of the assistant
🔒 locked5. Lesson 4 — The order half of the assistant
🔒 locked6. Lesson 5 — A real answer, even when it's not instant
🔒 locked7. Lesson 6 — The actual answer
🔒 locked8. Lesson 7 — An assistant that's honest when its dependency fails
🔒 locked9. Lesson 8 — Proof it actually works
🔒 lockedDig deeper
🔗Agent2Agent (A2A) protocol specification (Linux Foundation / Google, 2025)
spec🔗FIPA ACL Message Structure Specification (FIPA, 2002)
spec🔗thili-ai/thilia2a — the reference implementation you build in this course
code