Data Center
Data-CenterData Centers
Providers using this tag (160)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 2 Solid coverage with minor gaps
Developing 10 Usable, with meaningful gaps to close
Thin 9 Limited public surface area
Emerging 30 Early or largely undocumented
Minimal 103 Almost no public developer surface
APIs with this tag (19)
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 1 Complete, well-documented, and agent-ready
Strong 3 Solid coverage with minor gaps
Developing 7 Usable, with meaningful gaps to close
Thin 3 Limited public surface area
Emerging 5 Early or largely undocumented
Companies reaching this through an API (12)
These companies publish an API, specification or operation carrying “Data Center” 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 134 providers in the APIs.io catalog tagged Data Center, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Contract Governance | 3.5 | 6.3 | -2.8 | 134 |
| Discoverability | 54.8 | 58.1 | -3.3 | 134 |
| Operational Transparency | 5.3 | 13.7 | -8.4 | 134 |
| Developer Ergonomics | 14.8 | 23.2 | -8.4 | 134 |
| Contract Quality | 8.2 | 17.6 | -9.4 | 134 |
| Access Clarity | 15.1 | 26.5 | -11.4 | 134 |
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) | 6% | 14% | -8 |
| MCP server (first-party) | 3% | 12% | -9 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 5% | 11% | -6 |
| Security | 97% | 98% | -1 |
| Arazzo workflows | 0% | 2% | -2 |
| Governance rules | 6% | 14% | -8 |
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 Nutanix 67.4
- 2 Cisco Intersight 59.7
- 3 Cisco ACI 55.6
- 4 VMware 52.3
- 5 Eaton 49.5
- 6 Microsoft Windows Server 48.1
- 7 TensorWave 48
- 8 CoreWeave 44.7
- 9 Brocade 44.4
- 10 BitFury 41.4
- 1 Cisco ACI 35.5
- 2 Equinix 35.3
- 3 Cisco Intersight 29
- 4 Reed Semiconductor 26.3
- 5 Vapor IO 26.1
- 6 HorizonIQ 25.6
- 7 Vertiv 25.5
- 8 VMware 24.8
- 9 Positron 23.9
- 10 TensorWave 23.8
Coverage caveat. 129 of 134 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 5 October 2026, across 29093 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.