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. I read 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.
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.
1 published
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.