Standards
StandardStandards
Providers using this tag (85)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Strong 6 Solid coverage with minor gaps
Developing 13 Usable, with meaningful gaps to close
Thin 23 Limited public surface area
Emerging 31 Early or largely undocumented
Minimal 12 Almost no public developer surface
APIs with this tag (80)
Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →
Exemplar 3 Complete, well-documented, and agent-ready
Strong 12 Solid coverage with minor gaps
Developing 12 Usable, with meaningful gaps to close
Thin 23 Limited public surface area
Emerging 30 Early or largely undocumented
Companies reaching this through an API (33)
These companies publish an API, specification or operation carrying “Standards” but do not classify their business under it. Listed unranked and kept out of the count above, because one tagged operation is not a statement about what a company does.
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 80 providers in the APIs.io catalog tagged Standards, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Contract Quality | 29.7 | 17.2 | +12.5 | 80 |
| Developer Ergonomics | 33.7 | 23.2 | +10.5 | 80 |
| Operational Transparency | 18.5 | 13 | +5.5 | 80 |
| Contract Governance | 11.2 | 6.5 | +4.7 | 80 |
| Discoverability | 62.1 | 57.9 | +4.2 | 80 |
| Access Clarity | 20.8 | 23.9 | -3.1 | 80 |
A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 13% | 13% | 0 |
| MCP server (first-party) | 13% | 12% | +1 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 20% | 11% | +9 |
| Security | 90% | 98% | -8 |
| Arazzo workflows | 3% | 2% | +1 |
| Governance rules | 25% | 16% | +9 |
mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.
- 1 Netcracker 62.8
- 2 Eclipse Foundation 62.6
- 3 Trisotech 58.4
- 4 Academy Software Foundation 55.4
- 5 OpenADR Alliance 55.3
- 6 GSMA 54.3
- 7 ETSI 53.7
- 8 MEF 51.9
- 9 EHRbase 51.1
- 10 IAB Tech Lab 50.8
- 1 EHRbase 46.1
- 2 ETSI 45.1
- 3 Eclipse Foundation 43.5
- 4 Telia Company 43
- 5 OpenTravel Alliance 41.5
- 6 GSMA 40.2
- 7 3GPP 39.2
- 8 IAB Tech Lab 37.6
- 9 Academy Software Foundation 35.7
- 10 CAMARA Project 35.3
Coverage caveat. 73 of 80 scored members had under half their catalog-attributable points satisfied at all (catalog_earned / catalog_max < 0.5). They are INCLUDED in the mean above. A large share here means the cohort mean is partly a measurement of how far our enrichment reached, not only of how these providers publish.Generated from the catalog build of 24 October 2026, across 31984 providers, using the same computation served by the APIs.io cohort API. Briefs are published for rosters of 5 or more scored providers; below that a distribution is not meaningful.
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.