Deep-Dives / Protocols & Interop
Protocols & Interop
The protocol layer of the agent stack — MCP, A2A, tool-calling standards, capability discovery — and how systems plug together.
- Why Interop Matters: The M×N ProblemHow connecting M agents to N systems by hand explodes, and why a protocol layer is the structural fix.
- Tool Calling Standards: JSON SchemaThe universal declare/select/execute/return contract, the portable JSON Schema core, and where providers differ.
- MCP: Hosts, Clients, ServersThe Model Context Protocol participant model, resources/tools/prompts, JSON-RPC lifecycle, and transports.
- Agent-to-Agent CommunicationDelegating to opaque peer agents: Agent Cards, tasks, messages, artifacts, and long-running work.
- Structured Tool I/O & ValidationInput and output as two trust boundaries: structural-then-semantic validation, and why typed output is still untrusted.
- Capability Discovery & NegotiationRuntime discovery, feature-test version negotiation, and why discovery describes ability not permission.
- Building an Interoperable AgentComparing tool calling, MCP, and A2A; a decision rule and one normalised registry architecture.
- A2A v1.0: Task Lifecycle, Messages, ArtifactsA2A hit v1.0 in April 2026 — nine task states (not four), Message vs Artifact split, A2A-Version header, breaking changes from pre-1.0, and 150+ org adoption.
- Agent Cards & DiscoveryA2A's /.well-known/agent.json — capability declaration, extended cards, signing, caching, and how it compares with MCP registry-based discovery.
- ACP: What HappenedA short post-mortem — ACP existed, was REST-native, was contributed to the Linux Foundation in July 2025, and folded into A2A. Useful because search still surfaces stale 'ACP vs A2A' content.
- AP2 & Agent CommerceThe Agent Payments Protocol — Intent / Cart / Payment as W3C VCs, why it sits above A2A/MCP rather than inside them, and the stablecoin-rail pitch to keep skeptical of.
- agents.json & OpenAPI for AgentsThe agents.json v0.1 spec on top of OpenAPI, the AGENTS.md convention adopted by 20k+ repos, and why "just point the agent at your OpenAPI" does not fully work.
- ACP: The Agent Client ProtocolZed's editor-to-agent protocol — the initialize capability gate, the prompt turn, and the filesystem inversion that makes the client, not the agent, hold the disk.
- Poppy: The Personal Agent ProtocolSierra and Meta's protocol for someone else's agent signing in as your customer — the well-known file that points the other way, the session that starts with no user in it, two reserved scopes that cannot express risk, and the per-company pseudonym that deletes a key you were using.
- Web Bot Auth: Signing an Agent’s RequestsA signature proves which operator's software sent the request and nothing else — not which user, not the errand, not a scope — so it retires impersonation and leaves delegation untouched. Adopted as the webbotauth working group's first draft in September 2026 over RFC 9421, which is the stable half; verification spread much faster than signing (Cloudflare's Verified Bots Program, Akamai, AWS WAF, HUMAN, Vercel, Stytch against Google, OpenAI and Bedrock AgentCore), so a signature-required rule still blocks most legitimate agents. Three buckets, not two — and never let a verified operator name reach where a user identity is checked.