ID.me

ID.me is a digital identity network that provides NIST 800-63-3 IAL2/AAL2 identity verification, single sign-on, and group affiliation (community) verification for government agencies, healthcare, and commercial partners. For developers, ID.me exposes an OpenID Connect and OAuth 2.0 identity provider (authorization code flow with PKCE, plus SAML 2.0 federation), a REST Services API for telecom and document verification, an Applications API, a Document Passback API, and a Shared Signals Framework (SSF) event stream for fraud and verification signals. Native iOS and Android SDKs, a button widget, conversion tracking, and multi-language sample code round out the developer surface, letting relying parties add strong identity proofing and attribute exchange to any application or IAM platform (Okta, Keycloak, Entra, PingOne, AWS Cognito).

ID.me publishes 2 APIs on the APIs.io network. Tagged areas include Company, Identity, Identity Verification, Authentication, and OpenID Connect.

The ID.me catalog on APIs.io includes 1 event-driven AsyncAPI specification.

ID.me’s developer surface includes documentation, API reference, getting-started guide, support, signup flow, authentication, sandbox, and 22 more developer resources.

50.3/100 developing ▬ flat Agent 51/100 agent ready Full breakdown ↓
scored 2026-08-10 · rubric v0.9.1
AccessSelf serve
2 APIs 1 MCP Servers
CompanyIdentityIdentity VerificationAuthenticationOpenID ConnectOAuth 2.0SAMLSingle Sign-OnDigital IdentityKYCFraud PreventionGovernment

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-10 · rubric v0.9.1
Composite quality — 50.3/100 · developing
Contract Quality 12.9 / 25
Developer Ergonomics 14.3 / 20
Commercial Clarity 4.2 / 20
Operational Transparency 5.1 / 13
Governance 1.5 / 12
Discoverability 8.7 / 10
Agent readiness — 51/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 6 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 3 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/idme: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 2

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

ID.me OpenID Connect & OAuth 2.0 API

ID.me's OpenID Connect and OAuth 2.0 identity provider. Supports the authorization code flow (with PKCE), refresh tokens, encrypted ID tokens and userinfo, and returns verified ...

ID.me Services API

ID.me's REST Services API for orchestrating identity verification: create and manage verifications, verify phone possession and identity via telecom endpoints, and verify identi...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

idme-mcp.yml

MCP SERVER

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Security Posture 3

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

Idme Authentication

oauth2/openIdConnect · 3 schemes

SECURITY

Idme Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Idme Vulnerability Disclosure

security.txt · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Idme Scopes

11 scopes · authorizationCode

11 scopes

SCOPES

Resources

Get Started 4

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 7

Authentication, authorization, and security posture

Scroll for all 7

Operate 2

Status, limits, changes, and where to get help

Company 1

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: idme
name: ID.me
description: ID.me is a digital identity network that provides NIST 800-63-3 IAL2/AAL2 identity verification, single sign-on,
  and group affiliation (community) verification for government agencies, healthcare, and commercial partners. For developers,
  ID.me exposes an OpenID Connect and OAuth 2.0 identity provider (authorization code flow with PKCE, plus SAML 2.0 federation),
  a REST Services API for telecom and document verification, an Applications API, a Document Passback API, and a Shared Signals
  Framework (SSF) event stream for fraud and verification signals. Native iOS and Android SDKs, a button widget, conversion
  tracking, and multi-language sample code round out the developer surface, letting relying parties add strong identity proofing
  and attribute exchange to any application or IAM platform (Okta, Keycloak, Entra, PingOne, AWS Cognito).
url: https://raw.githubusercontent.com/api-evangelist/idme/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- ribbit-capital
x-tier: enriched
x-tier-reason: portfolio-lead
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://avatars.githubusercontent.com/u/295660?v=4
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Identity
- Identity Verification
- Authentication
- OpenID Connect
- OAuth 2.0
- SAML
- Single Sign-On
- Digital Identity
- KYC
- Fraud Prevention
- Government
apis:
- name: ID.me OpenID Connect & OAuth 2.0 API
  description: ID.me's OpenID Connect and OAuth 2.0 identity provider. Supports the authorization code flow (with PKCE), refresh
    tokens, encrypted ID tokens and userinfo, and returns verified identity attributes and community/group affiliation (military,
    responder, student, teacher, government, employee, etc.) after a user completes identity verification.
  humanURL: https://docs.id.me/guides/oidc/overview
  baseURL: https://api.id.me
  tags:
  - OpenID Connect
  - OAuth 2.0
  - Authentication
  - Identity Verification
  properties:
  - type: Documentation
    url: https://docs.id.me/guides/oidc/overview
  - type: APIReference
    url: https://docs.id.me/guides/o-auth-2-0/integration
  - type: OpenIDConnect
    url: https://api.id.me/oidc/.well-known/openid-configuration
  - type: Authentication
    url: authentication/idme-authentication.yml
  - type: OAuthScopes
    url: scopes/idme-scopes.yml
  - type: ErrorCatalog
    url: errors/idme-problem-types.yml
- name: ID.me Services API
  description: 'ID.me''s REST Services API for orchestrating identity verification: create and manage verifications, verify
    phone possession and identity via telecom endpoints, and verify identity documents (driver''s licenses, passports, passport
    cards). Delivers real-time transaction results via webhooks and a sandbox of pre-configured test personas.'
  humanURL: https://docs.id.me/services-api-overview
  baseURL: https://services.idmelabs.com
  tags:
  - Identity Verification
  - Documents
  - Telecom
  - KYC
  properties:
  - type: Documentation
    url: https://docs.id.me/services-api-overview
  - type: APIReference
    url: https://docs.id.me/services-api/verification
  - type: Webhooks
    url: asyncapi/idme-services-webhooks.yml
  - type: Sandbox
    url: sandbox/idme-sandbox.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.id.me
- type: DeveloperPortal
  url: https://developers.id.me
- type: Documentation
  url: https://docs.id.me
- type: APIReference
  url: https://docs.id.me/services-api-overview
- type: GettingStarted
  url: https://docs.id.me/home
- type: Support
  url: https://docs.id.me/integrations/deploy-and-monitor/help
- type: StatusPage
  url: https://status.id.me
- type: GitHubOrganization
  url: https://github.com/IDme
- type: SignUp
  url: https://developers.id.me
- type: LLMsTxt
  url: llms/idme-llms.txt
- type: WellKnown
  url: well-known/idme-well-known.yml
- type: SecurityTxt
  url: well-known/idme-security.txt
- type: OpenIDConnect
  url: well-known/idme-openid-configuration.json
- type: Authentication
  url: authentication/idme-authentication.yml
- type: OAuthScopes
  url: scopes/idme-scopes.yml
- type: MCPServer
  url: mcp/idme-mcp.yml
- type: ErrorCatalog
  url: errors/idme-problem-types.yml
- type: Lifecycle
  url: lifecycle/idme-lifecycle.yml
- type: Conventions
  url: conventions/idme-conventions.yml
- type: Conformance
  url: conformance/idme-conformance.yml
- type: Compliance
  url: https://docs.id.me/guides/learn-more/digital-wallet/nist-ial-2
- type: Sandbox
  url: sandbox/idme-sandbox.yml
- type: Packages
  url: packages/idme-packages.yml
- type: SDKs
  url: packages/idme-packages.yml
- type: Components
  url: components/idme-components.yml
- type: Webhooks
  url: asyncapi/idme-services-webhooks.yml
- type: DomainSecurity
  url: security/idme-domain-security.yml
- type: VulnerabilityDisclosure
  url: security/idme-vulnerability-disclosure.yml
- type: Security
  url: https://www.id.me/.well-known/security.txt
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence