Enterprise
Providers using this tag (964)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 35 Complete, well-documented, and agent-ready
Strong 70 Solid coverage with minor gaps
Developing 148 Usable, with meaningful gaps to close
Thin 150 Limited public surface area
Emerging 301 Early or largely undocumented
Minimal 252 Almost no public developer surface
Unrated 8 Not yet scored
APIs with this tag (175)
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 16 Complete, well-documented, and agent-ready
Strong 36 Solid coverage with minor gaps
Developing 37 Usable, with meaningful gaps to close
Thin 48 Limited public surface area
Emerging 31 Early or largely undocumented
Minimal 7 Almost no public developer surface
Companies reaching this through an API (107)
These companies publish an API, specification or operation carrying “Enterprise” 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 107 companies ↓
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 770 providers in the APIs.io catalog tagged Enterprise, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Access Clarity | 36.6 | 30 | +6.6 | 770 |
| Developer Ergonomics | 30.5 | 24.5 | +6 | 770 |
| Operational Transparency | 18.6 | 13.2 | +5.4 | 770 |
| Discoverability | 62 | 59.1 | +2.9 | 770 |
| Contract Governance | 11.7 | 9.7 | +2 | 770 |
| Contract Quality | 20.2 | 18.6 | +1.6 | 770 |
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) | 17% | 18% | -1 |
| MCP server (first-party) | 17% | 16% | +1 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 13% | 13% | 0 |
| Security | 99% | 99% | 0 |
| Arazzo workflows | 3% | 1% | +2 |
| Governance rules | 39% | 36% | +3 |
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 88
- 2 Microsoft Azure API Management 78.5
- 3 Optimizely 78.1
- 4 Azure Service Bus 77.2
- 5 Losant 75.7
- 6 Microsoft Azure 75.7
- 7 ThousandEyes 75.4
- 8 Veeva 75.2
- 9 Amazon Q 75.1
- 10 Svix 74.7
- 1 Orq.ai 68.5
- 2 Losant 65.4
- 3 Scope3 64.3
- 4 AthenaHQ 64.1
- 5 Optimizely 62.9
- 6 TextQL 62.2
- 7 Prezent 61.7
- 8 Webex 61.1
- 9 Oracle 59
- 10 Poggio Labs 58.6
Coverage caveat. 605 of 770 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.
Compared on APIs.io
Side by side with another market, using the compare_cohorts tool: facet by facet, with the full tool response.
- vs Open Source Open Source vs Enterprise: governance from the community, clarity from the sales team
- All comparisons →
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.