Voice Verification

biometric-core voice 1:1 engine with provider contract.

Roadmap

Runs against the biometric-core voice engine (mock adapter until a certified provider is registered).

Engine

src/lib/verification/biometric-core/voice (mock adapter — ready for provider)

API

POST /api/public/biometrics/v1/enroll · /compare

Roadmap service — not part of the Veridexa launch

Voice Verification is on the Veridexa roadmap. It is not offered commercially today: no certified engine, hardware, or trust anchors are integrated, and nothing on this page should be read as an available production capability. The contracts, storage schema, and API surface documented below exist so a certified provider can be integrated later without call-site changes. Mock adapters are used for tests only and never produce verification evidence.

Live Veridexa services today: Document Fraud Detection, Face Verification, and Biometric Portrait Consistency.

The voice engine follows the same enrolment / verify / quality / audit contract as every other modality. A mock adapter powers deterministic tests; a production speaker-verification provider registers behind the same interface.

What is implemented

  • Engine, types and mock adapter
  • Voice modality added to the core registry
  • Wired through /enroll and /compare

Modules

src/lib/verification/biometric-core/voice/
  engine.ts
  types.ts
  mock-adapter.ts
src/lib/verification/biometric-core/providers/mock-voice.ts
biometric-core.api/v1 · isolated from Fraud Detection · mock adapters clearly labelled; certified providers register behind the same contracts.