Migrating from Inworld

​

What is served

​

What is not served here

​

What to change

-export INWORLD_API_KEY="…"
+export INWORLD_API_KEY="aireserve_api_…"                  # your AI Reserve API key
+export INWORLD_BASE_URL="https://api.aireserve.com/inworld"

import os
from inworld_tts import InworldTTS

client = InworldTTS(
    api_key=os.environ["INWORLD_API_KEY"],         # aireserve_api_…
    base_url="https://api.aireserve.com/inworld",
)

audio = client.tts.synthesize(text="Hello from Inworld, through AI Reserve.", voice_id="Ashley", model_id="inworld-tts-2")
with open("hello.mp3", "wb") as f:
    f.write(audio.audio_bytes)

import { InworldTTSClient } from "@inworld/tts";

const inworld = new InworldTTSClient({
  apiKey: process.env.INWORLD_API_KEY,             // aireserve_api_…
  baseUrl: "https://api.aireserve.com/inworld",
});

const audio = await inworld.tts.synthesize({ text: "Hello from Inworld, through AI Reserve.", voiceId: "Ashley", modelId: "inworld-tts-2" });
const voices = await inworld.voices.list();        // stock voices + your organization's clones

import OpenAI from "openai";

const openai = new OpenAI({ apiKey: process.env.INWORLD_API_KEY, baseURL: "https://api.aireserve.com/inworld/v1" });
const speech = await openai.audio.speech.create({ model: "inworld-tts-2-flash", voice: "Ashley", input: "Hello from AI Reserve." });

# Text to speech, native shape
curl -X POST https://api.aireserve.com/inworld/tts/v1/voice \
  -H "Authorization: Basic $INWORLD_API_KEY" -H "Content-Type: application/json" \
  -d '{"text":"Hello from Inworld, through AI Reserve.","voiceId":"Ashley","modelId":"inworld-tts-2"}'

# Speech to text
curl -X POST https://api.aireserve.com/inworld/stt/v1/transcribe \
  -H "Authorization: Basic $INWORLD_API_KEY" \
  -F 'transcribeConfig={"modelId":"inworld-stt-1"};type=application/json' -F "file=@meeting.wav"

# Voice list
curl "https://api.aireserve.com/inworld/voices/v1/voices?pageSize=20" -H "Authorization: Basic $INWORLD_API_KEY"

​

Voice cloning and designed voices

​

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). An Inworld request is a wallet request: an exhausted budget refuses it before Inworld is called.
• Your voices stay yours. A stored voice that belongs to another AI Reserve organization — named in the path of /voices/v1/voices/{id} or as the voiceId / voice of a synthesis — answers 404 voice not found, exactly as Inworld answers for a voice that does not exist. A voice in AI Reserve’s workspace that no organization has claimed is refused the same way. If the ownership check itself cannot run, the call is refused with 503 rather than forwarded unverified. A voice whose ownership could not be recorded at creation is removed from Inworld again and the create answers 503; retry it.
• Metering, never filtering. The gateway reads the text / input, voiceId / voice and modelId / model of a synthesis body and the usage of a transcription answer to price and scope the call; it never changes, drops or validates what you sent. A body it cannot read is still forwarded and, if Inworld serves it, recorded at $0 marked for repair. The one answer the gateway edits is a voice list, where other organizations’ voices are removed.
• Headers. Your Authorization and x-api-key are replaced by AI Reserve’s Inworld credential; Accept-Encoding is pinned to identity so Inworld’s bytes are the bytes relayed. Content types and your client’s user agent go through.
• A request log. Each call is recorded with method, path, 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. Inworld unreachable → 503; no response headers within the time-to-headers bound → 504; a stream that has started is never cut by that bound.

​

Limits

• Rate limits are Inworld’s account tiers, shared. Inworld limits requests and concurrency per account, not per key; AI Reserve’s account tier is shared across every organization using this endpoint, and a 429 from Inworld is relayed as Inworld sends it (a plain-text Rate limit exceeded, no Retry-After). Back off exponentially.
• One Inworld workspace, Inworld’s data handling. Text, audio uploads and reference audio reach Inworld under AI Reserve’s workspace and Inworld’s terms. See the provider data-handling page.
• HTTP only. The gateway relays HTTP requests. Inworld’s WebSocket endpoints (/v1/tts/synthesize:websocket, /stt/v1/transcribe:streamBidirectional) and the Realtime API are not upgraded through the gateway; POST /tts/v1/voice:stream streams its chunks as they are synthesized.