Research
Publish research into vocabulary topics, outlining interfaces, standards, policies, rules, pipelines, and skills.
Before I have an opinion worth sharing, I do the reading. A lot of what I publish is really just research done in the open — surveying a landscape carefully enough that the patterns become visible. Most organizations never get to do this, because there is never any time carved out for it.
I conduct research into the topics your operations depend on — the vocabulary, the interfaces, the standards, the policies, the rules, the pipelines, and the skills — and publish it in a form your teams and your community can build on. I have been doing this kind of survey work across the API space for sixteen years, and I bring that method and that back-catalog to your specific questions.
Research is how you replace opinion with evidence, and how you find out what is actually true about your space before you commit real resources to it.
What you walk away with
- Structured research into the questions that matter to your operations
- Findings your teams can act on with confidence
- Evidence in place of guesswork
Related reading
Start with the research
Everything I know about the research already published, before commissioning any is already written down, priced, and yours to read tonight — no call, no scoping, no proposal. Start there.
-
Industry Report $500
Every provider in one market, scored on the same public rubric — the distribution, the leaders, the absent incumbents. -
Portfolio Report $750
One fund's whole book, read through the APIs its companies actually ship. -
Insights Bundle $1,500
One enterprise account read from both sides — demand from its job corpus and press, supply from the APIs it publishes.
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.
