A2A Interoperability
Uses HTTP, SSE, and JSON-RPC to ensure compatibility with existing systems. It defines a “task” object with a lifecycle and an “artifact” as the task output. It supports message negotiation using MIME-type “parts” including JSON, images, or video.
Agents describe their functions in structured JSON files called Agent Cards. Cards list each agent’s capabilities, supported modalities, and accepted content types. Client agents use cards to select the correct remote agent for each task. Content-type negotiation supports iframes, video, HTML forms, and structured outputs. No requirement for shared context or memory between agents.
The protocol supports both synchronous and asynchronous execution patterns. It supports short tasks and long-running operations with real-time status updates. It enables state synchronization and failure handling between client and remote agents.
