OpenID Connect
OpenID ConnectOpenid Connectopenid-connect
Providers using this tag (138)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Strong 18 Solid coverage with minor gaps
Developing 40 Usable, with meaningful gaps to close
Thin 46 Limited public surface area
Emerging 31 Early or largely undocumented
Minimal 1 Almost no public developer surface
APIs with this tag (108)
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 2 Complete, well-documented, and agent-ready
Strong 14 Solid coverage with minor gaps
Developing 29 Usable, with meaningful gaps to close
Thin 39 Limited public surface area
Emerging 24 Early or largely undocumented
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 138 providers in the APIs.io catalog tagged OpenID Connect, 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 | 38.8 | 17.9 | +20.9 | 138 |
| Discoverability | 76.5 | 60.4 | +16.1 | 138 |
| Contract Quality | 31 | 17.5 | +13.5 | 138 |
| Access Clarity | 35.5 | 22.3 | +13.2 | 138 |
| Operational Transparency | 23.3 | 11.3 | +12 | 138 |
| Contract Governance | 17.1 | 6.4 | +10.7 | 138 |
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) | 36% | 16% | +20 |
| MCP server (first-party) | 12% | 7% | +5 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 72% | 9% | +63 |
| Security | 100% | 88% | +12 |
| Arazzo workflows | 8% | 2% | +6 |
| Governance rules | 20% | 13% | +7 |
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 LINE 71.2
- 2 iOS 67.9
- 3 PropelAuth 65.9
- 4 Nokia Network as Code 65.7
- 5 Nursa 63.8
- 6 Frontegg 63.3
- 7 Kinde 62.9
- 8 Airtm 62.8
- 9 GitHub 62.4
- 10 Slack 62.3
- 1 Liquid Death 51.2
- 2 Airtm 49.8
- 3 Telia Company 48.1
- 4 Amber Electric 47.7
- 5 Reapit 46.6
- 6 GitHub 45.5
- 7 GoFundMe 45.5
- 8 LINE 45.4
- 9 Steadfast Group 44.8
- 10 Dust Identity 44.7
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/openid-connect"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/openid-connect"
curl "https://apis.io/api/v1/cohorts/tag/openid-connect/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.