API Reference
Gemini Live WebSocket
Gemini Live WebSocket
Preview guide
Paste into an AI assistant to help with integration. Documentation and examples only; no real credentials.
Updated · Reviewed
Endpoint and authentication
GET https://api.tu-zi.com/v1beta/live?model={model}
Transport: websocket
Use an inference API key. Examples contain placeholders; read credentials from environment variables.
Authorization: Bearer YOUR_API_KEY
Minimal request example
{
"setup": {
"model": "models/YOUR_MODEL",
"generationConfig": {
"responseModalities": [
"AUDIO"
]
}
}
}
Before running
Replace https://api.tu-zi.com with this site origin (do not append /v1 twice), and YOUR_MODEL with the exact marketplace model ID. Install requests for Python; use Node.js 20+ and save JavaScript as .mjs. WebSocket samples list their own dependencies.
Create an inference key on the site and set API_KEY in the environment; replace YOUR_API_KEY in cURL. Prepare local input.png/input.wav files for upload examples.
Start with a minimal request, then read the result using the response fields below. For async APIs, a returned task ID requires polling; acceptance does not mean generation has finished.
Constraints
This page describes the base protocol. Use the selected model quick start for supported fields, enums, limits and asynchronous behavior. Replace YOUR_MODEL. Form initial values are not upstream defaults.
Query parameters
| Field | Type | Required | Description / constraints |
|---|---|---|---|
| model | string | Yes | Selected model identifier. Example: YOUR_MODEL |
Response fields
| Field | Type | Description / constraints |
|---|---|---|
| setupComplete | object | Setup-complete event. |
| serverContent.modelTurn.parts[] | object | Model audio or other content parts. |
| serverContent.turnComplete | boolean | Turn completion. |
Illustrative response; some endpoints show essential fields only. Optional fields may be absent.
{
"setupComplete": {}
}
Streaming
Connect with wss, send setup, then realtimeInput or clientContent. Handle audio/transcription events, turnComplete, interrupted and errors. The example sends one request after setupComplete and requires model output followed by turnComplete. Errors, timeout, premature close or interrupted mean incomplete; do not automatically resubmit.
Errors and retries
Check HTTP status and protocol-specific errors; do not mix error formats across protocols. For 401/403 check credentials and permissions, for 429 back off, and for 5xx check gateway/upstream status. Error bodies may contain error/message/code depending on the protocol.
Use bounded exponential backoff for reads. Do not blindly retry task creation, generation, or key mutations, to avoid duplicate billing or execution.
兔子API