API Gateway
API GatewayAPI gatewayapi-gateway
Providers using this tag (103)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 11 Solid coverage with minor gaps
Developing 30 Usable, with meaningful gaps to close
Thin 35 Limited public surface area
Emerging 22 Early or largely undocumented
Minimal 4 Almost no public developer surface
APIs with this tag (65)
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 →
Strong 6 Solid coverage with minor gaps
Developing 17 Usable, with meaningful gaps to close
Thin 24 Limited public surface area
Emerging 15 Early or largely undocumented
Minimal 3 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 103 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 |
|---|---|---|---|---|
| Contract Quality | 40.3 | 17.5 | +22.8 | 103 |
| Developer Ergonomics | 37.4 | 17.9 | +19.5 | 103 |
| Operational Transparency | 25.4 | 11.3 | +14.1 | 103 |
| Access Clarity | 35.1 | 22.3 | +12.8 | 103 |
| Contract Governance | 14.7 | 6.4 | +8.3 | 103 |
| Discoverability | 67.6 | 60.4 | +7.2 | 103 |
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) | 22% | 16% | +6 |
| MCP server (first-party) | 11% | 7% | +4 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 12% | 9% | +3 |
| Security | 98% | 88% | +10 |
| Arazzo workflows | 11% | 2% | +9 |
| Governance rules | 55% | 13% | +42 |
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 Solo.io 68.4
- 2 Amazon API Gateway 65.8
- 3 Vendia 63.7
- 4 IBM 62.6
- 5 Boomi 62.3
- 6 Cloudflare 62
- 7 Apigee 59.5
- 8 Red Hat 59.1
- 9 Microsoft Azure API Management 58
- 10 Tyk 57.7
- 1 Red Hat 52.3
- 2 Cloudflare 44.5
- 3 Oracle 41.9
- 4 Speko 41.1
- 5 IBM 39.4
- 6 Google 39.2
- 7 Vendia 38.3
- 8 Solo.io 37.6
- 9 RouterPlex 37.2
- 10 Sapiom 36.3
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/tags/api-gateway"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/api-gateway"
curl "https://apis.io/api/v1/cohorts/tag/api-gateway/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.