Kadiria umri wa mtumiaji kutoka kwa selfie, hakuna upakiaji wa kitambulisho, hakuna usumbufu. Chini ya sekunde mbili, usahihi wa ±3.5-mwaka, iBeta-certified liveness kwenye upigaji picha uleule. $0.10 kwa kila ukaguzi, 500 bure/mwezi.
Inaaminika na mashirika 2,000+ duniani kote.
Chini ya sekunde 2 kwenye kifaa
Uchambuzi wa uso kwenye kifaa unatoa makadirio ya umri chini ya sekunde mbili, hakuna picha ya kitambulisho, data ndogo ya kibinafsi. Imejengwa kwenye injini ileile iliyothibitishwa na iBeta Level 1 kwa ugunduzi wa mashambulizi ya uwasilishaji.
Chagua ukaguzi unaotaka, kitambulisho, liveness, kulinganisha uso, vikwazo, anwani, umri, simu, barua pepe, maswali maalum. Ziburute kwenye mtiririko kwenye dashibodi, au tuma mtiririko uleule kwenye API yetu. Panga masharti, fanya majaribio ya A/B, hakuna code inayohitajika.
$ curl -X POST https://verification.didit.me/v3/session/ \
-H "x-api-key: $DIDIT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"workflow_id": "wf_age_adaptive",
"vendor_data": "user-42"
}'{ "session_url": "verify.didit.me/..." }$ curl -X POST https://verification.didit.me/v3/age-estimation/ \
-H "x-api-key: $DIDIT_API_KEY" \
-F "user_image=@selfie.jpg" \
-F "age_estimation_decline_threshold=18"{ "status": "Approved", "age_estimation": 27.33 }# Didit Age Estimation — integrate in 5 minutes
You are integrating Didit's Age Estimation module into <my_stack>. Follow
these steps exactly. Every URL, header, and enum value below is canonical
— do not paraphrase or "improve" them.
## 1. Provision an account
- Sign up: https://business.didit.me (no credit card required).
- Or provision programmatically: POST https://apx.didit.me/auth/v2/programmatic/register/
(returns an API key bound to the workspace + application).
## 2. Two integration paths — pick one
### Path A — Workflow Builder (hosted UI)
Best when you want Didit to handle the camera, framing, low-light
fallback, mobile handoff, and accessibility for you. Required if you want
Adaptive Age Verification (auto-fall-back to ID for borderline cases).
1. Create a workflow that contains the AGE_ESTIMATION feature:
POST https://verification.didit.me/v3/workflows/
Authorization header: x-api-key: <your-api-key>
Body: workflow_label, features array with the single entry
{ feature: "AGE_ESTIMATION" } (UPPERCASE — strict enum)
Optional config:
- age_estimation_decline_threshold (default 18)
- face_liveness_score_decline_threshold (default 30)
- adaptive_id_verification (when true, borderline cases trigger ID
verification fallback governed by per-country age restrictions on
the ID Verification step)
- per_country_age_restrictions (map of country -> min / max age,
with optional state-level overrides)
2. Create a verification session for an end user:
POST https://verification.didit.me/v3/session/
Body: workflow_id (from step 1), vendor_data (your own user id).
Response: session_url — redirect the user to it.
3. Listen for webhook callbacks (see "Webhooks" below).
### Path B — Standalone server-to-server API
Best when you already have a selfie image (mobile SDK capture, native
onboarding app, reseller pipeline) and only need a numeric age estimate
plus passive-liveness verdict on it. No adaptive ID fallback on this
path — wire that yourself if you need it.
POST https://verification.didit.me/v3/age-estimation/
Content-Type: multipart/form-data
Body fields:
- user_image (required, file — single selfie)
- age_estimation_decline_threshold (optional integer 0-100, default 18)
- face_liveness_score_decline_threshold (optional integer 0-100, default 30)
- rotate_image (optional boolean, default false)
- save_api_request (optional boolean, default true)
- vendor_data (optional string, your user id)
Response: JSON with request_id, age_estimation block, created_at.
## 3. Webhooks (Path A only — Path B returns synchronously)
- Register a webhook destination once via
POST https://verification.didit.me/v3/webhook/destinations/
Body: url, subscribed_events: ["session.verified", "session.review_started",
"session.declined"]
- Response includes secret_shared_key — store it.
- Every webhook delivery carries an X-Signature-V2 header you MUST verify
before trusting the payload. HMAC-SHA256 verification MUST run against the raw body bytes (the raw payload as Didit sent it) BEFORE any JSON parsing — re-serialising the parsed body changes whitespace and key order, which invalidates the signature.Algorithm:
1. sortKeys(payload) recursively
2. shortenFloats (truncate trailing zeros after the decimal point)
3. JSON.stringify the result
4. HMAC-SHA256 with the secret_shared_key
5. Hex-encode, compare to the X-Signature-V2 header.
## 4. Reading the report
### Path A (session) — age_estimation lives on the liveness object
The liveness object on the session report includes age_estimation as a
number-of-years field on the same selfie capture:
- liveness.status "Approved" | "Declined" | "In Review" | "Not Finished"
- liveness.method "PASSIVE" | "FLASHING" | "ACTIVE_3D"
- liveness.score number 0-100 (normalized liveness score)
- liveness.reference_image signed URL to the captured selfie (60-minute TTL)
- liveness.age_estimation estimated age in years (e.g. 24.3)
- liveness.warnings Array of risk objects (see below)
### Path B (standalone) — top-level age_estimation block
- request_id uuid
- age_estimation.status "Approved" | "Declined" | "In Review"
- age_estimation.method "PASSIVE"
- age_estimation.score number 0-100 (passive-liveness score)
- age_estimation.age_estimation estimated age in years (e.g. 27.33)
- age_estimation.user_image.entities array of detected faces, each with
age, bbox, confidence, gender
- age_estimation.user_image.best_angle integer
- age_estimation.face_quality 0-100 face image quality score
- age_estimation.face_luminance 0-100 face luminance score
- age_estimation.warnings Array of risk objects (see below)
- created_at ISO8601
### Warning catalog (both paths)
- AGE_BELOW_MINIMUM estimated age below the configured threshold
- AGE_NOT_DETECTED unable to estimate age (quality / lighting)
- LOW_LIVENESS_SCORE passive-liveness score below threshold
- NO_FACE_DETECTED no face in the capture
- LIVENESS_FACE_ATTACK presentation attack suspected
- FACE_IN_BLOCKLIST face matches an entry in your blocklist
- POSSIBLE_DUPLICATED_FACE face matches a previously verified face
## 5. Hard rules — do not change
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- Feature enum is UPPERCASE: AGE_ESTIMATION, LIVENESS, ID_VERIFICATION,
FACE_MATCH, AML, IP_ANALYSIS.
- 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).
- Always verify webhook signatures before trusting payload data.
- Status casing matches exactly: "Approved", "Declined", "In Review",
"Not Finished" (title-cased, space-separated).
- Reference image / video URLs are signed and expire in 60 minutes —
store only the verdict + score, never the biometric media.
## 6. Pricing reference (public)
- AGE_ESTIMATION standalone or bundled inside a workflow: $0.10 per check
- Adaptive fallback to ID Verification (when triggered): $0.15 per check
- Bundled in a full KYC workflow alongside Liveness + ID + IP: $0.33 per session
- 500 free verifications every month, forever, on every account.
## 7. Verify your integration
- Sandbox starts on signup at https://business.didit.me — no separate flag.
- Test images: deterministic synthetic faces returned in sandbox
(predictable estimated age band; trigger AGE_BELOW_MINIMUM by sending
the canonical "minor" test image).
- Switch to live: flip the application environment toggle in console.
When in doubt: https://docs.didit.me/core-technology/age-estimation/overview
Kwa ajili ya kuunda, kujaribu, na watumiaji wako wa kwanza.
Moduli 25+, bei wazi. Punguzo la kiotomatiki kwa wingi.
Kwa kiasi kikubwa na programu zilizodhibitiwa.
Punguzo la wingi hutumika kiotomatiki kadri matumizi yanavyoongezeka — hakuna mazungumzo, hakuna simu ya mauzo.
Didit ni miundombinu ya utambulisho na udanganyifu, jukwaa ambalo tulitamani lingekuwepo tulipokuwa tukijenga bidhaa sisi wenyewe: wazi, rahisi, na rafiki kwa waendelezaji, ili lifanye kazi kama sehemu halisi ya stack yako badala ya sanduku jeusi unalounganisha.
API moja inashughulikia kuthibitisha watu (KYC, mjue mteja wako), kuthibitisha biashara (KYB, ijue biashara yako), kuchunguza pochi za crypto (KYT, ijue miamala yako), na kufuatilia miamala kwa wakati halisi, kwenye stack iliyojengwa kuwa:
Alama ya miguu chini: aina 14,000+ za hati katika lugha 48+, vyanzo vya data 1,000+, na ishara za udanganyifu 200+ kwenye kila kipindi. Miundombinu ya Didit hujifunza kwa nguvu kutoka kila kipindi na inakuwa bora kila siku.
Ukadiriaji wa Umri hukadiria umri wa mtumiaji kutoka kwenye selfie moja, passiv, hakuna Hati ya Utambulisho inayohitajika, hakuna changamoto ya mwendo. Inafaa unapotaka kuweka kikomo cha umri (pombe, kamari, maudhui ya watu wazima, majukwaa ya watu wazima) lakini kukusanya Hati kamili ya Utambulisho kunaweza kuwa kupita kiasi kwa watumiaji wengi.
Kosa la wastani kabisa (MAE) ni ±3.5 miaka. $0.10 kwa kila ukaguzi kwenye Application Programming Interface (API) inayojitegemea, imejumuishwa kwa bei sawa ndani ya mtiririko wa kazi. Inalingana na Sheria ya Usalama Mtandaoni ya Uingereza na matarajio ya Umoja wa Ulaya ya kuweka kikomo cha umri. Marejeleo kamili: docs.didit.me/core-technology/age-estimation/overview.
POST /v3/age-estimation/ endpoint inayojitegemea, au $0.10 imejumuishwa ndani ya mtiririko wa kazi pamoja na Liveness. Uthibitishaji wa Umri wa Adaptive (wakati kesi ya mpaka inapoanzisha kiotomatiki upakiaji wa Hati ya Utambulisho) inatozwa kwa kiwango cha kawaida cha $0.15 cha Uthibitishaji wa Hati ya Utambulisho, tu kwa wachache walio kwenye mpaka, si kwa kila kipindi. Bei za umma: didit.me/pricing.Mchakato mzima kwa kawaida huchukua chini ya sekunde 30 kuanzia mwanzo hadi mwisho, chukua kitambulisho, piga picha hati, piga picha selfie, umemaliza. Hiyo ndiyo kasi zaidi sokoni. Watoa huduma wa zamani wa KYC kwa kawaida huchukua zaidi ya sekunde 90 kwa mchakato huo huo.
Kwa upande wa nyuma, Didit inarudisha matokeo kwa chini ya sekunde mbili kwa p99, ikipimwa kutoka wakati mtumiaji anamaliza selfie hadi wakati webhook yako inawashwa. Upigaji picha wa simu umeboreshwa kwa simu za polepole na mitandao ya polepole: ukandamizaji wa picha unaoendelea, upakiaji wa polepole wa software development kit, na uhamishaji wa kugusa mara moja kutoka desktop kwenda simu kupitia QR code ikiwa mtumiaji anaanza kwenye wavuti.
Kwenye session Application Programming Interface (API), Ukadiriaji wa Umri huishi kwenye liveness object kama age_estimation, upigaji picha wa selfie uleule hutoa ishara zote mbili (upigaji picha mmoja, matokeo mawili).
Kwenye standalone Application Programming Interface (API) (POST /v3/age-estimation/), jibu hubeba block ya age_estimation ya kiwango cha juu:
status, Approved, Declined, In Review, Not Finished.method, PASSIVE.score, age_estimation (umri uliokadiriwa kwa miaka), face_quality, face_luminance, warnings.user_image.entities[], umri kwa kila uso, bounding box, uaminifu, jinsia.Kila kipindi huishia katika mojawapo ya hadhi saba zilizo wazi, hivyo code yako inajua nini cha kufanya kila wakati:
Approved, kila ukaguzi umefaulu. Mpeleke mtumiaji mbele.Declined, ukaguzi mmoja au zaidi umefeli. Unaweza kumruhusu mtumiaji kutuma upya hatua maalum iliyofeli (kwa mfano, kupiga selfie upya) bila kurudia mchakato mzima.In Review, imewekewa alama kwa ukaguzi wa kufuata sheria. Fungua kesi kwenye console, angalia kila ishara, amua kuidhinisha au kukataa.In Progress, mtumiaji yuko katikati ya mchakato.Not Started, kiungo kimetumwa, mtumiaji bado hajafungua. Tuma ukumbusho ikiwa itakaa muda mrefu sana.Abandoned, mtumiaji alifungua kiungo lakini hakumaliza kwa wakati. Mshawishi tena au muda wake uishe.Expired, muda wa kiungo cha kipindi umeisha. Unda kipindi kipya.Webhook iliyosainiwa huwashwa kila mabadiliko ya hadhi, hivyo database yako inabaki kusawazishwa kila wakati. Vipindi vilivyoachwa na vilivyokataliwa ni bure.
Data ya uzalishaji inachakatwa na kuhifadhiwa katika Umoja wa Ulaya kwa chaguo-msingi, kwenye Amazon Web Services. Mikataba ya Enterprise inaweza kuomba maeneo mbadala kwa mamlaka ambazo wadhibiti wao wanahitaji.
Usimbaji fiche kila mahali. AES-256 wakati wa kupumzika kwenye kila database, hifadhi ya vitu, na backup. Usalama wa Tabaka la Usafirishaji 1.3 wakati wa kusafirisha kwenye kila simu ya API, webhook, na kipindi cha Business Console. Data ya kibayometriki imesimbwa kwa njia fiche chini ya Ufunguo Mkuu wa Mteja tofauti.
Uhifadhi ni wako kudhibiti. Uhifadhi wa chaguo-msingi ni usio na kikomo (unlimited) isipokuwa ukisanidi mfupi zaidi, kati ya siku 30 na miaka 10 kwa kila programu, na unaweza kufuta kipindi chochote cha kibinafsi wakati wowote kutoka kwenye dashibodi au API.
Vyeti: SOC 2 Aina ya 1 & Aina ya 2, ISO/IEC 27001:2022, iBeta Kiwango cha 1 PAD, na uthibitisho wa umma kutoka Tesoro / SEPBLAC / CNMV ya Uhispania kwamba uthibitishaji wa utambulisho wa mbali wa Didit ni salama zaidi kuliko kumthibitisha mtu ana kwa ana. Ripoti kamili inapatikana kwenye /security-compliance.
Didit inatii sheria kwa chaguo-msingi kwa wasimamizi muhimu kwa miundombinu ya utambulisho:
Memo ya kina, kila cheti, kila barua ya mdhibiti: /security-compliance.
Njia tatu za kuunganisha, chagua inayofaa stack yako:
Dashibodi sawa, bili sawa, bei sawa ya kulipa kwa mafanikio kwa zote tatu. Mwongozo wa hatua kwa hatua unapatikana kwenye docs.didit.me/integration/integration-prompt.
API moja kwa KYC, KYB, Ufuatiliaji wa Miamala, na Uchunguzi wa Wallet. Unganisha ndani ya dakika 5.