Gateways
GatewayGateways
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 7 Solid coverage with minor gaps
Developing 7 Usable, with meaningful gaps to close
Thin 12 Limited public surface area
APIs with this tag (95)
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 8 Complete, well-documented, and agent-ready
Strong 14 Solid coverage with minor gaps
Developing 34 Usable, with meaningful gaps to close
Thin 32 Limited public surface area
Emerging 7 Early or largely undocumented
Companies reaching this through an API (86)
These companies publish an API, specification or operation carrying “Gateways” 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.
Show all 86 companies ↓
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 31 providers in the APIs.io catalog tagged Gateways, 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 | 52.1 | 17.6 | +34.5 | 31 |
| Developer Ergonomics | 46.7 | 23.2 | +23.5 | 31 |
| Access Clarity | 49.7 | 26.5 | +23.2 | 31 |
| Operational Transparency | 35.4 | 13.7 | +21.7 | 31 |
| Contract Governance | 14.7 | 6.3 | +8.4 | 31 |
| Discoverability | 64.7 | 58.1 | +6.6 | 31 |
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) | 26% | 14% | +12 |
| MCP server (first-party) | 23% | 12% | +11 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 6% | 11% | -5 |
| Security | 100% | 98% | +2 |
| Arazzo workflows | 13% | 2% | +11 |
| Governance rules | 71% | 14% | +57 |
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 79.9
- 2 The Things Network / The Things Stack 79.2
- 3 Couchbase 68.8
- 4 Zuplo 62.3
- 5 Hookdeck 60.8
- 6 Vercel 59
- 7 Amazon Storage Gateway 58.3
- 8 ReefAPI 57.7
- 9 Portkey 57
- 10 Onecli 53.8
- 1 Zuplo 51.5
- 2 Keywords AI 48.2
- 3 OpenRouter 47.5
- 4 Vercel 45.7
- 5 Broadcom 44.3
- 6 Dedalus Labs 40.7
- 7 Portkey 35.6
- 8 WSO2 35.4
- 9 ReefAPI 34.9
- 10 The Things Network / The Things Stack 33.7
Coverage caveat. 16 of 31 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 5 October 2026, across 29093 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.