Liveness Detection
Liveness and presentation-attack detection behind a certified provider contract.
Liveness is in preparation — its own playground explains the current status and the endpoint returns 503 liveness_not_available.
Engine
Pending certified provider (src/lib/verification/liveness-provider — adapter only)
API
Unavailable — /api/v1/biometrics/liveness* returns 503 liveness_not_available
Liveness Detection is in preparation. Veridexa does not currently offer a liveness or presentation-attack-detection service, and no liveness endpoint returns a verification decision. Earlier capture experiments were diagnostic prototypes only; they have been frozen internally and removed from the platform. We will launch this service only once a certified engine is integrated behind our provider adapter.
Current status
- No public liveness service, endpoint, or playground
POST /api/v1/biometrics/liveness*returns503 liveness_not_available- No liveness claims are made in any product surface or contract
- No liveness decision, score, or evidence is produced today
What the launched service will return
- Verified face presence
- Active challenge evidence
- Passive PAD evidence (ISO/IEC 30107-3 evaluated engine)
- Anti-replay result
- Injection / deepfake risk result
- Signed session evidence and an auditable event timeline
- Exact failure reason plus per-signal confidence scores
Integration contract
A production engine connects through the strict adapter in src/lib/verification/liveness-provider. Adapters translate a vendor response into the contract; they may not compute, infer, or synthesise evidence. Diagnostic counters and simulated challenge states are never accepted as verification evidence.
Need liveness for a project? Talk to us and we will notify you at launch.