Skip to main content

Overview

Gemini 3.5 Transcribe is a speech-to-text model for recorded audio, not a chat model and not a live streaming session. On Kyma it is served through the same OpenAI-compatible transcription endpoint as the other STT SKUs: multipart file or JSON audio_url, response { text, language?, duration? } with json or text — it does not return per-segment timestamps. It accepts up to about an hour of audio per request. Billing is per second of audio at the per-minute rate (10-second minimum per request), not per token. This SKU is opt-in by id. This is file transcription only. It does not answer questions about how the audio sounds, and it is not the live streaming companion.

Specs

Pricing

Billed per second of audio, with a 10-second minimum per request. Every request reports its exact cost in usage.cost; the full media price list is on Pricing.

Use this when

  • Meeting and call transcripts — Turn recorded meetings and call logs into plain text for search and notes.
  • Multilingual dictation — Transcribe speech across many languages without swapping SKUs.
  • Captions from a file — Produce a transcript from an uploaded clip, then format it client-side.
  • Voice-agent offline pass — Batch-transcribe recorded user audio before a later language-model step.

Not ideal for

Do not use this for live bidirectional speech or for audio-scene questions (tone, music, SFX). Those are different endpoints. It returns a plain transcript with no per-segment timestamps: verbose_json, srt and vtt are refused on this SKU (400 segments_unsupported) — use whisper-v3-turbo for timestamps.

Pick something else when

Example

Agent query example

Ask the API which models fit, instead of hardcoding an id:

FAQ

How do I call this model? Pin gemini-3.5-transcribe by id on POST /v1/audio/transcriptions. How is this billed? Per second of audio at the per-minute rate, with a 10-second minimum per request. The generated Pricing table on this page is the live rate. Is this a chat completions model? No. Send audio to POST /v1/audio/transcriptions. A chat request is the wrong surface.