CLEAR

CLEAR (clearme.com) is a secure identity company best known for its biometric identity network. For developers, CLEAR1 exposes an identity verification API: you create a verification session, hand the user off to CLEAR's hosted UI to capture a government ID and a selfie/liveness check, then retrieve the verified result and traits. The platform supports OAuth 2.0 / OpenID Connect (with PKCE) for end-user identity tokens, bearer-key auth for the REST API, webhooks for session lifecycle events, a sandbox with synthetic test identities, and native integrations (Okta, Microsoft Entra, Ping, Amazon Connect, DocuSign, Greenhouse) across workforce, healthcare, financial services, and consumer use cases, including IAL2 identity proofing and TEFCA/Carequality access.

CLEAR publishes 1 API contract indexed on the APIs.io network: Verification Sessions API. Tagged areas include Company, Identity, Identity Verification, Authentication, and KYC.

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

CLEAR’s developer surface includes engineering blog, documentation, API reference, getting-started guide, support, authentication, sandbox, and 27 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

46.5/100 developing ▬ flat Agent 33/100 agent ready Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-10-17 · rubric v0.24.0

AccessSelf serve

1 published contract

Company Identity Identity Verification Authentication KYC Biometrics OpenID Connect Healthcare Financial Services

What this lets a business do 1

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

Banking Customer Management

BC-1300

Verification Sessions

POST /verification_sessions

Kin Score

Kin Score How this is scored →
scored 2026-10-17 · rubric v0.24.0

Composite quality — 46.5/100 · developing

Contract Quality 10.2 / 19

Developer Ergonomics 7.1 / 15

Access Clarity 4.1 / 15

Operational Transparency 4.1 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 5.5 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 33/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 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 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

Regulatory Posture applies to this provider. Its tags matched the Health 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/clear: 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 →

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	builds-on	46.4	-	-

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.

OpenID Connect

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

APIs 1

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

CLEAR Verification Sessions API

The Verification Sessions API from CLEAR — 4 operation(s) for verification sessions.

Open Collections 2

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

CLEAR1 Verification Sessions API

OPEN COLLECTION

Arazzo Workflows 1

Multi-step API workflows described with the Arazzo specification.

CLEAR verify an identity

Create a CLEAR verification session, then retrieve its result and verified traits.

ARAZZO

Event Specifications 1

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

CLEAR1 Webhooks

Server-to-server webhook events emitted by CLEAR when a verification session changes. Generated by API Evangelist from the documented CLEAR webhook catalog (contact CLEAR suppor...

ASYNCAPI

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Clear Verification Overlay

3 actions · update · clear-verification-openapi.json

UNRECORDED

Security Posture 3

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

Clear Authentication

http/oauth2/openIdConnect · 2 schemes

SECURITY

Clear Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Clear Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Clear Scopes

3 scopes · authorizationCode

3 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Clear Agentic Access

6 operations · 3 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Login

Sandbox

Sandbox

Documentation 3

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

AsyncAPI

AsyncAPI

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

X-MCPServerCandidate

AgentSkill

AgenticAccess

LLMsTxt

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Lifecycle

Webhooks

Conformance

ErrorCatalog

Components

Access & Security 6

Authentication, authorization, and security posture

Authentication

Authentication

OAuthScopes

OAuthScopes

Security

Security

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

SecurityTxt

SecurityTxt

Operate 3

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

Deprecation

Deprecation

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 4

The organization behind the API

Blog

BlogRSS

Blog

Website

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: clear
name: CLEAR
description: 'CLEAR (clearme.com) is a secure identity company best known for its biometric identity network. For developers,
  CLEAR1 exposes an identity verification API: you create a verification session, hand the user off to CLEAR''s hosted UI
  to capture a government ID and a selfie/liveness check, then retrieve the verified result and traits. The platform supports
  OAuth 2.0 / OpenID Connect (with PKCE) for end-user identity tokens, bearer-key auth for the REST API, webhooks for session
  lifecycle events, a sandbox with synthetic test identities, and native integrations (Okta, Microsoft Entra, Ping, Amazon
  Connect, DocuSign, Greenhouse) across workforce, healthcare, financial services, and consumer use cases, including IAL2
  identity proofing and TEFCA/Carequality access.'
url: https://raw.githubusercontent.com/api-evangelist/clear/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- bond-capital
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - 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
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
image: https://static-verified.clearme.com/CLEAR1_Logo_Horizontal_2Color_RGB.png
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-09-24
tags:
- Company
- Identity
- Identity Verification
- Authentication
- KYC
- Biometrics
- OpenID Connect
- Healthcare
- Financial Services
tags_raw:
- Company
- Identity
- Identity Verification
- Authentication
- KYC
- Biometrics
- OAuth
- OpenID Connect
- Healthcare
- Financial Services
- Financial-Services
apis:
- aid: clear:clear-verification-sessions-api
  name: CLEAR Verification Sessions API
  description: The Verification Sessions API from CLEAR — 4 operation(s) for verification sessions.
  humanURL: https://docs.clearme.com/reference/the-verification-sessions-api
  baseURL: https://verified.clearme.com/v1
  tags:
  - Verification Sessions
  properties:
  - type: OpenAPI
    url: openapi/clear-verification-sessions-api-openapi.yml
  - type: Authentication
    url: authentication/clear-authentication.yml
  - type: OAuthScopes
    url: scopes/clear-scopes.yml
  - type: ErrorCatalog
    url: errors/clear-problem-types.yml
  - type: Conventions
    url: conventions/clear-conventions.yml
  - type: DataModel
    url: data-model/clear-data-model.yml
  - type: Arazzo
    url: arazzo/clear-verify-identity.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- url: https://ir.clearme.com/news-events/press-releases
  type: Blog
- url: https://ir.clearme.com/news-events/press-releases/rss
  type: BlogRSS
- type: CapabilityMap
  url: capabilities/clear-capability-edges.yml
  name: CLEAR Business Capability Map
- type: Overlay
  url: overlays/clear-verification-overlay.yaml
- type: DeveloperPortal
  url: https://docs.clearme.com
- type: Documentation
  url: https://docs.clearme.com/docs/getting-started
- type: APIReference
  url: https://docs.clearme.com/reference/the-verification-sessions-api
- type: GettingStarted
  url: https://docs.clearme.com/docs/standard-integration
- type: Support
  url: https://www.clearme.com/support
- type: Blog
  url: https://www.clearme.com/blog
- type: Login
  url: https://verified.clearme.com/dashboard
- type: TermsOfService
  url: https://www.clearme.com/terms
- type: PrivacyPolicy
  url: https://www.clearme.com/privacy-policy
- type: StatusPage
  url: https://status.clearme.com
- type: Deprecation
  url: lifecycle/clear-lifecycle.yml
- type: Lifecycle
  url: lifecycle/clear-lifecycle.yml
- type: Authentication
  url: authentication/clear-authentication.yml
- type: OAuthScopes
  url: scopes/clear-scopes.yml
- type: Security
  url: https://hackerone.com/clear
- type: VulnerabilityDisclosure
  url: security/clear-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/clear-domain-security.yml
- type: SecurityTxt
  url: well-known/clear-security.txt
- type: WellKnown
  url: well-known/clear-well-known.yml
- type: Webhooks
  url: asyncapi/clear-events-asyncapi.yml
- type: AsyncAPI
  url: asyncapi/clear-events-asyncapi.yml
- type: Sandbox
  url: sandbox/clear-sandbox.yml
- type: Conformance
  url: conformance/clear-conformance.yml
- type: ErrorCatalog
  url: errors/clear-reason-codes.yml
- type: Components
  url: components/clear-components.yml
- type: X-MCPServerCandidate
  url: mcp/clear-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: AgentSkill
  url: skills/_index.yml
- type: AgenticAccess
  url: agentic-access/clear-agentic-access.yml
- type: LLMsTxt
  url: llms/clear-llms.txt
- type: Website
  url: https://clearme.com
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

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

All providers

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

Every operation they expose

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

How their score was established

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