Skip to content
Detectif.ai Aletheia logo

Detectif.ai Aletheia

Scores call audio for cloned or generated voices and checks whether a speaker matches an enrolled voiceprint.

Actively maintained

At a glanceswept Oct 17, 2026

not read yet

Use

For
Banks, lenders, insurers and contact centers verifying customer voices on phone calls
Activity
Actively maintainedrelease 12 days ago · site updated 4 weeks ago
Runs as
API
Used for
  • score customer calls for synthetic speech before account changes
  • flag cloned voices in payment and transfer requests
  • check remote identity checks for synthetic or replayed speech
Worth knowingcomputed from what we read · each with its source
  • Has an MCP server (1 in the registry)public registry →
How a program reaches itfound, not claimed · read Oct 27, 2026
  • MCP serverai.detectif.platform/detectifverified in the MCP registry
  • Stateanswers, requires sign-inchecked 2026-10-27
  • Address to connectplatform.detectif.ai/mcp
  • OpenAPI spec10 pathsthe spec ↗
  • API docsplatform.detectif.ai/dashboard/deepfakethe vendor's page ↗

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use Detectif.ai Aletheia for?

Sign in to leave a note
Questions this page answers
  • What is Detectif.ai Aletheia?

    Scores call audio for cloned or generated voices and checks whether a speaker matches an enrolled voiceprint.

  • Who is Detectif.ai Aletheia for?

    Banks, lenders, insurers and contact centers verifying customer voices on phone calls

  • Do people use Detectif.ai Aletheia?

    Little sign of use.

  • Is Detectif.ai Aletheia still maintained?

    Actively maintained: release 12 days ago · site updated 4 weeks ago.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk