OpenClaw Gradium provider
OpenClaw’s provider reference for Gradium TTS.
GitHub integration
View the OpenClaw Gradium extension source.
Gradium TTS guide
Gradium WebSocket TTS setup and streaming behavior.
Setup
Create a Gradium API key, then expose it to OpenClaw with an environment variable:messages.tts.providers.gradium.apiKey in ~/.openclaw/openclaw.json.
Basic config
Setgradium as the TTS provider and choose a Gradium voice ID.
auto: "always" when every eligible agent reply should include audio. Use OpenClaw’s session commands or per-agent config when you need more targeted behavior.
Provider settings
| Setting | Description |
|---|---|
messages.tts.provider | Set to gradium to make Gradium the primary TTS provider. |
messages.tts.providers.gradium.apiKey | Gradium API key. You can use ${GRADIUM_API_KEY} or rely on the environment variable. |
messages.tts.providers.gradium.voiceId | Default Gradium voice ID for replies. |
messages.tts.providers.gradium.baseUrl | Optional Gradium API origin override. Defaults to https://api.gradium.ai. |
Voices
OpenClaw’s Gradium provider defaults to Emma.| Voice | Voice ID |
|---|---|
| Emma | YTpq7expH9539ERJ |
| Kent | LFZvm12tW_z0xfGo |
| Tiffany | Eu9iL_CYe8N-Gkx_ |
| Christina | 2H4HY2CBNyJHBCrP |
| Sydney | jtEKaLYNn6iif5PR |
| John | KWJiFWu2O9nMPYcR |
| Arthur | 3jUdJyOi9pgbxBTK |
Output behavior
OpenClaw chooses the Gradium output format from the destination surface:| Destination | Gradium output |
|---|---|
| Standard audio reply | WAV audio file |
| Voice-note channel | Opus voice-compatible audio |
| Telephony surface | ulaw_8000 at 8 kHz |
When to use OpenClaw with Gradium
- Messaging-channel agents: speak replies across OpenClaw-supported channels without building per-channel audio delivery.
- Voice-note workflows: send spoken responses as voice-compatible channel media.
- Telephony surfaces: synthesize 8 kHz u-law audio for phone-oriented integrations.
- Self-hosted agent stacks: keep OpenClaw’s local gateway model while using Gradium for speech output.