Migrating from Fish Audio

​

What is served

​

What to change

-export FISH_API_KEY="…"
+export FISH_API_KEY="aireserve_api_…"                     # your AI Reserve API key
+export FISH_BASE_URL="https://api.aireserve.com/fish-audio"

import os
from fishaudio import FishAudio
from fishaudio.core.request_options import RequestOptions
from fishaudio.utils import save

client = FishAudio(
    api_key=os.environ["FISH_API_KEY"],          # aireserve_api_…
    base_url="https://api.aireserve.com/fish-audio",
)

audio = client.tts.convert(text="Hello from Fish Audio, through AI Reserve.", model="s2.1-pro")
save(audio, "hello.mp3")

with open("meeting.wav", "rb") as f:
    transcript = client.asr.transcribe(
        audio=f.read(),
        request_options=RequestOptions(additional_headers={"model": "transcribe-1-pro"}),
    )
print(transcript.text, transcript.duration)

import { FishAudioClient } from "fish-audio";

const fishAudio = new FishAudioClient({
  apiKey: process.env.FISH_API_KEY,                 // aireserve_api_…
  baseUrl: "https://api.aireserve.com/fish-audio",
});

const audio = await fishAudio.textToSpeech.convert({ text: "Hello from Fish Audio, through AI Reserve." }, "s2.1-pro");
const transcript = await fishAudio.speechToText.convert({ audio: myAudio }, { headers: { model: "transcribe-1-pro" } });
const voices = await fishAudio.voices.search({ title: "narrator" });

# Text to speech (JSON; the SDKs send MessagePack — both pass through)
curl -X POST https://api.aireserve.com/fish-audio/v1/tts \
  -H "Authorization: Bearer $FISH_API_KEY" -H "Content-Type: application/json" -H "model: s2.1-pro" \
  -d '{"text":"Hello from Fish Audio, through AI Reserve.","reference_id":"933563129e564b19a115bedd57b7406a","format":"mp3"}' \
  --output hello.mp3

# Speech to text
curl -X POST https://api.aireserve.com/fish-audio/v1/asr \
  -H "Authorization: Bearer $FISH_API_KEY" -H "model: transcribe-1-pro" \
  -F "audio=@meeting.wav" -F "ignore_timestamps=false"

# Voice library
curl "https://api.aireserve.com/fish-audio/model?title=narrator&language=en" -H "Authorization: Bearer $FISH_API_KEY"

​

Voice cloning

​

What AI Reserve enforces

• Your organization’s policies. The key is checked exactly as on every AI Reserve endpoint: paused keys (401), invalid keys (401, Invalid API key.), per-key IP allowlists and organization network policies (403), rate limits (429 with Retry-After), and — on every POST — your organization’s spend caps and wallet (402). A Fish request is a wallet request: an exhausted budget refuses it before Fish is called.
• Metering is a precondition, not an afterthought. A /v1/tts body the gateway cannot read as JSON or MessagePack with a string text is refused with 400 before any upstream call; a deployment that cannot reach the ledger refuses billable calls with 503 rather than serving them unmetered.
• Headers. Your Authorization and x-api-key are replaced by AI Reserve’s Fish key; Accept-Encoding is pinned to identity so Fish’s bytes are the bytes relayed. The model header, content types and your client’s user agent go through. Fish’s X-Generation-Id comes back on every synthesis and transcription.
• A request log. Each call is recorded with method, path, Fish’s generation id, upstream status, byte counts, time-to-headers, duration, outcome, your key id, and the metered amount. Refusals are recorded with their outcome before any upstream request. Neither includes bodies, audio, or credentials.
• Transport. Fish unreachable → 503; no response headers within the time-to-headers bound (sized for multi-minute transcriptions) → 504; a stream that has started is never cut by that bound.

​

Limits

• Rate limits are Fish’s concurrency tiers, shared. Fish limits concurrent requests per account, not per key; AI Reserve’s account tier is shared across every organization using this endpoint, and a 429 from Fish is relayed as Fish sends it (without Retry-After). Back off exponentially, as Fish’s own docs advise.
• One Fish account, Fish’s data handling. Text, audio uploads and reference audio reach Fish Audio under AI Reserve’s account and Fish’s terms. See the provider data-handling page.
• No stored voices, no WebSockets, no agents, no wallet (above).
• The native API only. Fish’s OpenAI- and ElevenLabs-compatible endpoints (/compat/*, /elevenlabs/*) are not mounted; use the OpenAI shape on AI Reserve’s own /v1/audio/speech instead.