verified API Evangelist Product
Standard Reports
The gap between claiming a standard and shipping one.
What the body publishes, how much of it has actually graduated, who staffs and who steers the coalition, and the number that matters most — how many organizations that claim the standard publish a contract a developer can download, price, and call. The report reads the specifications, the governance record, and the machine-readable surface of every claimed implementer. Where a composite score is the wrong instrument for a standards body, the report says so in its own section rather than letting the number stand as a verdict.
Who buys it
The body and its participants, implementers weighing adoption, and the vendors and investors betting on it.
Every Standard Report is free
A specification is a public good. Everybody in a market is asked to adopt it, so the honest read of how far adoption actually got should not sit behind a paywall — that is the same thing that keeps the gap invisible in the first place. Every report in this line downloads free, with no signup and no checkout, including the machine-readable data bundle underneath it. The Market, Portfolio and Insights lines are what pay for the research.
Claiming is cheap. Shipping is not.
Every standards body has a membership page, a specification set, and a story about industry alignment. The question that actually matters to anyone building on it is narrower: of the organizations that claim the standard, how many publish a contract a developer can download, price, and call — self-serve, today? That ratio is the spine of a Standard Report, and it is usually the number nobody has computed.
What's in every one
- What the standard is, and what it is not
- What the body publishes — repositories, categories, and the actual API surface
- The maturity ladder — how much has genuinely graduated, and how long the flagship set has been in progress
- The coalition — who staffs it, who steers it, and who does the work, named
- The adoption gap, category by category
- Conformance — including a document-level diff where the programme allows one
- The regulatory layer — which regimes touch this subject matter, and whether any compels it
- The scoring caveat — where a composite score is the wrong instrument, said plainly
- What would have to be true — the checkable signals that would change the call
- The investable thesis
Fair to the body, useful to everyone else
A standards body scored on a provider rubric will score badly for structural reasons — it doesn't operate APIs, it publishes specifications. Every Standard Report carries a section that says so explicitly rather than letting a number stand as a verdict, and a section on what would have to change for the call to change. The goal is a read the body itself can use, not a scoreboard.
What you get
The data bundle is the evidence behind every number — layered per-entity data, an APIs.json manifest, a conversation primer, and a data dictionary — packaged to drop straight into the AI tool of your choice. Converse with the research you bought, check any claim against the source, and take it further than the PDF.
12 published
The CAMARA Standard
The industry that standardised itself without being told to — 1,369 participants, 487 organizations, 93 repositories, nothing graduated, and exactly one operator on ea...
The OpenAPI Standard
14,257 real OpenAPI documents, read as published. One in three carries no callable address, and OAS 3.2.0 reached four of them in ten months.
The AsyncAPI Standard
Across 26,722 providers, exactly one publishes an AsyncAPI document — and 159 describe their events in OpenAPI instead. In its own strongest segment, AsyncAPI is losin...
The JSON Schema Standard
9,439,146 schema objects measured inside published API contracts — and an industry still writing with the vocabulary it had in 2013.
The Arazzo Standard
812 Arazzo documents exist across all of public GitHub. API Evangelist holds 5,276. And the market adopted the specification as a test format, not a description format.
The Model Context Protocol Standard
3,060 providers carry an MCP artifact. 672 publish a server you can actually reach. And the median server exposes 11 tools while the largest exposes 588.
The OpenID Connect Standard
The identity layer under everything, declared in 102 of 14,195 published API contracts — 0.72%.
The OpenAPI Overlay Standard
122 stars, 21 contributors, two people writing four fifths of it — and Elastic, MongoDB, Cloudinary and Vercel running it in production. Attention and adoption have co...
The GraphQL Standard
793 providers publish a GraphQL schema defining 69,521 types — the second-largest description corpus measured here, and the one JSON Schema cannot reach.
The OAuth 2.0 Standard
775 published contracts still declare the implicit flow — 28.9% of every OAuth-using contract in the corpus, for a flow removed from OAuth 2.1.
The ARD Standard
Eleven of the largest agent builders specified the discovery layer. Nine companies publish it, seven of them are outsiders, none is fully conformant — and two fail on ...
The A2A Standard
65 organizations publish an Agent Card. Ten publish one a conformant client can read. And the ten that got it right score lower on API maturity than the forty-one that...
Want your standard read this way?
If you steer a body, implement one, or are betting on one, the same read can be run on it — including the parts that are uncomfortable.