CLEAR website screenshot

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 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 documentation, API reference, getting-started guide, support, engineering blog, authentication, sandbox, and 23 more developer resources.

🌐 Visit website 📡 Source on GitHub
56.7/100 developing ▬ flat Agent 78/100 agent native Full breakdown ↓
scored 2026-07-27 · rubric v0.5
AccessSelf serve
1 APIs 1 MCP Servers
CompanyIdentityIdentity VerificationAuthenticationKYCBiometricsOAuthOpenID ConnectHealthcareFinancial Services

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 56.7/100 · developing
Contract Quality 14.6 / 25
Developer Ergonomics 14.8 / 20
Commercial Clarity 6.8 / 20
Operational Transparency 5.5 / 13
Governance 0.0 / 12
Discoverability 9.3 / 10
Agent readiness — 78/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
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 5 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 3 / 3
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/clear: 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 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.

Arazzo Workflows 2

Multi-step API workflows described with the Arazzo specification.

_Index

ARAZZO

CLEAR verify an identity

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

ARAZZO

MCP Servers 1

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

clear-mcp.yml

MCP SERVER

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

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

6 operations · 3 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal
DeveloperPortal
 GettingStarted
GettingStarted
 Login
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
 MCPServer
MCPServer
 AgentSkill
AgentSkill
 AgenticAccess
AgenticAccess
 LLMsTxt
LLMsTxt

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Lifecycle
Lifecycle
 Webhooks
Webhooks
 Conformance
Conformance
 ErrorCatalog
ErrorCatalog
 Components
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 2

The organization behind the API

Blog
Blog
 Website
Website

Source (apis.yml)

apis.yml Raw ↑ 
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
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.20'
created: '2026-07-17'
modified: '2026-07-18'
image: https://static-verified.clearme.com/CLEAR1_Logo_Horizontal_2Color_RGB.png
tags:
- Company
- Identity
- Identity Verification
- Authentication
- KYC
- Biometrics
- OAuth
- OpenID Connect
- Healthcare
- 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:
- 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: MCPServer
  url: mcp/clear-mcp.yml
- 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