Identity Federation
Providers using this tag (297)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 9 Complete, well-documented, and agent-ready
Strong 14 Solid coverage with minor gaps
Developing 55 Usable, with meaningful gaps to close
Thin 123 Limited public surface area
Emerging 92 Early or largely undocumented
Minimal 4 Almost no public developer surface
APIs with this tag (243)
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 →
Strong 1 Solid coverage with minor gaps
Developing 38 Usable, with meaningful gaps to close
Thin 106 Limited public surface area
Emerging 97 Early or largely undocumented
Minimal 1 Almost no public developer surface
Score breakdown
Where this tag sits
Related tags
Where this tag comes from
Markets provisional
Kin Score markets whose measured providers carry this tag. Share is the fraction of the market's measured providers that carry it — it describes the market, not this tag.
| Market | Share of the market's providers |
|---|---|
| Identity and Auth | 84% |
| Higher Education and Research | 54% |
| IIIF and Cultural Heritage (GLAM image interoperability, Linked Art) | 53% |
| OpenID Certified Implementations (OIDC, FAPI, OpenID4VC) | 23% |
Cohort brief
Auto-generatedThe 296 providers in the APIs.io catalog tagged Identity Federation, 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 | 36.3 | 18.6 | +17.7 | 296 |
| Developer Ergonomics | 33.8 | 24.5 | +9.3 | 296 |
| Discoverability | 66.5 | 59.1 | +7.4 | 296 |
| Contract Governance | 15.4 | 9.7 | +5.7 | 296 |
| Operational Transparency | 18.2 | 13.2 | +5 | 296 |
| Access Clarity | 28.5 | 30 | -1.5 | 296 |
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) | 7% | 18% | -11 |
| MCP server (first-party) | 6% | 16% | -10 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 34% | 13% | +21 |
| Security | 100% | 99% | +1 |
| Arazzo workflows | 2% | 1% | +1 |
| Governance rules | 69% | 36% | +33 |
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 Entra ID (formerly Azure AD) 85.1
- 2 WSO2 84.3
- 3 Okta 81.8
- 4 Amazon Cognito 74.5
- 5 Authentik 73.1
- 6 Clerk 73.1
- 7 Cvent 72.6
- 8 Auth0 71.4
- 9 Microsoft Entra 70.3
- 10 Gluu 65.7
- 1 WorkOS 58.8
- 2 Microsoft Entra ID (formerly Azure AD) 57.9
- 3 Supabase 48.1
- 4 Okta 47.7
- 5 Cvent 47.4
- 6 PlanSource 46.4
- 7 Clerk 46.1
- 8 Rice University 41.7
- 9 Columbia University 41
- 10 Google Firebase 40.3
Coverage caveat. 206 of 296 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.