Surviving an interconnected world with API governance
summary
Agentic AI increases API usage and turns APIs into product channels via MCP (model context protocol, launched by Entropic) that lets agents call web APIs and local data; agents sometimes plan and even delete chunks of code. Fixes are practical: API design (avoid GET-for-delete and 200-with-error bodies), documentation (fix undocumented endpoints and malformed OpenAPI), and access management (OIDC/OAuth, dynamic client registration, scoped tokens, rate limits). Use Stoplight, Postman and API gateways like Tyk to enforce these rules.
AI-written summary · about
chapters (12)
- 0:00API governance introduction
- 1:49Brief history of APIs and their evolution
- 3:36AI and agentic systems rise
- 5:47Model Context Protocol impact
- 7:38AI agents transforming workflows
- 9:24Future of AI and API growth
- 11:52Why API governance matters
- 13:17Three pillars of API governance
- 15:28API design pitfalls
- 16:10AI workflow documentation challenges
- 18:17Access management for AI agents
- 20:50Summary
related talks
21mAre APIs becoming obsolete? Think MCP, ACP, A2A, AGNTCY etc.
48mThe Death of API Management. Welcome to the Funeral
27mAre APIs becoming obsolete? Think MCP, ACP, A2A, AGNTCY etc.
35mUnleash Your Inner API Architect: Build Agents That Deliver
24mThe API Economy's Next Chapter: AI Agents as First-Class Clients
26mAPI Governance: The Latest Trends Making Teams Love API Standardization.
26mIf your APIs aren’t agent‑ready, your AI agent is just chat: [...]
24mAPIs Are the Nervous System of Agentic AI - Designing Agent-Ready APIs for Aut…