emerging · -1.1 capabilitymarket schemaindustry

Service Mesh

Score 20.5 / 100 31 providers +7 via APIs 27 APIs Search apis.io →

Providers using this tag (31)

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

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

APIs with this tag (27)

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

Companies reaching this through an API (7)

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

A10 Networks Amazon ECS Envoy Proxy HashiCorp HashiCorp Cloud Platform Red Hat OpenShift Traefik Labs

Score breakdown

Frequency
44.1
log-scaled weighted occurrences
Breadth
0.4
spread across providers
Quality lift
38.8
mean composite of providers using it
Cohesion
10.6
strength of nearest seed neighbor

Related tags

Envoy 11 co-occurrences Istio 8 co-occurrences mTLS 7 co-occurrences Traffic Management 8 co-occurrences Multi-Cluster 5 co-occurrences Kubernetes 29 co-occurrences Cloud-Native 14 co-occurrences CNCF 5 co-occurrences

Where this tag comes from

Api tag27
Provider tag31

Cohort brief

Auto-generated

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

Providers
30
of 31 in the catalog
Mean Kin Score
40
+15.9 vs catalog 24.1
Mean Agent Readiness
21.8
+7.7 vs catalog 14.1
Spread
7.5–73.8
median 37 · σ 17.1
How the 30 split by band
Exemplar 3Strong 3Developing 8Thin 10Emerging 5Minimal 1
Facet averages, against the whole catalog
FacetThis cohortCatalogDifferenceScored
Developer Ergonomics 46.8 24.5 +22.3 30
Contract Quality 38.2 18.6 +19.6 30
Operational Transparency 32.5 13.2 +19.3 30
Discoverability 66.3 59.1 +7.2 30
Contract Governance 16.2 9.7 +6.5 30
Access Clarity 29.3 30 -0.7 30

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) 20% 18% +2
MCP server (first-party) 13% 16% -3
Agent Skills 0% 0% 0
OAuth scopes 10% 13% -3
Security 100% 99% +1
Arazzo workflows 0% 1% -1
Governance rules 67% 36% +31

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 Kong 73.8
  2. 2 Amazon VPC Lattice 73.5
  3. 3 Calico 67.3
  4. 4 Solo.io 62.3
  5. 5 Gloo 60.4
  6. 6 Google Cloud Service Mesh 59.7
  7. 7 Google Anthos 54
  8. 8 Gloo Mesh 51.9
  9. 9 Buoyant 51.2
  10. 10 Envoy 43.9
Top by Agent Readiness
  1. 1 Kong 44.3
  2. 2 Amazon VPC Lattice 42.9
  3. 3 Calico 40.4
  4. 4 Google Cloud Service Mesh 35.8
  5. 5 Solo.io 34.8
  6. 6 Gloo 34.5
  7. 7 Google Anthos 34.1
  8. 8 APIClarity 30.7
  9. 9 Gloo Mesh 29.3
  10. 10 Traefik Mesh 27.3
All 31 members of this roster resolve to a provider in the catalog; 30 carry a score (97%). The figures above describe the scored members only.
Coverage caveat. 21 of 30 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/service-mesh"
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.