use case
verified July 2026
A reading voice that is not a punishment.
Accessibility is the use case a meter distorts most quietly. The alt text gets terser, the description gets skipped, the confirmation stops being read back — each one a small saving, and together the difference between a product someone can use and one they cannot.
01
Where the meter edits accessibility
Every accessible affordance is extra characters: the longer image description, the read-back of a confirmation number, the heading structure spoken aloud, the error explained rather than announced. On a meter each of those has a price, and the pressure is always toward saying less.
On a seat the extra sentence is free, which removes the argument entirely. The decision returns to what a person needs to hear.
The whole text, every time
Film
The longer description, the spoken read-back, the error explained rather than announced. On a seat none of those is a saving anyone is tempted to make.
02
What matters technically
- Spell tags read codes, references and confirmation numbers character by character, which is the difference between a usable read-back and a guess.
- A low temperature holds a steady, predictable delivery — the right setting for a voice someone listens to all day.
- Break tags let a structure be heard: a real beat between a heading and its content.
- 24 kHz output by default, so the audio is full-rate rather than the compressed telephony band.
03
Notes — an engineer's checklist
01Is this a screen reader?
No — it is the synthesis layer a screen reader or an application can call. Gandr turns text into audio over an API; the navigation model, the semantics and the focus handling stay in your product or in the assistive technology the person already uses.
02What sample rate does the audio come back at?
24 kHz mono PCM by default, which is the full-rate audio rather than the 8 kHz telephony band. Set output_sample_rate if your playback path wants something else.
See also — related sheets
capability
7.9
Delivery is a request parameter
The prosody dial moves measured pitch range from 10.1 to 18.0 semitones on one voice, one sentence — continuous per-request control on the production API.
use case
$0
The course that can afford to be updated
Course audio on a flat seat: when re-narrating a module costs nothing per character, curriculum updates stop being an annual event.
capability
3
A text-to-speech API built for live audio
REST, SSE, and WebSocket TTS from one endpoint: 107 ms measured first audio, instant cloning from ten seconds, and a flat per-seat price with usage unmetered.
use case
1
Ship the voice in every market, not the top three
Localised product audio on a flat seat: one cloned identity across 23 languages, with the character count no longer deciding which markets get voice.
A key and one seat to build this on — the same production API this page measures.
Request access for this use case