API Management
API ManagementAPI-Managementapi-management
Providers using this tag (54)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 4 Complete, well-documented, and agent-ready
Strong 10 Solid coverage with minor gaps
Developing 23 Usable, with meaningful gaps to close
Thin 10 Limited public surface area
Emerging 6 Early or largely undocumented
Minimal 1 Almost no public developer surface
APIs with this tag (60)
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 4 Complete, well-documented, and agent-ready
Strong 11 Solid coverage with minor gaps
Developing 21 Usable, with meaningful gaps to close
Thin 14 Limited public surface area
Emerging 9 Early or largely undocumented
Minimal 1 Almost no public developer surface
Companies reaching this through an API (33)
These companies publish an API, specification or operation carrying “API Management” 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 54 providers in the APIs.io catalog tagged API Management, 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 | 51.1 | 19.8 | +31.3 | 54 |
| Developer Ergonomics | 47.1 | 23.4 | +23.7 | 54 |
| Access Clarity | 45.9 | 26.5 | +19.4 | 54 |
| Operational Transparency | 32.1 | 14 | +18.1 | 54 |
| Contract Governance | 18.1 | 6.4 | +11.7 | 54 |
| Discoverability | 67.2 | 61.2 | +6 | 54 |
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) | 24% | 10% | +14 |
| MCP server (first-party) | 17% | 13% | +4 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 28% | 11% | +17 |
| Security | 100% | 97% | +3 |
| Arazzo workflows | 19% | 2% | +17 |
| Governance rules | 67% | 14% | +53 |
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 Microsoft Azure 73.3
- 2 Jitterbit 70.1
- 3 Authentik 69.1
- 4 Microsoft Azure API Management 67
- 5 Workato 62.9
- 6 General Services Administration 62.2
- 7 Apigee 62.1
- 8 Netcracker 61
- 9 WSO2 60.6
- 10 IBM 60
- 1 Fusio 48.9
- 2 Microsoft Azure 46.2
- 3 Elva 44.8
- 4 Google Cloud Platform 42.3
- 5 AmunCore 41.5
- 6 IBM 37.3
- 7 Netcracker 36.8
- 8 Tyk 34
- 9 Axway 32.7
- 10 Zuplo 31.7
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.