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 is listed with 6 APIs on the APIs.io network, including applications API, core API, document passback API, and 3 more. Tagged areas include Company, Identity, Identity Verification, Authentication, and OpenID Connect.

The ID.me catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 1 Spectral governance ruleset.

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

🌐 Visit website 📡 Profile data on GitHub

48.7/100 developing ▬ flat Agent 37/100 agent ready Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-01 · rubric v0.26.0 · Show this score on your site →

AccessSelf serve

6 APIs 1 MCP Servers 2 Agent Skills

Company Identity Identity Verification Authentication OpenID Connect OAuth SAML SSO Digital Identity KYC Fraud Prevention Government Identity Federation

Kin Score

Kin Score How this is scored →
scored 2026-11-01 · rubric v0.26.0

Composite quality — 48.7/100 · developing

Contract Quality 6.3 / 19

Developer Ergonomics 11.0 / 15

Access Clarity 4.3 / 15

Operational Transparency 3.6 / 10

Contract Governance 3.2 / 9

Discoverability 6.0 / 8

Regulatory Posture 5.6 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 37/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 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 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Government & Public Sector 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/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/idme/"><img src="https://apis.io/badge/idme/card.svg" alt="ID.me on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too

6 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 33.5 — up to +16.6 composite points
Access Clarity scores 28.9 — up to +14.2 composite points
Operational Transparency scores 36.8 — up to +8.2 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/idme/apis.yml: open an issue on github.com/api-evangelist/idme to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
RegTech, AML/KYC and Money Transmission	mixed	53.8	-	-
Government Cloud (FedRAMP, GovRAMP, G-Cloud)	mixed	53.8	-	-
Biometrics Testing (biometric recognition vendors, identity verification depth)	mixed	53.8	-	-
TX-RAMP Certified Cloud Products (Texas DIR)	mixed	53.8	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

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.

Model Context Protocol (MCP)

measured — observed by APIs.io (documented)

APIs 6

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...

ID.me applications API

ID.me applications API as documented publicly: 10 operations. Contract generated from the documentation by API Evangelist (2026-10-20); not the provider's own document.

ID.me core API

ID.me core API as documented publicly: 1 operations. Contract generated from the documentation by API Evangelist (2026-10-20); not the provider's own document.

ID.me document passback API

ID.me document passback API as documented publicly: 3 operations. Contract generated from the documentation by API Evangelist (2026-10-20); not the provider's own document.

ID.me services API

ID.me services API as documented publicly: 14 operations. Contract generated from the documentation by API Evangelist (2026-10-20); not the provider's own document.

MCP Servers 1

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

ID.me Developer Docs

Official hosted MCP server for the ID.me developer documentation, advertised in docs.id.me/llms.txt for AI client integration (Claude Code, Cursor, etc.). Surfaces the ID.me int...

MCP SERVER

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

idme-document-verification

AGENT SKILL

idme-telecom-phone-verification

AGENT SKILL

Event Specifications 1

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

Idme Services Webhooks

ASYNCAPI

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Idme Context

36 classes · 54 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

ID.me API Rules

12 rules · 9 errors 2 warnings 1 info

SPECTRAL

SOC 2, ISO 27001, FedRAMP, GDPR, FIPS 140

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

DeveloperPortal

GettingStarted

SignUp

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

AgentSkill

LLMsTxt

WellKnown

MCPServer

Design & Contract 10

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

DataModel

ErrorCatalog

Lifecycle

Conventions

Conformance

Components

Webhooks

Scroll for all 10

Build 4

SDKs, sample code, and the tooling you integrate with

IntegrationEdges

IntegrationEdges

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 8

Authentication, authorization, and security posture

Security

TrustCenter

SecurityTxt

Authentication

OAuthScopes

Compliance

DomainSecurity

VulnerabilityDisclosure

VulnerabilityDisclosure

Scroll for all 8

Operate 2

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

Company 3

The organization behind the API

Blog

Blog

BlogRSS

BlogRSS

Website

Website

Other 3

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

OpenIDConnect

OpenIDConnect

Source (apis.yml)

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
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
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.23'
created: '2026-07-17'
modified: '2026-10-06'
tags:
- Company
- Identity
- Identity Verification
- Authentication
- OpenID Connect
- OAuth
- SAML
- SSO
- Digital Identity
- KYC
- Fraud Prevention
- Government
- Identity Federation
tags_raw:
- Company
- Identity
- Identity Verification
- Authentication
- OpenID Connect
- OAuth 2.0
- SAML
- Single Sign-On
- Digital Identity
- KYC
- Fraud Prevention
- Government
- Identity Federation
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: AgentSkill
  url: skills/_index.yml
- type: Spectral
  url: rules/idme-rules.yml
- type: JSONLD
  url: json-ld/idme-context.jsonld
- type: Vocabulary
  url: vocabulary/idme-vocabulary.yml
- type: DataModel
  url: data-model/idme-data-model.yml
- type: Security
  url: security/idme-vulnerability-disclosure.yml
- type: Hosts
  url: hosts/idme-hosts.yml
- type: IntegrationEdges
  url: integrations/idme-integration-edges.yml
- type: Vendors
  url: vendors/idme-vendors.yml
- type: TrustCenter
  url: security/idme-trust-center.yml
- url: https://network.id.me/insights-home/
  type: Blog
- url: https://network.id.me/feed/
  type: BlogRSS
- 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
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
  - Authentication
  - Identity Verification
  tags_raw:
  - 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
  aid: idme:id-me-openid-connect-oauth-2-0-api
- 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
  - Telecommunications
  - KYC
  tags_raw:
  - 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
  aid: idme:id-me-services-api
- aid: idme:applications-api
  name: ID.me applications API
  description: 'ID.me applications API as documented publicly: 10 operations. Contract generated from the documentation by
    API Evangelist (2026-10-20); not the provider''s own document.'
  humanURL: https://docs.id.me/apis/applications-api
  baseURL: https://services.idmelabs.com
  properties:
  - type: OpenAPI
    url: openapi/_ae-authored/idme-applications-openapi-generated.yml
    x-provenance: generated
  - type: JSONSchema
    url: json-schema/idme-post-v1-organizations-organizationuuid-applications-request-schema.json
  - type: JSONSchema
    url: json-schema/idme-get-v1-domains-domain-response-schema.json
  - type: JSONSchema
    url: json-schema/idme-patch-v1-organizations-uuid-request-schema.json
  - type: JSONSchema
    url: json-schema/idme-post-v1-domains-response-schema.json
  - type: JSONSchema
    url: json-schema/idme-patch-v1-organizations-uuid-response-schema.json
  - type: JSONSchema
    url: json-schema/idme-get-v1-sectors-id-structures-response-schema.json
- aid: idme:core-api
  name: ID.me core API
  description: 'ID.me core API as documented publicly: 1 operations. Contract generated from the documentation by API Evangelist
    (2026-10-20); not the provider''s own document.'
  humanURL: https://docs.id.me/apis/check-credentials-api
  baseURL: https://api.id.me
  properties:
  - type: OpenAPI
    url: openapi/_ae-authored/idme-core-openapi-generated.yml
    x-provenance: generated
  - type: JSONSchema
    url: json-schema/idme-post-api-auth-v1-credentials-uuid-check-response-schema.json
- aid: idme:document-passback-api
  name: ID.me document passback API
  description: 'ID.me document passback API as documented publicly: 3 operations. Contract generated from the documentation
    by API Evangelist (2026-10-20); not the provider''s own document.'
  humanURL: https://docs.id.me/apis/document-passback-api
  baseURL: https://api.id.me
  properties:
  - type: OpenAPI
    url: openapi/_ae-authored/idme-document-passback-openapi-generated.yml
    x-provenance: generated
  - type: JSONSchema
    url: json-schema/idme-get-api-public-v3-attributes-json-response-schema.json
  - type: JSONSchema
    url: json-schema/idme-post-api-public-v3-documents-refresh-documenttoken-response-schema.json
  - type: JSONSchema
    url: json-schema/idme-post-api-public-v3-documents-documenttoken-response-schema.json
- aid: idme:services-api
  name: ID.me services API
  description: 'ID.me services API as documented publicly: 14 operations. Contract generated from the documentation by API
    Evangelist (2026-10-20); not the provider''s own document.'
  humanURL: https://docs.id.me/apis/services-api
  baseURL: https://services.idmelabs.com
  properties:
  - type: OpenAPI
    url: openapi/_ae-authored/idme-services-openapi-generated.yml
    x-provenance: generated
  - type: JSONSchema
    url: json-schema/idme-post-api-v2-telecom-identity-request-schema.json
  - type: JSONSchema
    url: json-schema/idme-post-api-v2-telecom-possession-sms-send-request-schema.json
  - type: JSONSchema
    url: json-schema/idme-post-api-v2-telecom-possession-sms-confirm-request-schema.json
  - type: JSONSchema
    url: json-schema/idme-get-api-v2-product-transactionid-response-schema.json
  - type: JSONSchema
    url: json-schema/idme-get-api-v2-document-passcard-verify-response-schema.json
  - type: JSONSchema
    url: json-schema/idme-get-api-v2-document-passport-verify-response-schema.json
x-enrichment:
  date: '2026-10-20'
  status: enriched
  artifacts_added: 12
  pass: local-v5
x-coverage:
  state: unreadable
  reason: no-machine-readable-spec
  method: derived
  generated: '2026-10-20'
  generator: derive-coverage.py (pre-flight evidence)
  detail: the company publishes developer documentation but serves no machine-readable contract from it
  evidence:
  - url: https://docs.id.me/mcp
    status: null
  - url: https://www.id.me
    status: 200

ID.me API — frequently asked questions

Does ID.me have an API?

Yes. APIs.io lists 6 APIs from ID.me, including ID.me OpenID Connect & OAuth 2.0 API, ID.me Services API and ID.me applications API, and 3 more.

Is there an OpenAPI specification for the ID.me API?

Yes. APIs.io indexes 4 OpenAPI specifications for ID.me, each linked for download from this page.

How do I authenticate with the ID.me API?

ID.me documents its authentication (oauth2/openIdConnect · 3 schemes). The details are profiled on APIs.io as Idme Authentication.

Does ID.me have an MCP server?

Yes. APIs.io lists 1 MCP server for ID.me: Official hosted MCP server for the ID.me developer documentation, advertised in docs.id.me/llms.txt for AI client integration (Claude Code, Cursor, etc.). Surfaces the ID.me integration docs — OIDC/OA

Is the ID.me API ready for AI agents?

ID.me has a Kin Score of 48.7 out of 100 (developing) and an Agent Readiness score of 36.8 (agent-ready), scored by API Evangelist on 2026-11-01.

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/idme"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/idme/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/idme/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.