Are APIs becoming obsolete? Think MCP, ACP, A2A, AGNTCY etc.
summary
Claim: APIs are not dead but must evolve into a hybrid stack where traditional REST/JSON APIs handle core transactions while agent protocols manage context, goals and long-running orchestration. Specifics: MCP model context protocol (Anthropic) uses JSON‑RPC and persistent state to reduce hallucinations; ACP agent communication protocol (IBM + BAI) is REST‑based for lightweight multiagent messaging; A2A agent to agent protocol (Google) supports multimodal, enterprise‑scale discovery and long‑running tasks. Surprising numbers: 57% of internet requests are API calls, $200B market today heading to $420B; developers must add context and agent governance skills.
AI-written summary · about
chapters (12)
- 0:00API evolution debate
- 1:06API evolution challenges
- 4:18Agentic disruption demands
- 6:07Model Context Protocol
- 8:20Agent Communication Protocol
- 11:40Agent-to-Agent Protocol
- 14:15MCP vs ACP vs A2A
- 15:39API evolution facets
- 17:27Hybrid architecture
- 18:29Developer skills & governance
- 19:53Protocol standardization roadmap
- 20:17APIs evolving hybrid future
related talks
27mAre APIs becoming obsolete? Think MCP, ACP, A2A, AGNTCY etc.
07mThe Transition from Strict APIs to Flexible, Context-Aware Interfaces
22mSurviving an interconnected world with API governance
26mAPIs in Agentic world
13mAre Your APIs Ready for AI Agents?
35mUnleash Your Inner API Architect: Build Agents That Deliver
24mThe API Economy's Next Chapter: AI Agents as First-Class Clients
21mBingo! Making Sense of AI-Ready APIs in a Buzzword World