Single Sign-On
Single Sign OnSingle Sign-OnSingleSignOn
Providers using this tag (51)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 3 Complete, well-documented, and agent-ready
Strong 3 Solid coverage with minor gaps
Developing 11 Usable, with meaningful gaps to close
Thin 19 Limited public surface area
Emerging 12 Early or largely undocumented
Minimal 3 Almost no public developer surface
APIs with this tag (186)
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 3 Complete, well-documented, and agent-ready
Strong 7 Solid coverage with minor gaps
Developing 61 Usable, with meaningful gaps to close
Thin 92 Limited public surface area
Emerging 23 Early or largely undocumented
Companies reaching this through an API (150)
These companies publish an API, specification or operation carrying “Single Sign-On” 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 150 companies ↓
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 50 providers in the APIs.io catalog tagged Single Sign-On, 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 | 37.3 | 23.4 | +13.9 | 50 |
| Access Clarity | 37.7 | 26.5 | +11.2 | 50 |
| Operational Transparency | 24.5 | 14 | +10.5 | 50 |
| Contract Quality | 29.5 | 19.8 | +9.7 | 50 |
| Contract Governance | 14.2 | 6.4 | +7.8 | 50 |
| Discoverability | 67.7 | 61.2 | +6.5 | 50 |
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) | 16% | 10% | +6 |
| MCP server (first-party) | 12% | 13% | -1 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 36% | 11% | +25 |
| Security | 98% | 97% | +1 |
| Arazzo workflows | 4% | 2% | +2 |
| Governance rules | 22% | 14% | +8 |
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 86
- 2 Microsoft Entra ID (formerly Azure AD) 77.9
- 3 Authentik 69.1
- 4 Okta 62.1
- 5 Microsoft Azure Active Directory 57.3
- 6 Namely 56.9
- 7 Amazon IAM Identity Center 52.6
- 8 ID.me 50.3
- 9 Clever 49.7
- 10 Cirrus Identity 49.5
- 1 Microsoft Entra ID (formerly Azure AD) 52
- 2 Kinde 48.5
- 3 PlanSource 45.1
- 4 ID.me 34.4
- 5 Microsoft Azure Active Directory 32.4
- 6 FusionAuth 31.4
- 7 Okta 30.8
- 8 Authentik 30.4
- 9 Cirrus Identity 30.2
- 10 SSO 28.1
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.