emerging · -0.6 marketcapability domainschemaresource

Hosting

Score 21.5 / 100 102 providers +14 via APIs 18 APIs Search apis.io →

Providers using this tag (102)

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

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

APIs with this tag (18)

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

Companies reaching this through an API (14)

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

AgentStack Agoragentic Automattic Blubrry API DBOS Expo GitHub Glama Hlix Huly Newfold TaiVPS Unstoppable Domains Zyte

Score breakdown

Frequency
52.9
log-scaled weighted occurrences
Breadth
1.3
spread across providers
Quality lift
35.1
mean composite of providers using it
Cohesion
6.2
strength of nearest seed neighbor

Related tags

Domains 29 co-occurrences Web Hosting 8 co-occurrences DNS 13 co-occurrences VPS 7 co-occurrences Cloud 42 co-occurrences Deployment 18 co-occurrences Platform-as-a-Service 7 co-occurrences SSL 6 co-occurrences

Where this tag comes from

Provider tag102
Api tag18
Openapi tag2
Openapi op tag3

Cohort brief

Auto-generated

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

Providers
90
of 102 in the catalog
Mean Kin Score
36.1
+12.0 vs catalog 24.1
Mean Agent Readiness
25.5
+11.4 vs catalog 14.1
Spread
2.2–84.6
median 35.9 · σ 18.6
How the 90 split by band
Exemplar 3Strong 13Developing 20Thin 25Emerging 23Minimal 6
Facet averages, against the whole catalog
FacetThis cohortCatalogDifferenceScored
Access Clarity 45 30 +15 90
Contract Quality 31.1 18.6 +12.5 90
Developer Ergonomics 36.9 24.5 +12.4 90
Operational Transparency 20.9 13.2 +7.7 90
Discoverability 64.9 59.1 +5.8 90
Contract Governance 15.5 9.7 +5.8 90

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) 29% 18% +11
MCP server (first-party) 26% 16% +10
Agent Skills 0% 0% 0
OAuth scopes 13% 13% 0
Security 99% 99% 0
Arazzo workflows 1% 1% 0
Governance rules 60% 36% +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.

Top by Kin Score
  1. 1 Appwrite 84.6
  2. 2 Amazon Lightsail 76.4
  3. 3 Amazon Amplify 75.8
  4. 4 Upsun 66.3
  5. 5 Hostinger 65.9
  6. 6 cPanel 65.1
  7. 7 Microsoft Azure App Service 63.8
  8. 8 Koyeb 63.2
  9. 9 SAKURA internet 62.6
  10. 10 Vercel 62.5
Top by Agent Readiness
  1. 1 Blazing Bullet Private Limited 68.7
  2. 2 ex2-com 59.8
  3. 3 Upsun 59.4
  4. 4 Appwrite 56.3
  5. 5 AgentsPodium 53.9
  6. 6 AgentSpace 51.8
  7. 7 cPanel 51.5
  8. 8 Chinaready 51.4
  9. 9 Hostilo 49.1
  10. 10 Render 47.8
All 102 members of this roster resolve to a provider in the catalog; 90 carry a score (88%). The figures above describe the scored members only.
Coverage caveat. 56 of 90 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/hosting"
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.