API Evangelist started in 2010 because web APIs were becoming vital to the internet and the economy and almost nobody outside a small circle of developers understood why. Closing that gap was the whole project, and it still is.
In practice it is several things that feed each other. A blog with sixteen years of writing at apievangelist.com. A network of catalogs — providers, APIs, standards, regulations, vocabularies, headers, schema, rules, policies — each one a machine-readable index of a piece of this landscape. A search engine over the whole thing at APIs.io. A rating system, the Kin Score. A guidance catalog that distills the writing into topic-by-topic treatments. And a set of research reports people buy.
The organizing belief underneath all of it is that this space needs an independent, evidence-based, non-vendor account of itself — one that reads what providers actually publish rather than what they claim, and that says so plainly.
It is one person with a lot of tooling, which is worth knowing when you read anything here. The opinions are mine, they are argued rather than neutral, and the evidence behind them is public so you can check it.
