API Gateway
Providers using this tag (107)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 10 Complete, well-documented, and agent-ready
Strong 21 Solid coverage with minor gaps
Developing 24 Usable, with meaningful gaps to close
Thin 29 Limited public surface area
Emerging 19 Early or largely undocumented
Minimal 4 Almost no public developer surface
APIs with this tag (75)
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 10 Complete, well-documented, and agent-ready
Strong 8 Solid coverage with minor gaps
Developing 19 Usable, with meaningful gaps to close
Thin 20 Limited public surface area
Emerging 17 Early or largely undocumented
Minimal 1 Almost no public developer surface
Companies reaching this through an API (29)
These companies publish an API, specification or operation carrying “API Gateway” 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
Where this tag sits
Related tags
Where this tag comes from
Markets provisional
Kin Score markets whose measured providers carry this tag. Share is the fraction of the market's measured providers that carry it — it describes the market, not this tag.
| Market | Share of the market's providers |
|---|---|
| API Management (gateways, portals, service mesh, proxies) | 49% |
Cohort brief
Auto-generatedThe 105 providers in the APIs.io catalog tagged API Gateway, 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 | 47.5 | 24.5 | +23 | 105 |
| Contract Quality | 40.5 | 18.6 | +21.9 | 105 |
| Operational Transparency | 30.7 | 13.2 | +17.5 | 105 |
| Access Clarity | 41.8 | 30 | +11.8 | 105 |
| Contract Governance | 20.6 | 9.7 | +10.9 | 105 |
| Discoverability | 68.4 | 59.1 | +9.3 | 105 |
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) | 29% | 18% | +11 |
| MCP server (first-party) | 26% | 16% | +10 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 21% | 13% | +8 |
| Security | 99% | 99% | 0 |
| Arazzo workflows | 6% | 1% | +5 |
| Governance rules | 70% | 36% | +34 |
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 WSO2 84.3
- 2 Cloudflare 82.5
- 3 Microsoft Azure API Management 78.5
- 4 Amazon API Gateway 77.4
- 5 F5 74.7
- 6 Kong 73.8
- 7 Jitterbit 73.1
- 8 Zuplo 72.8
- 9 Google Cloud API Gateway 71.8
- 10 Apigee 67.6
- 1 Cloudflare 69.6
- 2 kymaapi-com 61.4
- 3 Speko 61
- 4 Zuplo 57.3
- 5 IBM API Connect 54.7
- 6 AIMLAPI 54
- 7 Fusio 53.4
- 8 Citi 52.9
- 9 F5 50.2
- 10 XGuard 46.5
Coverage caveat. 58 of 105 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.