OAuth
OAuth2OAuth 2.0OAuth
Providers using this tag (243)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 15 Complete, well-documented, and agent-ready
Strong 40 Solid coverage with minor gaps
Developing 68 Usable, with meaningful gaps to close
Thin 72 Limited public surface area
Emerging 39 Early or largely undocumented
Minimal 9 Almost no public developer surface
APIs with this tag (928)
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 82 Complete, well-documented, and agent-ready
Strong 141 Solid coverage with minor gaps
Developing 267 Usable, with meaningful gaps to close
Thin 269 Limited public surface area
Emerging 155 Early or largely undocumented
Minimal 14 Almost no public developer surface
Companies reaching this through an API (766)
These companies publish an API, specification or operation carrying “OAuth” 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 766 companies ↓
Score breakdown
Where this tag sits
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 237 providers in the APIs.io catalog tagged OAuth, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Developer Ergonomics | 46.8 | 24.5 | +22.3 | 237 |
| Contract Quality | 33.3 | 18.6 | +14.7 | 237 |
| Operational Transparency | 26.7 | 13.2 | +13.5 | 237 |
| Access Clarity | 42.2 | 30 | +12.2 | 237 |
| Discoverability | 70 | 59.1 | +10.9 | 237 |
| Contract Governance | 18.4 | 9.7 | +8.7 | 237 |
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% | 18% | +6 |
| MCP server (first-party) | 22% | 16% | +6 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 66% | 13% | +53 |
| Security | 100% | 99% | +1 |
| Arazzo workflows | 6% | 1% | +5 |
| Governance rules | 58% | 36% | +22 |
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 Kinde 89
- 2 Microsoft Entra ID (formerly Azure AD) 85.1
- 3 Cvent Registration 73.6
- 4 Strivacity 73.5
- 5 Authentik 73.1
- 6 Clerk 73.1
- 7 Hootsuite 72.8
- 8 Cvent 72.6
- 9 AWeber 71.7
- 10 Auth0 71.4
- 1 Taskfolk 69.1
- 2 Kann KI das? Sponsoring Agent 68
- 3 1F916 66.4
- 4 Cobot 58.6
- 5 Lacuna 58.1
- 6 Microsoft Entra ID (formerly Azure AD) 57.9
- 7 Cvent Hospitality Cloud 57.2
- 8 Hostfully 56.3
- 9 Flume Health 53.2
- 10 Photon 52.6
Coverage caveat. 171 of 237 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.
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.