Standards
Standardsstandards
Providers using this tag (135)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 2 Complete, well-documented, and agent-ready
Strong 9 Solid coverage with minor gaps
Developing 13 Usable, with meaningful gaps to close
Thin 26 Limited public surface area
Emerging 64 Early or largely undocumented
APIs with this tag (210)
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 2 Complete, well-documented, and agent-ready
Strong 4 Solid coverage with minor gaps
Developing 125 Usable, with meaningful gaps to close
Thin 12 Limited public surface area
Emerging 66 Early or largely undocumented
Minimal 1 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 135 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 | 27.2 | 17.5 | +9.7 | 135 |
| Contract Governance | 11.2 | 6.4 | +4.8 | 135 |
| Developer Ergonomics | 21.6 | 17.9 | +3.7 | 135 |
| Operational Transparency | 14.4 | 11.3 | +3.1 | 135 |
| Discoverability | 62.5 | 60.4 | +2.1 | 135 |
| Access Clarity | 18.4 | 22.3 | -3.9 | 135 |
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) | 18% | 16% | +2 |
| MCP server (first-party) | 5% | 7% | -2 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 12% | 9% | +3 |
| Security | 84% | 88% | -4 |
| Arazzo workflows | 4% | 2% | +2 |
| Governance rules | 37% | 13% | +24 |
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 Canvas LMS 76.2
- 2 API Evangelist 69.8
- 3 Nokia Network as Code 65.7
- 4 OpenADR Alliance 65.3
- 5 GSMA 59.8
- 6 ETSI 58.4
- 7 Reliance Jio 58.4
- 8 Voltus 56.4
- 9 Telia Company 55.2
- 10 Treblle 55.1
- 1 Telia Company 48.1
- 2 ETSI 47.9
- 3 API Evangelist 44.8
- 4 OpenTravel Alliance 43.9
- 5 Nokia Network as Code 43
- 6 GSMA 42.2
- 7 GSMA Open Gateway 39.5
- 8 Global System for Mobile Communications 39.1
- 9 Netcracker 36.8
- 10 3GPP 35.4
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for tags
7 MCP tools reach this
find_tagsBrowse and filter every tag in the catalog.get_cohortThis tag as a scored cohort — every provider carrying it, with scores.cohort_statsPRO — the distribution across this tag: mean, median, band split, adoption rates.cohort_rankingsPRO — the leaderboard, on composite AND agent-readiness axes.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/tags/standards"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/standards"
curl "https://apis.io/api/v1/cohorts/tag/standards/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.