Fish Audio

The tenant's own Fish Audio key, so SHAI's replies in the portal are spoken by Fish Audio's text-to-speech endpoint (POST https://api.fish.audio/v1/tts, chunked audio, model header s1 / s2-pro / s2.1-pro). Portal only: Twilio's ConversationRelay carries Google, Amazon and ElevenLabs voices and not Fish Audio, so a Fish Audio tenant's calls use Twilio's documented default voice and Settings -> Voice says so.

connectable today

Connect Fish Audio

How SHAI connects to it

SHAI talks to it directly, with the key you paste. It is one of the tools SHAI has written up — what it costs, why it matters, what breaks without it — as `fishaudio-api-key` in the tool guide.

What it needs

a key you paste, in Setup or on /connections

Nothing else. It is connectable on this deployment as it stands.

Route read from docs/tools/tools.json (fishaudio-api-key) · docs.fish.audio/overview/mcp (https://api.fish.audio/mcp) · verified 2026-10-28 · entry 20001 of the integrations list

Whatever a run does with this tool goes through one door and one approval row: reading is allowed by default, anything that writes, sends or spends stops and asks first, and you can set that per tool on Connect My Tools.