API Evangelist

Nineteen keys in the x-fern- namespace, thirteen providers.

There is a new file companies are starting to put on their domain, and almost nobody has noticed it yet.

After a week of writing about vocabularies with nineteen and thirty-six keys, Mintlify is a relief.

I have written twice recently about the two excuses I hear most often when I walk a company through their public API presence.

Nineteen keys in the x-stainless- namespace, across twenty-five providers.

A friend of mine, Mike from Curity, gave a talk at apidays Munich this year with a title I have not been able to put down: When AI Agents Start Acting, APIs Become Execution Contracts.

I gave Agents Inherit Your Governance — Whether You Meant Them To or Not at APIdays Toronto this week, the first live outing of an argument I have been assembling in the APIs.io catalog all year.

x-stoplight appears 7,708 times in my catalog, across 162 OpenAPI documents belonging to thirty-seven providers.

I sat for a fireside chat this week on the architecture and strategy behind the Kin Score — what it is, how the agent orchestration that produces it works, what the early findings look like, and how any of it becomes a business.

Agent skills are the newest thing I am watching closely, and they are the clearest case yet of a technology that brings real, obvious value and a fresh set of problems in the exact same package.

I found x-readme in eighty providers’ OpenAPI documents, 1,076 times across 320 files.

There is a category of standard that nobody sets out to create.

An Italian company called Plumma reached out to me last week about the state of operator APIs in Latin America, we had a short call, and then I did what I always do afterward — I went and profiled them.

I keep coming back to the same wall.