hat error usually points to the CLI not getting the config it expects, not your API key. I’ve run into this when the JSON structure was off or when TTS params were in the wrong place. Easiest way to confirm is testing the request against the API directly instead of only through the CLI. Quick question — are you trying to set a custom voice in the assistant config, or are you hooking in your own TTS endpoint? That’ll make it clearer where it’s breaking. @msc