Prove que é um humano de verdade. Não um deepfake. Não uma LLM.
Bloqueie agentes de IA, rostos gerados, deepfakes e contas duplicadas de superfícies exclusivas para humanos. Liveness passiva certificada iBeta Nível 1 PAD mais deduplicação 1:N gratuita. $0.10 por verificação, 500 gratuitas todo mês.
Confiado por mais de 2.000 organizações em todo o mundo.
Bloqueie agentes · Pare deepfakes · Deduplique Sybil
Prove que o usuário é humano. Prove que ele se cadastrou apenas uma vez.
A Prova de Vida Passiva rejeita todas as categorias de Detecção de Ataque de Apresentação (PAD),
impressão, tela, máscara, rosto gerado por IA. A Busca Facial 1:N então detecta a mesma
pessoa tentando se registrar duas vezes. Veredito em menos de 2 segundos. $0.10 por verificação.
500 verificações gratuitas todo mês, para sempre.
Como funciona
Do cadastro ao usuário verificado em quatro passos.
Passo 01
Crie o fluxo de trabalho
Escolha as verificações que você quer, ID, prova de vida, correspondência facial, sanções, endereço, idade, telefone, e-mail, perguntas personalizadas. Arraste-as para um fluxo no painel, ou publique o mesmo fluxo na nossa API. Crie ramificações com condições, faça testes A/B, sem precisar de código.
Passo 02
Integre
Incorpore nativamente com nossos SDKs para Web, iOS, Android, React Native ou Flutter. Redirecione para uma página hospedada. Ou simplesmente envie um link ao seu usuário, por e-mail, SMS, WhatsApp, onde quiser. Escolha o que melhor se adapta à sua stack.
Passo 03
O usuário passa pelo fluxo
A Didit hospeda a câmera, as dicas de iluminação, a transição para o celular e a acessibilidade. Enquanto o usuário está no fluxo, pontuamos mais de 200 sinais de fraude em tempo real e verificamos cada campo contra fontes de dados autorizadas. Resultado em menos de dois segundos.
Passo 04
Você recebe os resultados
Webhooks assinados em tempo real mantêm seu banco de dados sincronizado no momento em que um usuário é aprovado, recusado ou enviado para revisão. Consulte a API sob demanda. Ou abra o console para inspecionar cada sessão, cada sinal e gerenciar casos do seu jeito.
Bloqueie todo agente · Emita uma credencial que um humano pode carregar
Seis capacidades. Um Proof of Human assinado.
Um fluxo de trabalho, um veredito, uma credencial. Ative cada módulo por superfície. Sem níveis de upsell, sem SKUs adicionais, sem APIs separadas.
Certificado independentemente no iBeta Presentation Attack Detection (PAD) Nível 1, o padrão citado pelo National Institute of Standards and Technology (NIST) dos Estados Unidos. Bloqueia todas as categorias ISO/IEC 30107-3: fotos impressas, replays de tela, máscaras de papel, silicone e látex, ataques de morphing, deepfakes gerados por IA. Retestado anualmente.
Inferência de ponta em menos de dois segundos em Android de entrada. O mesmo modelo que derrota fotos impressas rejeita rostos de Redes Generativas Adversariais (GAN), retratos de modelos de difusão e vídeo deepfake em tempo real. Sem download de modelo, sem experiência degradada em hardware barato.
Edge inference sub-2-seconds on entry-level Android.
03 · Busca Facial 1:N, grátis
As mesmas superfícies faciais. O mesmo humano detectado.
Todo Proof of Human aprovado adiciona um modelo facial ao seu índice de conta privada. A próxima tentativa da mesma pessoa aparece no topo com uma pontuação de correspondência. Ajuste o limite de recusa automática por fluxo de trabalho; encaminhe correspondências limítrofes para revisão. Grátis em todos os planos.
Vincule uma Credencial Reutilizável a cada usuário aprovado. A próxima superfície alimentada pela Didit que precisar da mesma validação consome a credencial a custo zero. O humano detém a prova; você verifica a assinatura. O efeito de rede se multiplica em cada cliente que utiliza Credenciais Reutilizáveis.
Onde quer que um humano seja a unidade de confiança.
Cadastro social, votação online, concursos, pesquisas, registro de vendedores em marketplaces, onboarding de trabalhadores autônomos, selos de confiança em apps de namoro, cadastro em exchanges, jogos de azar online. Onde quer que agentes de IA ou duplicatas corroam o valor de ser humano, o Proof of Human é a barreira.
Contests + surveysNo bot brigading the leaderboard
Dating + marketplacesReal seller, real buyer
Block agents at the door.$0.10 / check
06 · Três métodos, um preço
Passivo $0.10. Ativo 3D $0.15. Face Search grátis.
Passivo (um frame, zero ação do usuário) para cadastro de baixa fricção. O Flash 3D Ativo captura profundidade a partir de uma curta sequência de flash. O 3D Ativo Ação + Flash adiciona um desafio de movimento para as superfícies de maior sensibilidade. A Busca Facial 1:N é gratuita e sempre ativa. 500 verificações gratuitas todo mês, para sempre.
Use a sessão hospedada quando a Didit lidar com a captura (necessário para 3D Ativo), ou chame os endpoints de prova de vida passiva e busca facial autônomos quando você já tiver a selfie.
200OKstatus Aprovado · Em Revisão · Recusado · Não Finalizado
Primeiro, verifique a X-Signature-V2 no webhook assinado.docs →
Integração pronta para agentes
Lance o Proof of Human com um único prompt.
Cole no Claude Code, Cursor, Codex, Devin, Aider ou Replit Agent. Preencha sua stack. O agente provisiona o Didit, constrói o fluxo de trabalho, conecta o webhook e implementa o gate em cinco minutos.
didit-integration-prompt.md
You are integrating Didit's Proof of Human gate into <my_stack>. Block AI agents, deepfakes, masks, and duplicate accounts from human-only surfaces — signup, voting, contests, marketplaces, dating. Two endpoints, one verdict.
1. Prove a real human is present (Liveness). ONE call to the Sessions API runs a Presentation Attack Detection (PAD)-certified passive selfie and returns a verdict in sub-2-seconds.
2. Prove the human is unique (Face Search 1:N). Same Sessions API workflow runs Face Search 1:N against your account's private face index.
Pricing (public):
- Passive Liveness: $0.10 per check
- Active 3D Liveness: $0.15 per check (motion challenge — use for high-sensitivity flows)
- Face Search 1:N: free, included
- First 500 verifications free every month, forever
PRE-REQUISITES
- Production API key from https://business.didit.me (sandbox key in 60s, no card).
- Webhook endpoint with Hash-based Message Authentication Code (HMAC) SHA-256 verification using the X-Signature-V2 header.
- A workflow_id from the Workflow Builder that contains the LIVENESS feature, and (recommended) FACE_MATCH and IP_ANALYSIS so Sybil dedupe + agent / bot signals come in on the same verdict.
STEP 1 — Build the Proof of Human workflow once
POST https://verification.didit.me/v3/workflows/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body:
{
"workflow_label": "proof_of_human",
"features": [
{ "feature": "LIVENESS", "config": { "method": "PASSIVE" } },
{ "feature": "FACE_MATCH" },
{ "feature": "IP_ANALYSIS" }
],
"face_liveness_score_decline_threshold": 30
}
Notes:
- LIVENESS, FACE_MATCH, IP_ANALYSIS are exact, case-sensitive feature names.
- method enum: PASSIVE (one frame) · FLASHING (3D flash) · ACTIVE_3D (action + flash). Use ACTIVE_3D for the highest-sensitivity surfaces (large-value account creation, voting, contest finals).
STEP 2 — Open a Proof of Human session per user
POST https://verification.didit.me/v3/session/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body:
{
"workflow_id": "<the workflow_id from step 1>",
"vendor_data": "<your internal user id>",
"callback": "https://<your-app>/proof-of-human/callback",
"metadata": {
"surface": "<signup | vote | contest | marketplace | dating>"
}
}
Response: 201 Created with the hosted session_url. Redirect the user. The hosted UI opens the front camera, captures one passive frame (or a short motion challenge for ACTIVE_3D), runs Liveness + Face Search 1:N, returns the verdict in sub-2-seconds.
STEP 3 — Read the signed verdict on the webhook
Body (excerpted for a clean human):
{
"session_id": "<uuid>",
"vendor_data": "<your user id>",
"status": "Approved",
"liveness": {
"status": "Approved",
"method": "PASSIVE",
"score": 96,
"warnings": []
},
"face": {
"status": "Approved",
"similarity_score": null,
"matches": []
},
"ip_analysis": { "status": "Approved" }
}
Body (excerpted for a duplicate):
{
"status": "In Review",
"liveness": { "status": "Approved", "score": 94 },
"face": {
"status": "In Review",
"matches": [
{ "vendor_data": "user_8124", "similarity_score": 0.97 }
],
"warnings": [{ "code": "POSSIBLE_DUPLICATED_FACE" }]
}
}
Verify X-Signature-V2 BEFORE trusting the body — HMAC SHA-256 of the raw bytes with your webhook secret.
Session status enum (exact case): Approved | Declined | In Review | Resubmitted | Expired | Not Finished | Kyc Expired | Abandoned.
Liveness warning catalog:
- LIVENESS_FACE_ATTACK PAD attack suspected (print / replay / mask / GAN)
- LOW_LIVENESS_SCORE score below threshold
- NO_FACE_DETECTED no face in the capture
- AGE_NOT_DETECTED capture quality too low for age signal
- POSSIBLE_DUPLICATED_FACE same face previously verified on your account
STEP 4 — Branch your surface on the final verdict
Approved → grant access to the human-only surface.
Declined → block; log the rejected agent / spoof attempt.
In Review → hold; show a review-pending banner, route to ops queue.
Not Finished → user abandoned; safe to re-prompt.
STEP 5 — Alternate path (server-to-server, when you have the selfie)
POST https://verification.didit.me/v3/passive-liveness/
Headers:
x-api-key: <your api key>
Body (multipart/form-data):
image <single front-camera selfie>
Then dedupe:
POST https://verification.didit.me/v3/face-search/
Body (multipart/form-data):
image <same selfie>
vendor_data <your user id>
Use the standalone path for native onboarding apps that capture the selfie locally. Active 3D liveness REQUIRES the hosted session — it needs the motion challenge to run.
CONSTRAINTS
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- Feature enum is UPPERCASE: LIVENESS, FACE_MATCH, IP_ANALYSIS, ID_VERIFICATION, AML, AGE_ESTIMATION.
- Method enum is UPPERCASE: PASSIVE, FLASHING, ACTIVE_3D.
- Auth header is x-api-key (lowercase, hyphenated).
- Webhook signature header is X-Signature-V2 (NOT X-Signature).
- Status casing matches exactly: Approved, Declined, In Review, Expired, Not Finished, Resubmitted, Kyc Expired, Abandoned.
- 200+ fraud signals are evaluated on every session at no extra cost.
PRO TIP
- Bind a Reusable Credential to each approved user. The next Didit-powered surface that needs the same gate consumes the credential at zero cost — the Proof of Human "compounds" across the network.
Read the docs:
- https://docs.didit.me/core-technology/liveness/overview
- https://docs.didit.me/core-technology/face-search/overview
- https://docs.didit.me/sessions-api/create-session
- https://docs.didit.me/integration/webhooks
Start free at https://business.didit.me — sandbox key in 60 seconds, 500 verifications free every month, no credit card.
Precisa de mais contexto? Consulte a documentação completa do módulo.docs.didit.me →
Conformidade por design
Abra um novo país com um clique. Nós fazemos o trabalho pesado.
Nós abrimos as subsidiárias locais, garantimos as licenças, realizamos os testes de penetração, obtemos as certificações e nos alinhamos a cada nova regulamentação. Para lançar verificações em um novo país, basta ativar uma chave. Mais de 220 países ativos, auditados e testados trimestralmente, o único provedor de identidade que um governo de um estado membro da UE formalmente considerou mais seguro do que a verificação presencial.
Detecção de Ataque de Apresentação certificada independentemente em cada selfie passiva.
<0%
Usuários reais rejeitados no ponto de teste certificado.
<0s
Detecção de vivacidade (liveness) de ponta a ponta e inferência de busca facial em Android de entrada.
$0.00
Por verificação de vivacidade passiva. A busca facial 1:N é gratuita.
Três planos, uma tabela de preços
Comece grátis. Pague pelo uso. Escale para Enterprise.
500 verificações gratuitas todo mês, para sempre. Pague conforme usar para produção. Contratos personalizados, residência de dados e SLAs (Service Level Agreements) no plano Enterprise.
Grátis
Grátis
$0 / mês. Não precisa de cartão de crédito.
Pacote KYC grátis (Verificação de ID + Prova de Vida Passiva + Comparação Facial + Análise de Dispositivo e IP), 500 / mês, todo mês
Comece grátis → pague apenas quando uma verificação for executada → desbloqueie o Enterprise para um contrato personalizado, SLA ou residência de dados.
FAQ
Perguntas frequentes
What is Didit?
Didit is infrastructure for identity and fraud, the platform we wished existed when we were building products ourselves: open, flexible, and developer-friendly, so it works as a real part of your stack instead of a black box you integrate around.
One API covers verifying people (KYC, know your customer), verifying businesses (KYB, know your business), screening crypto wallets (KYT, know your transaction), and monitoring transactions in real time, on a stack built to be:
Fast, sub-2-second p99 on every session
Reliable, in production with 1,500+ companies across 220+ countries
Secure, SOC 2 Type 1, ISO 27001, GDPR-native, and formally attested by Spain's financial regulator as safer than verifying someone in person
The footprint underneath: 14,000+ document types in 48+ languages, 1,000+ data sources, and 200+ fraud signals on every session. The Didit infrastructure dynamically learns from every session and gets better every day.
What does "proof of human" mean in practice?
A short challenge that proves three things at once:
A real person is on the other side, captured in real time, not a stored photo, replay, or video file.
The person is not a printout, screen, silicone mask, or AI-generated face.
The person is unique, they haven't already passed the same gate on your platform.
The first two are called liveness and Presentation Attack Detection (PAD). The third is 1:N face deduplication. Together they're what most platforms now mean when they say "proof of human".
Why does this matter in 2026?
Two reasons.
Generative AI shipped. A teenager with a free image model can mint a photorealistic face in seconds. Headless agents can spin up thousands of accounts overnight. Old defences (a CAPTCHA, a phone number, an email) don't bind to a real person anymore.
Platforms are accountable for what humans on them say. The EU Digital Services Act, the UK Online Safety Act, and several state-level rules treat platforms as responsible for harms caused by inauthentic behaviour. "We didn't know" stopped being a defence in 2024.
How fast is the verification for my end user?
The full flow normally takes under 30 seconds end-to-end, pick up the ID, snap the document, snap the selfie, done. That is the fastest in the market. Legacy KYC providers usually take more than 90 seconds for the same flow.
On the back end, Didit returns the result in under two seconds at p99, measured from the moment the user finishes the selfie to the moment your webhook fires. Mobile capture is tuned for slow phones and slow networks: progressive image compression, lazy software development kit load, and a one-tap hand-off from desktop to phone via QR code if the user starts on web.
How does liveness detect a deepfake or generated face?
The model is trained on real captures vs. every known spoof class, print, screen replay, mask, morph, Generative Adversarial Network (GAN) portrait, diffusion render. Real captures carry tiny artefacts no spoof has: micro-motion of the head, sub-pixel skin texture, reflections that match the device's flash spectrum, depth cues from a single passive frame.
The iBeta Level 1 PAD certification, the bar the US National Institute of Standards and Technology cites, measures exactly this performance, and Didit holds it across every passive-liveness session.
What happens if a user fails, abandons, or expires?
Every session lands on one of seven clear statuses, so your code always knows what to do:
Approved, every check passed. Move the user forward.
Declined, one or more checks failed. You can allow the user to resubmit the specific failed step (for example, re-take the selfie) without re-running the whole flow.
In Review, flagged for compliance review. Open the case in the console, see every signal, decide approve or decline.
In Progress, user is mid-flow.
Not Started, link sent, user has not opened it yet. Send a reminder if it sits too long.
Abandoned, user opened the link but did not finish in time. Re-engage or expire.
Expired, the session link aged out. Create a new session.
A signed webhook fires on every status change, so your database always stays in sync. Abandoned and declined sessions are free.
Where does my customer data live and how is it protected?
Production data is processed and stored in the European Union by default, on Amazon Web Services. Enterprise contracts can request alternative regions for jurisdictions whose regulators require it.
Encryption everywhere. AES-256 at rest across every database, object store, and backup. Transport Layer Security 1.3 in transit on every API call, webhook, and Business Console session. Biometric data is encrypted under a separate Customer Master Key.
Retention is yours to control. Default retention is indefinite (unlimited) unless you configure shorter, between 30 days and 10 years per application, and you can delete any individual session at any time from the dashboard or the API.
Certifications: SOC 2 Type 1 (Type 2 audit in progress), ISO/IEC 27001:2022, iBeta Level 1 PAD, and a public attestation from Spain''s Tesoro / SEPBLAC / CNMV that Didit''s remote identity verification is safer than verifying someone in person. Full report at /security-compliance.
Is Didit compliant for my industry?
Didit ships compliant by default for the regulators that matter to identity infrastructure:
GDPR + UK GDPR, controller / processor split, full Data Processing Agreement published, lead supervisory authority named (Spain''s AEPD).
AMLD6 + EU AML Single Rulebook, 1,300+ sanctions, politically exposed person, and adverse-media lists screened in real time.
eIDAS 2.0, EU Digital Identity Wallet aligned; reusable-identity ready.
MiCA (Markets in Crypto-Assets), ready for crypto on-ramps, exchanges, and custodians.
DORA, Digital Operational Resilience Act, EU financial-services operational resilience.
BIPA, CUBI, Washington HB 1493, CCPA / CPRA, US biometric privacy (Illinois, Texas, Washington) and California consumer privacy.
UK Online Safety Act, age-gating and child-safety obligations.
FATF Travel Rule, originator and beneficiary data on crypto transfers, IVMS-101 interoperable.
Hosted workflow, POST /v3/session/ with the workflow_id you built in the Business Console. We host the capture UI, run Liveness + Face Search 1:N, return a signed verdict to your webhook. Five-minute integration.
Server-to-server, call POST /v3/passive-liveness/ with the selfie you already captured locally, then POST /v3/face-search/ for Sybil dedupe.
Full cURL example, response shape, and the agent-pastable prompt are above. The Model Context Protocol (MCP) server speaks both surfaces to Claude, Cursor, and any other agent.
How do you handle the user's biometric data?
Data minimisation by default. The selfie is processed in memory; the verdict, liveness score, and an irreversible face template are persisted; the raw image is deleted unless retention is explicitly enabled. The face template is a one-way hash, you cannot reconstruct the underlying face from it.
We never sell, share, or train third-party models on a customer's biometric data. The full data-processing terms live at didit.me/terms/business; the privacy notice the end user sees is at didit.me/terms/verification-privacy-notice.
What if a user fails the check?
The session returns one of four outcomes:
Approved, clean human. Issue the Reusable Credential and grant access.
Declined, clear spoof signal (print, screen, mask, generated face). Block.
In Review, high-similarity match in Face Search 1:N or a low liveness score. Hold the surface, route to your ops queue. The Business Console gives the analyst the selfie, the match, and the score.
Not Finished, user abandoned the capture. Safe to re-prompt.
A signed webhook lands at every state change, so you only render against the latest verdict.