Didit
Didit is a developer-first identity verification and fraud-prevention platform that exposes one unified API for KYC (ID verification, passive/active liveness, face match and search, age estimation, proof of address, NFC), KYB business verification (registry, UBO/ownership, officers, entity AML), AML sanctions/PEP screening, transaction monitoring (KYT), crypto wallet screening, and FATF/EU Travel Rule. It spans 220+ countries, 14,000+ document types and 50+ languages with sub-two-second inference, pay-per-call pricing from $0.30 and a 500-verification monthly free tier. The v3 REST API authenticates with an x-api-key header, ships Web/iOS/Android/React Native/Flutter SDKs, HMAC-signed webhooks, a live hosted MCP server, and Agent Skills. Backed by Y Combinator and Robinhood Ventures.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Didit the way a machine reads it — 23 machine-readable artifacts across 17 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Didit scores 58.4/100 (developing), with a separate agent-readiness read of 75/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Didit
Each block below is one kind of artifact we hold for Didit. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 17
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Didit Billing API
The Billing API from Didit — 2 operation(s) for billing.
Didit Businesses API
The Businesses API from Didit — 5 operation(s) for businesses.
Didit Case Blueprints API
The Case Blueprints API from Didit — 4 operation(s) for case blueprints.
Didit Cases API
The Cases API from Didit — 24 operation(s) for cases.
Didit Customization API
The Customization API from Didit — 1 operation(s) for customization.
Didit Questionnaires API
The Questionnaires API from Didit — 2 operation(s) for questionnaires.
Didit Regulatory Reports API
The Regulatory Reports API from Didit — 6 operation(s) for regulatory reports.
Didit Report Templates API
The Report Templates API from Didit — 2 operation(s) for report templates.
Didit Session API
The Session API from Didit — 1 operation(s) for session.
Didit Sessions API
The Sessions API from Didit — 20 operation(s) for sessions.
Didit Standalone APIs API
The Standalone APIs API from Didit — 14 operation(s) for standalone apis.
Didit System API
The System API from Didit — 1 operation(s) for system.
Didit Transactions API
The Transactions API from Didit — 6 operation(s) for transactions.
Didit Travel Rule API
The Travel Rule API from Didit — 11 operation(s) for travel rule.
Didit Users API
The Users API from Didit — 6 operation(s) for users.
Didit Webhook API
The Webhook API from Didit — 2 operation(s) for webhook.
Didit Workflows API
The Workflows API from Didit — 2 operation(s) for workflows.
Scroll within the panel for all 17 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
didit-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Didit Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Didit — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/didit · machine-readable index on apis.io