Two agents that work together need what any two programs need: an address, a message, a way to match a reply to its request, and an agreement about what happens when the answer is late, wrong or never comes. This site starts from one request and one result and climbs, one idea at a time, to topologies, task lifecycles, Agent Cards, the Agent2Agent (A2A) protocol, its boundary with the Model Context Protocol (MCP), security, reliability and tracing, asking one question at each step: what must both sides agree on?
An intake agent hands evidence collection to an assessment agent, and an underwriting agent waits for the result. If the reply comes late, comes twice or never comes, nothing on either side says what to do. An orchestrator is one answer, not the only one. Agent communication is the contract that makes delegation between agents safe, whoever routes the messages.
Sender, recipient, payload and correlation; a central orchestrator against peer-to-peer and hierarchical designs; request and reply against asynchronous tasks.
Messages, artifacts, typed schemas, errors and versions; submitted, working, input required, completed, failed and canceled.
Agent Cards and skill discovery, the A2A protocol and its transports, and why delegating to an agent differs from calling a tool.
Identity and delegated scopes, retries, idempotency and out-of-order delivery, and one causal timeline across all three agents.