Specification
SpecificationsSpecification
Providers using this tag (30)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Thin 6 Limited public surface area
Emerging 12 Early or largely undocumented
Minimal 5 Almost no public developer surface
APIs with this tag (75)
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 6 Complete, well-documented, and agent-ready
Strong 5 Solid coverage with minor gaps
Developing 15 Usable, with meaningful gaps to close
Thin 23 Limited public surface area
Emerging 25 Early or largely undocumented
Minimal 1 Almost no public developer surface
Companies reaching this through an API (45)
These companies publish an API, specification or operation carrying “Specification” 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 29 providers in the APIs.io catalog tagged Specification, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Developer Ergonomics | 32.5 | 23.2 | +9.3 | 29 |
| Contract Quality | 26.6 | 17.6 | +9 | 29 |
| Operational Transparency | 20.9 | 13.7 | +7.2 | 29 |
| Contract Governance | 11.8 | 6.3 | +5.5 | 29 |
| Discoverability | 59.4 | 58.1 | +1.3 | 29 |
| Access Clarity | 17.6 | 26.5 | -8.9 | 29 |
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) | 14% | 14% | 0 |
| MCP server (first-party) | 14% | 12% | +2 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 7% | 11% | -4 |
| Security | 90% | 98% | -8 |
| Arazzo workflows | 3% | 2% | +1 |
| Governance rules | 38% | 14% | +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 Postman 79.6
- 2 GSMA 53.8
- 3 Buildpacks Io 53.4
- 4 AGNTCY 48.4
- 5 AsyncAPI 45.7
- 6 Hey API 42.8
- 7 Craft.io 39.5
- 8 Acelab 38.2
- 9 CloudEvents 37.6
- 10 Alliance for OpenUSD 29.8
- 1 Postman 54.9
- 2 Craft.io 52.9
- 3 GSMA 40.8
- 4 AGNTCY 39.2
- 5 OpenFeature 33.1
- 6 Hey API 32.6
- 7 Open Geospatial Consortium (OGC) 29.1
- 8 Buildpacks Io 28.7
- 9 Acelab 25.5
- 10 AsyncAPI 25.3
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.