API Management
API Managementapi-management
Providers using this tag (85)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 14 Solid coverage with minor gaps
Developing 28 Usable, with meaningful gaps to close
Thin 21 Limited public surface area
Emerging 18 Early or largely undocumented
Minimal 3 Almost no public developer surface
APIs with this tag (59)
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 8 Solid coverage with minor gaps
Developing 17 Usable, with meaningful gaps to close
Thin 18 Limited public surface area
Emerging 13 Early or largely undocumented
Minimal 2 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 85 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 | 44.4 | 17.5 | +26.9 | 85 |
| Developer Ergonomics | 38.6 | 17.9 | +20.7 | 85 |
| Access Clarity | 40.6 | 22.3 | +18.3 | 85 |
| Operational Transparency | 28.4 | 11.3 | +17.1 | 85 |
| Contract Governance | 14.3 | 6.4 | +7.9 | 85 |
| Discoverability | 67.2 | 60.4 | +6.8 | 85 |
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) | 25% | 16% | +9 |
| MCP server (first-party) | 13% | 7% | +6 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 27% | 9% | +18 |
| Security | 100% | 88% | +12 |
| Arazzo workflows | 19% | 2% | +17 |
| Governance rules | 65% | 13% | +52 |
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 Salesforce 83.3
- 2 Postman 64.5
- 3 IBM 62.6
- 4 Google Cloud Platform 62.4
- 5 Boomi 62.3
- 6 Workato 61.3
- 7 Apigee 59.5
- 8 Red Hat 59.1
- 9 ETSI 58.4
- 10 Zuplo 58.1
- 1 Red Hat 52.3
- 2 Salesforce 52.2
- 3 Microsoft Azure 49.6
- 4 ETSI 47.9
- 5 Google Cloud Platform 44.5
- 6 Oracle 41.9
- 7 AmunCore 41.5
- 8 IBM 39.4
- 9 KORE Wireless 38.6
- 10 Datadog 38.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-management"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/api-management"
curl "https://apis.io/api/v1/cohorts/tag/api-management/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.