Service Mesh
Providers using this tag (31)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 4 Solid coverage with minor gaps
Developing 8 Usable, with meaningful gaps to close
Thin 12 Limited public surface area
Emerging 4 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 1 Complete, well-documented, and agent-ready
Strong 2 Solid coverage with minor gaps
Developing 6 Usable, with meaningful gaps to close
Thin 13 Limited public surface area
Emerging 5 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.
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 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.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Developer Ergonomics | 44.8 | 23.2 | +21.6 | 30 |
| Contract Quality | 37.7 | 17.6 | +20.1 | 30 |
| Operational Transparency | 31.3 | 13.7 | +17.6 | 30 |
| Contract Governance | 13.3 | 6.3 | +7 | 30 |
| Discoverability | 64.9 | 58.1 | +6.8 | 30 |
| Access Clarity | 31.9 | 26.5 | +5.4 | 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.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 17% | 14% | +3 |
| MCP server (first-party) | 10% | 12% | -2 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 10% | 11% | -1 |
| Security | 100% | 98% | +2 |
| Arazzo workflows | 0% | 2% | -2 |
| Governance rules | 50% | 14% | +36 |
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 Kong 73.2
- 2 Calico 66.3
- 3 Solo.io 63
- 4 Gloo 57.8
- 5 AWS App Mesh 55.1
- 6 Buoyant 54
- 7 Amazon VPC Lattice 50.3
- 8 Gloo Mesh 47.3
- 9 Envoy 44
- 10 Apache Dubbo 42.9
- 1 Kong 46.9
- 2 Solo.io 37.6
- 3 AWS App Mesh 37.1
- 4 Calico 36.2
- 5 Gloo 34.4
- 6 APIClarity 32.5
- 7 Envoy 27.3
- 8 Traefik Mesh 26.7
- 9 Google Cloud Service Mesh 26.5
- 10 Gloo Mesh 26.3
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.