emerging · 0.2 market domain

Infrastructure as Code

Score 23.4 / 100 47 providers +14 via APIs 25 APIs Search apis.io →

Providers using this tag (47)

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

Exemplar 1 Complete, well-documented, and agent-ready
Strong 10 Solid coverage with minor gaps
Developing 10 Usable, with meaningful gaps to close
Thin 12 Limited public surface area
Emerging 9 Early or largely undocumented
Minimal 5 Almost no public developer surface

APIs with this tag (25)

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 5 Complete, well-documented, and agent-ready
Strong 6 Solid coverage with minor gaps
Developing 3 Usable, with meaningful gaps to close
Thin 8 Limited public surface area
Emerging 3 Early or largely undocumented

Companies reaching this through an API (14)

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

F5 Flightcontrol Genesys Harness HashiCorp IBM Linode OpenStack Oracle Red Hat Satellite Rubrik Software Development Lifecycle Speakeasy Stainless

Score breakdown

Frequency
50.3
log-scaled weighted occurrences
Breadth
1.2
spread across providers
Quality lift
45.6
mean composite of providers using it
Cohesion
9.4
strength of nearest seed neighbor

Related tags

Terraform 18 co-occurrences Configuration Management 11 co-occurrences Ansible 6 co-occurrences DevOps 31 co-occurrences Platform Engineering 6 co-occurrences GitOps 5 co-occurrences Orchestration 11 co-occurrences Deployment 15 co-occurrences

Where this tag comes from

Provider tag47
Api tag25

Cohort brief

Auto-generated

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

Providers
46
all scored
Mean Kin Score
37.8
+14.9 vs catalog 22.9
Mean Agent Readiness
19.3
+7.4 vs catalog 11.9
Spread
4.9–66.5
median 37.4 · σ 17.5
How the 46 split by band
Exemplar 1Strong 10Developing 10Thin 12Emerging 9Minimal 4
Facet averages, against the whole catalog
FacetThis cohortCatalogDifferenceScored
Developer Ergonomics 45.8 23.2 +22.6 46
Contract Quality 32.5 17.6 +14.9 46
Operational Transparency 28.2 13.7 +14.5 46
Contract Governance 15.3 6.3 +9 46
Access Clarity 35.5 26.5 +9 46
Discoverability 62.7 58.1 +4.6 46

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) 37% 14% +23
MCP server (first-party) 30% 12% +18
Agent Skills 0% 0% 0
OAuth scopes 17% 11% +6
Security 98% 98% 0
Arazzo workflows 2% 2% 0
Governance rules 35% 14% +21

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 Databricks Asset Bundles 66.5
  2. 2 Red Hat Ansible Automation Platform 66
  3. 3 Env0 64.6
  4. 4 Modal 64.5
  5. 5 Koyeb 63.5
  6. 6 Cisco Catalyst SD-WAN 63.2
  7. 7 Chronosphere 62.4
  8. 8 Chef Software 58.7
  9. 9 Amazon CloudFormation 58.2
  10. 10 Amazon Proton 55.5
Top by Agent Readiness
  1. 1 Chronosphere 56.6
  2. 2 Koyeb 39.8
  3. 3 Scale Computing 35.4
  4. 4 Modal 33.5
  5. 5 Red Hat Ansible Automation Platform 33.4
  6. 6 Cisco Catalyst SD-WAN 33.1
  7. 7 Terraform 31.8
  8. 8 Env0 29.9
  9. 9 Luther Systems 29.2
  10. 10 Amazon Proton 28.5
All 47 members of this roster resolve to a scored provider in the catalog.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.

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/infrastructure-as-code"
All tags
curl "https://apis.io/api/v1/tags?limit=25"
As a scored cohort
curl "https://apis.io/api/v1/cohorts/tag/infrastructure-as-code"
The distribution (Pro)
curl "https://apis.io/api/v1/cohorts/tag/infrastructure-as-code/stats" \
  -H "X-API-Key: $APIS_IO_KEY"

Discovery needs no key. Ratings and market analysis are Pro.

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.