Entries claiming languages without naming or counting
Three entries claim breadth and produce no figure. Full multi-language support, multiple languages and audio types, and an optional language field with no values. None can be checked, and none can be wrong. As of 2026-09-22.
| Model | The claim as published | And where a voice comes from |
|---|---|---|
| D-ID | A language field, no list | A voice id, or a recording by url |
| Hedra | A claim with no names | A track, or a voice id from the endpoint |
| PixVerse | Multiple, none of them named | A sample, or a built-in voice |
Inclusion rule. Entries whose documentation asserts more than one spoken language without naming any or giving a number. Entries with a published total are on a separate route page. Order. Alphabetical by model name.
1An unfalsifiable claim is still worth recording
None of these three can be tested against a page. No market is named, so none can be missing, and the claim survives any amount of contrary experience. It sits one grade above silence only because it tells a reader the capability is intended.
Recording it as a claim rather than promoting it to coverage is the whole point of keeping wording instead of ticks. A feature table with a checkmark in this column for all three would be describing a market that does not exist.
2Two of the three have somewhere the answer could live
One delegates its voices to five named speech providers, so the enumeration belongs to them and is genuinely published, one level down. Another draws voices from an endpoint, which means the inventory is current and unreadable at the same time.
Both arrangements are defensible engineering and poor commissioning. A decision about which markets a series can reach is usually taken by somebody who will never call an endpoint or audit five upstream catalogues.
3One of them answers a different question instead
The third entry names kinds of performance rather than places: speech, singing and advertisements. That is information nobody else in this register offers, and it is in the wrong column for a market decision.
It is a useful reminder that a blank is not always laziness. A vendor can think carefully about registers of delivery and never think about geography, and the register records both halves of that rather than averaging them.
4The entries on this route, one page each
Each of these links to that entry on the field this route groups by. The wording behind every cell, and the date it was read, sits on the page it links to.
- D-ID — a language field, no list.
- Hedra — a claim with no names.
- PixVerse — multiple, none of them named.
- LanguagesDescribed as text, image and audio to video with full multi-language support, and a maximum duration of ten minutesa claim carrying no list
- LanguagesMultiple languages and audio types are supported, including speech, singing, and advertisementsmultiple, none of them named
- Voice sourceFive speech providers are named for the voice: Microsoft, ElevenLabs, Amazon, Google and Azure OpenAIoutside catalogues named on the page
- Per-character bindingThe voice is a voice id selected from the list of available voices, with an optional language field beside ita voice id on every request
- Voice sourceText to speech supports both built-in voices and custom voices created from user-provided sample audiocatalogue or supplied sample
5Sources
Membership of this route is decided by the wording in the field it groups by, read from the documentation each vendor publishes. The column itself is on the field note, all five columns are on the speech table, and what counts as documented is on how read. Other routes: A figure in writing, A named driver.