OpenID Connect website screenshot

OpenID Connect

OpenID Connect (OIDC) is an identity authentication protocol that is an extension of OAuth 2.0. It enables clients to verify the identity of end-users and obtain basic profile information in a secure, standardized way using JSON Web Tokens (JWT).

OpenID Connect publishes 6 API contracts indexed on the APIs.io network, including OIDC Authentication API, OIDC Discovery API, OIDC JWKS API, and 3 more. Tagged areas include Authentication, Identity, JWT, and OpenID Connect.

OpenID Connect’s developer surface includes documentation, engineering blog, and 5 more developer resources.

🌐 Visit website📡 Profile data on GitHub
13.8/100 emerging ▼ -5.8 Agent 13/100 agent aware Full breakdown ↓
scored 2026-10-17 · rubric v0.24.0
6 published contracts
AuthenticationIdentityJWTOpenID Connect

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Cybersecurity Management
BC-620
AuthenticationUser Info

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-10-17 · rubric v0.24.0
Composite quality — 13.8/100 · emerging
Contract Quality 4.5 / 19
Developer Ergonomics 2.9 / 15
Access Clarity 0.0 / 15
Operational Transparency 0.0 / 10
Contract Governance 0.0 / 9
Discoverability 4.6 / 8
Regulatory Posture 0.9 / 15
Create-or-Update Ergonomics 0.0 / 10
Agent readiness — 13/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 0 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Well-Known Document 0 / 5
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/openid-connect: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenID Connect
tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

APIs 6

Individual APIs this provider publishes, each with its own machine-readable definition.

OIDC Authentication API

Endpoints for authenticating end-users and obtaining authorization grants.

OIDC Discovery API

OpenID Connect Discovery endpoints for provider metadata.

OIDC JWKS API

JSON Web Key Set endpoint for token signature verification.

OIDC Session API

Session management endpoints including logout.

OIDC Token API

Token endpoint for exchanging authorization codes for tokens.

OIDC User Info API

Endpoint for retrieving claims about the authenticated end-user.

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Openid Connect Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Documentation 2

Reference material describing how the API behaves

Documentation
Documentation
 Reference
Reference

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LlmsText
LlmsText

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity
DomainSecurity

Company 2

The organization behind the API

Website
Website
 Blog
Blog

Other 1

Properties that don't map to a standard resource type

CapabilityMap
CapabilityMap

Source (apis.yml)

apis.yml Raw ↑ 
aid: openid-connect
name: OpenID Connect
description: OpenID Connect (OIDC) is an identity authentication protocol that is an extension of OAuth 2.0. It enables clients
  to verify the identity of end-users and obtain basic profile information in a secure, standardized way using JSON Web Tokens
  (JWT).
type: Index
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/openid-connect.png
tags:
- Authentication
- Identity
- JWT
- OpenID Connect
tags_raw:
- Authentication
- Identity
- JWT
- OAuth
- OpenID Connect
url: https://raw.githubusercontent.com/api-evangelist/openid-connect/refs/heads/main/apis.yml
created: '2025-01-01'
modified: '2026-04-28'
specificationVersion: '0.23'
apis:
- aid: openid-connect:oidc-authentication-api
  name: OIDC Authentication API
  description: Endpoints for authenticating end-users and obtaining authorization grants.
  humanURL: https://openid.net/specs/openid-connect-core-1_0.html
  tags:
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/oidc-authentication-api-openapi.yml
  - type: Documentation
    url: https://openid.net/specs/openid-connect-core-1_0.html
- aid: openid-connect:oidc-discovery-api
  name: OIDC Discovery API
  description: OpenID Connect Discovery endpoints for provider metadata.
  humanURL: https://openid.net/specs/openid-connect-core-1_0.html
  tags:
  - Discovery
  properties:
  - type: OpenAPI
    url: openapi/oidc-discovery-api-openapi.yml
  - type: Documentation
    url: https://openid.net/specs/openid-connect-core-1_0.html
- aid: openid-connect:oidc-jwks-api
  name: OIDC JWKS API
  description: JSON Web Key Set endpoint for token signature verification.
  humanURL: https://openid.net/specs/openid-connect-core-1_0.html
  tags:
  - JWKS
  properties:
  - type: OpenAPI
    url: openapi/oidc-jwks-api-openapi.yml
  - type: Documentation
    url: https://openid.net/specs/openid-connect-core-1_0.html
- aid: openid-connect:oidc-session-api
  name: OIDC Session API
  description: Session management endpoints including logout.
  humanURL: https://openid.net/specs/openid-connect-core-1_0.html
  tags:
  - Sessions
  tags_raw:
  - Session
  properties:
  - type: OpenAPI
    url: openapi/oidc-session-api-openapi.yml
  - type: Documentation
    url: https://openid.net/specs/openid-connect-core-1_0.html
- aid: openid-connect:oidc-token-api
  name: OIDC Token API
  description: Token endpoint for exchanging authorization codes for tokens.
  humanURL: https://openid.net/specs/openid-connect-core-1_0.html
  tags:
  - Tokens
  tags_raw:
  - Token
  properties:
  - type: OpenAPI
    url: openapi/oidc-token-api-openapi.yml
  - type: Documentation
    url: https://openid.net/specs/openid-connect-core-1_0.html
- aid: openid-connect:oidc-user-info-api
  name: OIDC User Info API
  description: Endpoint for retrieving claims about the authenticated end-user.
  humanURL: https://openid.net/specs/openid-connect-core-1_0.html
  tags:
  - UserInfo
  tags_raw:
  - User Info
  properties:
  - type: OpenAPI
    url: openapi/oidc-user-info-api-openapi.yml
  - type: Documentation
    url: https://openid.net/specs/openid-connect-core-1_0.html
common:
- type: CapabilityMap
  url: capabilities/openid-connect-capability-edges.yml
  name: OpenID Connect Business Capability Map
- type: DomainSecurity
  url: security/openid-connect-domain-security.yml
- type: Website
  url: https://openid.net/
- type: Documentation
  url: https://openid.net/developers/specs/
- type: Reference
  url: https://openid.net/specs/openid-connect-core-1_0.html
- type: LlmsText
  url: https://openid.net/llms.txt
- url: https://openid.net/feed/
  type: Blog
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider 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 providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • 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.
All 92 tools →

Call it yourself

curl for this page
This provider 
curl "https://apis.io/api/v1/providers/openid-connect"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/openid-connect/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/openid-connect/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.