Standards
Identify and develop the standards required to ensure the interoperability of any aspect of business operations.
I have watched more interoperability die from a lack of boring agreements than from any hard technical problem. Two teams, two formats, two ways of saying the same date — and suddenly integration is a project instead of a given. Standards are the boring agreements that make the interesting work possible.
I help you identify which standards actually apply to your operations — OpenAPI, AsyncAPI, JSON Schema, Arazzo, and the domain-specific ones your industry already leans on — and where you may need to establish your own. Then I help you adopt them in a way that sticks, so they show up in your interfaces and your pipelines rather than living in a slide deck.
Standards are how you buy interoperability once instead of renegotiating it on every project. I have been tracking the API standards landscape since before most of these specifications had version numbers, and I bring that history to bear on what is worth your attention and what is noise.
What you walk away with
- A shortlist of the standards that matter for your specific operations
- A plan for adopting them consistently across teams and interfaces
- Interoperability treated as a default, not a per-project negotiation
Related reading
- The Promise of a New Specification
- What is OpenAPI?
- API Validator — conform your specs to the standards you choose (OpenAPI, AsyncAPI, Arazzo, JSON Schema)
Start with the research
Everything I know about choosing and adopting standards is already written down, priced, and yours to read tonight — no call, no scoping, no proposal. Start there.
-
The Agent-Era API Standards Onramp $25
The sequenced ladder from OpenAPI to agent payments — what rung you're on. -
The CAMARA Standard $500
What CAMARA publishes, what graduated, and who actually ships a conformant contract.
Free first: your Kin Score and Agent Readiness are already published on APIs.io. Look yourself up before you buy anything — the score costs nothing and it is the same rubric every report on this page is built from.
If you would rather have this done with you than do it yourself, I take a small number of engagements a year — [email protected].
Newsletters
Two emails, both Monday mornings. Take either, or both.
API Evangelist
Highlights of the stories, conversations, and API knowledge published across the industry each week.
The Specification Layer
What actually merged into the thirty specifications the Linux Foundation stewards — OpenAPI, AsyncAPI, JSON Schema, and the rest.
