Skip to main content

​
“no API key configured”

rime usage reports this when no key is stored, but the TTS commands fail with “authentication failed: invalid API key” instead. Run rime login or set the environment variable:

​
“authentication failed: invalid API key”

The API rejected the key the CLI sent. Run rime config show to see which key the CLI resolved and where it came from, because a stale RIME_CLI_API_KEY overrides the key in rime.toml. Then verify the key at app.rime.ai/tokens and run rime login again.

​
”unsupported format: … (supported: wav, mp3)”

The CLI writes only WAV or MP3, and coda and mistv3 default to WAV. If you pick a format a model can’t serve, the API rejects it, not the CLI. Select a supported format explicitly:

​
No audio playback

  • Check your system audio output settings
  • Try saving to a file instead: rime tts "Hello" -s astra -m coda -o output.wav
  • Headless builds (e.g., Docker) require -o FILE because they have no audio playback

​
”command not found: rime”

The shell installer adds its bin directory (~/.rime/bin by default) to your PATH through your shell’s startup file, and the change reaches only new shells. Open a new terminal window or run:
If you skipped the installer’s PATH prompt, the startup file wasn’t changed. Add the line the installer printed to your shell config, then reload it.