{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/text-to-speech.names-numbers-codes/",
    "json": "https://www.anchorterminal.com/niches/text-to-speech.names-numbers-codes/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/text-to-speech.names-numbers-codes/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/text-to-speech.names-numbers-codes/index.min.md"
  },
  "markdown": "Four or more companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 7 | 13 | 38 | 10 | 7 |\n\n## What counts as done\n\nA year, a unit, a six-character code, acronyms and surnames are handled in the request language by the model's documented normalisation or by a documented override (dictionary, phoneme tag, alias) applied in one further call.\n\nMeasured, for our own tests: on a fixed test list (a year, a unit such as 135 ms, a six-character code, three acronyms, two surnames) every item is read correctly in the request language, or the override fixes a miss in one further call.\n\nHow agents ask for it: read back the account number; say this product name right; speak this confirmation code\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Amazon Polly (Amazon Web Services, Inc.)**: say-as, sub and phoneme tags plus PLS lexicons (alias or phonetic, up to five per request, also on the stream via LexiconNames) fix a miss in one further call; phoneme is partial on generative voices.\n- **Fish Audio TTS API (Hanabi AI Inc.)**: Pronunciation dictionaries with phoneme and alias rules are created and versioned over the API or sent inline, phoneme tags cover English, Chinese and Japanese, and normalize plus a language tag spells out numbers and units in 15 language families, on the WebSocket too.\n- **Google Cloud Text-to-Speech (Google LLC)**: SSML say-as (cardinal, characters, verbatim, telephone), sub and phoneme work on sync requests, and Chirp 3 HD takes a custom_pronunciations field in IPA or X-SAMPA; SSML is not applied on streaming requests.\n- **Inworld Realtime TTS-2 (Theai, Inc. dba Inworld AI)**: Inline /IPA/ replaces a word in the text, a workspace pronunciation dictionary applies with enable_custom_pronunciation on TTS-2 requests with an explicit language, and the docs index lists verbatim tags for codes and IDs.\n- **MiniMax Speech (T2A) (Nanonoble Pte. Ltd.)**: pronunciation_dict tone rules replace a word with plain text, pinyin, IPA or kana on sync, async and WebSocket routes, and inline (IPA) or (pinyin) in parentheses overrides one occurrence, so a miss is fixed in one further call.\n- **Murf TTS API + MCP (Murf Inc.)**: Inline IPA in quotes and slashes in the text, or pronunciationDictionary with IPA or SAY_AS entries, work on Stream Speech and WebSocket voice_config on Falcon 2.1, so a wrong surname is fixed in one further call.\n- **Rime TTS API + MCP (Rime Labs, Inc.)**: Normalisation expands numbers, dates, currency and units, spell() forces letter-by-letter codes on both models, customLexicon sends X-SAMPA pronunciations with Coda requests over HTTP, WebSocket and gRPC in six languages, and /textnorm shows what will be read.\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Azure AI Speech text-to-speech (Microsoft Corporation)**: phoneme (IPA, SAPI, UPS), say-as, sub and custom lexicons are documented, but HD voices support only a subset of SSML, and acc-27 shows an en-US multilingual voice reading numbers in Chinese with Microsoft offering only SSML or rewording as a fix.\n- **Cartesia Sonic TTS API + MCP (Cartesia AI, Inc.)**: Pronunciation dictionaries (IPA or sounds-like) apply on every TTS endpoint through pronunciation_dict_id, a spell tag forces character read-out and a normalization field sets number conventions, but entries default to case-insensitive on Sonic 3.6, the September change the listing records.\n- **Deepgram Text-to-Speech (Aura-2, Flux TTS) (Deepgram, Inc.)**: Inline IPA pronunciation is Early Access on Flux, English only and cannot be combined with speed or pause; Aura-2 has it in English and Spanish; numbers and dates are normalised in ten languages, the rest must be written out; SSML is stripped.\n- **ElevenLabs Text to Speech API + MCP (Eleven Labs Inc.)**: Pronunciation dictionaries with alias and IPA or CMU phoneme rules apply through pronunciation_dictionary_locators (up to three), v4 reads inline /IPA/, and apply_text_normalization has on, off and auto; but phoneme rules work only on eleven_flash_v2, Flash v2.5 misreads large numbers, and its normalisation toggle is Enterprise only.\n- **Fish Audio Drama 3 (39 AI, Inc. (the licensor named in the Fish Audio Community License). fish.audio's terms of use name Hanabi AI Inc. as the provider of the hosted services)**: Fish Audio's Drama 3 page documents phoneme tags (Arpabet, pinyin, romaji) as a model feature, but the fish-speech inference guide shows no dictionary, alias or normalisation option for the local server, so a miss is fixed only by editing the text.\n- **Fish Audio S2 Pro (39 AI, Inc. (the licensor named in the Fish Audio Research License). fish.audio's terms of use name Hanabi AI Inc. as the provider of the hosted services)**: Fish Audio's docs describe phoneme tags as a feature of the S2 family, but the fish-speech inference guide for the local server lists no dictionary, alias or normalisation control, so a misread must be fixed by rewording.\n- **HeyGen Voice (HeyGen Technology, Inc.)**: pronunciation_dictionary takes up to 100 IPA terms on both speech endpoints, but only on heygen-voice-1 and heygen-voice-1-turbo (not Turbo Free), matching ignores case, and there is no number or say-as control.\n- **Ming-3.0-tts-0.5B (inclusionAI (the LICENSE's copyright holder; source headers read Copyright (c) Ant Group))**: FST text normalisation covers numbers, dates, units and symbols but needs pynini, which has no universal wheel, and the README's first place on Artificial Analysis pronunciation robustness is self-reported; no dictionary or phoneme override exists.\n- **Ming-3.0-tts-tiny (inclusionAI, Ant Group (named in the site footer of inclusion-ai.org; the LICENSE copyright line reads inclusionAI))**: FST normalisation for numbers, dates and units needs pynini, the Artificial Analysis pronunciation lead in the README is self-reported, and no dictionary or phoneme override exists.\n- **OmniVoice (k2-fsa, the Next-gen Kaldi open-source project. The paper's authors are at Xiaomi Corp.; no company is named as the licensor)**: English pronunciation is overridden inline with CMU Arpabet in brackets and Chinese with tone-number pinyin, but digits are read digit by digit unless normalize_text (an optional extra) is on, and other languages fall back to num2words for integers only.\n- **Resemble AI Text-to-Speech API (Resemble AI, Inc.)**: data accepts text or SSML on all three routes, with partial SSML support on HTTP streaming, but no page lists which tags (phoneme, say-as, sub) Resemble Ultra honours, so an override cannot be confirmed.\n- **Smallest.ai Lightning TTS (Smallest, Inc.)**: pronunciation_dicts fix names and acronyms on sync, SSE and WebSocket routes, but entries are respellings, not IPA, there is no SSML, and nothing documents how years, units or codes are read.\n- **Soniox Text-to-Speech (Soniox Inc.)**: Soniox claims accurate alphanumerics, phone numbers and IDs, but no dictionary, phoneme tag or alias is on either API, so a miss cannot be fixed without rewording.\n\n- not this job: Audio8-TTS-Realistic 0.6B (Edge0 (edge0.ai), which names no legal entity or location on its site. The technical report's authors give their affiliation as AutoArk, and commit metadata in Edge0-AI/Audio8_TTS uses an autoark.ai domain): No phoneme tag, dictionary, alias or normalisation option in the card or README.\n- not this job: Qwen3-TTS 12Hz 1.7B CustomVoice (Alibaba Cloud (the copyright holder in the Qwen licences; RDAP names Alibaba Cloud (Singapore) Private Limited as registrant of qwen.ai, from the first batch's check)): No pronunciation dictionary, phoneme tag, SSML or normalisation setting is documented; the only control is a natural-language instruct for style.\n- not this job: VieNeu-TTS v3 Turbo (Phạm Nguyễn Ngọc Bảo, an individual (named on the card as author; Hugging Face account pnnbao-ump, GitHub account pnnbao97). No company found): No phoneme tag, dictionary or alias is documented; the g2p phonemizer runs internally with no override.\n\n## What stops agents finishing\n\n- no pronunciation control at all (Deepgram strips SSML; ElevenLabs Flash v2.5 number normalisation is Enterprise only)\n- a dictionary that silently changes behaviour (Cartesia dictionaries became case-insensitive in September 2026)\n- LLM-written text the agent cannot pre-edit, so a fix that needs rewording (acc-27) does not apply\n\n## Around it\n\nBefore: inference.chat-completion. After: text-to-speech.voice-agent-turn.\n\n## Where this comes from\n\nWeight 10 of 100 in Text-to-speech: 7 of 46 accounts tagged (acc-08, 09, 10, 24, 26, 27, 42); every one is a failure report, and the buyer check names it, so weighted above its count\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/text-to-speech.names-numbers-codes.json, or the MCP tool get_use_case with id text-to-speech.names-numbers-codes. Draft, read 2026-11-12 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Read names, numbers, acronyms and codes precisely",
        "url": ""
      }
    ],
    "description": "Read names, numbers, acronyms and codes precisely: 7 companies fully do it, 13 with a limit, 38 carry the tag. Every listing in Text-to-speech with the reason and a source.",
    "facts": null,
    "h1": "Read names, numbers, acronyms and codes precisely",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/text-to-speech.names-numbers-codes/",
    "published": "",
    "section": "agents",
    "title": "Read names, numbers, acronyms and codes precisely | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/text-to-speech.names-numbers-codes/"
  },
  "tokens": {
    "markdown": 2450,
    "slim": 580
  },
  "version": 1
}
