Skip to content

who it’s for

verified July 2026

Gandr for developers.

The whole API fits in your head: one base URL, one request schema, three surfaces. Cloning is a field on the request, not a training job. And because the bill is flat, you never write rate-limiting code to protect your own wallet.

01

The parts, in one breath

  • POST /v1/tts/bytes returns a complete WAV; POST /v1/tts/sse streams base64 PCM chunks; wss://…/ws holds one socket per live call.
  • A ten-second reference clip rides inside the request and comes back as a working clone — no enrollment pipeline.
  • Six expression controls and four transcript controls, documented on every surface.
  • If you have integrated another TTS API, the schema will look familiar — the switch is a diff, not a rewrite.

02

What flat pricing changes in your code

On a meter, retries cost money, dev loops cost money, and load tests are a line item — so codebases grow guard rails against their own vendor. On a line, none of that code exists: retry as aggressively as your UX wants, run the test suite against production, and let staging talk all night.

03

Where to start

The docs page carries the full request shape, authentication, error semantics, and copy-paste quickstarts. The console on the home page runs the production API from your browser — type a line and the first chunk lands in about a hundred milliseconds.

See also

Related sheets.

Thirty minutes on your own numbers — fleet size, talk time, and the bill both ways, worked live.

Bring your stack to the call