Your next API consumer won't read your documentation. It won't open a support ticket when confused. And when something fails, it won't pause to think—it will retry. Relentlessly.
We're entering an era where AI agents don't just call APIs—they orchestrate workflows, complete tasks, update records, and make autonomous decisions . Yet most of us are still designing APIs for humans who read, reason, and give up gracefully.
This talk is a wake-up call and a practical guide.
I'll challenge you to think differently about two things you thought you understood: API design and API governance. Because the rules that served us well for human consumers? They're about to become liabilities.
Consider this: An agent may initiate tasks without immediate human review—but that doesn't transfer responsibility to the system itself . So who's accountable when an autonomous agent misinterprets your API and causes chaos? Your governance framework better have an answer.
You'll discover:
The three questions every agent will ask your API—and why most APIs fail to answer them
Why "good enough" governance becomes dangerous when consumers operate at machine speed
A new mental model for designing APIs that agents can discover, understand, and use safely
This isn't about distant futures. Agents are already conducting deep investigations across sources, managing workflows spanning multiple systems, and resolving issues autonomously . The question isn't if they'll consume your APIs—it's whether your APIs are ready.
You'll leave with a framework to evaluate your APIs today and a governance checklist for the agentic tomorrow.