emerging · -1.3 capability resourceschema

Cloud Infrastructure

Score 20.4 / 100 57 providers +1 via APIs 6 APIs Search apis.io →

Providers using this tag (57)

Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.

Exemplar 8 Complete, well-documented, and agent-ready
Strong 7 Solid coverage with minor gaps
Developing 13 Usable, with meaningful gaps to close
Thin 14 Limited public surface area
Emerging 9 Early or largely undocumented
Minimal 5 Almost no public developer surface
Unrated 1 Not yet scored

APIs with this tag (6)

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 →

Developing 4 Usable, with meaningful gaps to close
Thin 1 Limited public surface area
Minimal 1 Almost no public developer surface

Companies reaching this through an API (1)

These companies publish an API, specification or operation carrying “Cloud Infrastructure” 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.

VMware

Score breakdown

Frequency
45.8
log-scaled weighted occurrences
Breadth
0.7
spread across providers
Quality lift
40.6
mean composite of providers using it
Cohesion
4.4
strength of nearest seed neighbor

Related tags

Virtualization 5 co-occurrences Cluster 8 co-occurrences AI Infrastructure 5 co-occurrences Data Center 7 co-occurrences Edge Computing 5 co-occurrences Policies 5 co-occurrences Kubernetes 8 co-occurrences Containers 5 co-occurrences

Where this tag comes from

Provider tag57
Api tag6

Cohort brief

Auto-generated

The 51 providers in the APIs.io catalog tagged Cloud Infrastructure, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.

Providers
51
of 57 in the catalog
Mean Kin Score
42.8
+18.7 vs catalog 24.1
Mean Agent Readiness
23.6
+9.5 vs catalog 14.1
Spread
5.7–87.2
median 40.4 · σ 20.4
How the 51 split by band
Exemplar 8Strong 7Developing 12Thin 13Emerging 8Minimal 3
Facet averages, against the whole catalog
FacetThis cohortCatalogDifferenceScored
Developer Ergonomics 49.4 24.5 +24.9 51
Operational Transparency 33.6 13.2 +20.4 51
Contract Quality 36.6 18.6 +18 51
Access Clarity 44.8 30 +14.8 51
Discoverability 69.8 59.1 +10.7 51
Contract Governance 17.9 9.7 +8.2 51

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.

What this cohort publishes
ArtifactThis cohortCatalogDifference
MCP server (any) 38% 18% +20
MCP server (first-party) 37% 16% +21
Agent Skills 0% 0% 0
OAuth scopes 21% 13% +8
Security 98% 99% -1
Arazzo workflows 2% 1% +1
Governance rules 63% 36% +27

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.

Top by Kin Score
  1. 1 Confluent 87.2
  2. 2 Amazon SES 83.8
  3. 3 Microsoft Azure Cdn 77.1
  4. 4 Microsoft Azure Cache For Redis 74
  5. 5 Timescale 70.6
  6. 6 Microsoft Azure Private Link 70.2
  7. 7 LaserData 69.9
  8. 8 Azion 68.2
  9. 9 Phala Network 64.9
  10. 10 Insforge 63.7
Top by Agent Readiness
  1. 1 Insforge 56.6
  2. 2 The San Francisco Compute Company 55.9
  3. 3 Antimetal 55.1
  4. 4 Confluent 46.2
  5. 5 Zadara 45.9
  6. 6 Workspot 45.2
  7. 7 Limrun 44.4
  8. 8 Microsoft Azure Cache For Redis 39.3
  9. 9 Amazon SES 38.4
  10. 10 Microsoft Azure Cdn 38.4
All 57 members of this roster resolve to a provider in the catalog; 51 carry a score (89%). The figures above describe the scored members only.
Coverage caveat. 32 of 51 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 14 November 2026, across 41591 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.

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.
All 92 tools →

Call it yourself

curl for this page
This tag
curl "https://apis.io/api/v1/tags/cloud-infrastructure"
All tags
curl "https://apis.io/api/v1/tags?limit=25"
As a scored cohort (paid plan)
The distribution (Pro)

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.