Pointing the Assistant to your own TTS endpoint is definitely possible, but it needs to be set up in a way that properly overrides the dashboard config — otherwise the CLI keeps throwing those errors. I’ve handled similar setups before, usually by adjusting how the assistant transport is defined and making sure the JSON lines up with what the API expects. Would you like me to assist you directly in getting this working with your TTS? @msc