I require that every API provider ships an agents.md file that tells an automated consumer exactly how to behave when working with the API, including the conventions, the guardrails, and the workflows we expect agents to follow. This is the operating manual we would hand a capable junior engineer, except it is written for a machine that will read it literally. I insist on it because agents will act on our APIs with or without our guidance, and the responsible move is to author that guidance ourselves rather than let each integrator invent their own assumptions. Every API must treat agents.md as a first-class contract artifact, versioned and maintained alongside the code.
Agent Readiness with agents.md
Rules
APIs.json Agent Agents Md Info
APIs should link an agents.md file so AI agents have documented instructions and conventions for working with the API. Declaring a property of type AgentsMd in the APIs.json properties array publis...
Strategies
APIs Are Ready for AI Agents
I want every API we operate to be ready for the agents that are now showing up as first-class consumers alongside our human developers. That means our APIs publish the machine-readable signposts ag...
Experiences
Agent Experience
Agent experience is developer experience for machines. As AI agents become first-class consumers of APIs, the experience they have discovering, understanding, authenticating, and calling an API mat...
Automation
Automating business operations is a primary driver for adopting and governing APIs, enabling organizations to achieve the scale, speed, and quality needed to remain competitive in global markets. A...
Lifecycle
travel_explore Discovery Production
Discovery is how APIs get found and reused instead of rebuilt. APIs.json, catalogs, and search make the APIs I operate visible to the people who need them. Good discovery is what turns a pile of AP...
