API Experience Meets Agentic AI

As part of recent work on spec-driven development I sat down for conversation with Chris Hood about experience-based API design, arguing that APIs should be expressed in human, business-oriented language rather than CRUD-centric engineering terms to improve contextual understanding. we discuseds why traditional REST approaches may be insufficient for AI and agent-based systems, concerns about introducing new protocols like MCP, and the “agentic API” paradigm for agent-to-agent communication with built-in security and web-embedded protocols. We also explore how AI could help by making APIs more intelligent and contextual, and by incorporating feedback loops where agents and humans report missing skills.