Omixa API Docs

Chirp 2 Transcription

Developer documentation

Chirp 2 Transcription

Google Cloud Speech-to-Text Chirp 2 for transcription and supported speech translation workflows.

Model Reference

Audio and speech models

Text-to-speech, GPT audio chat, realtime sessions, transcription-oriented catalog rows, and voice settings. Endpoint: https://omixa.cloud/api/v1/audio

Chirp 2 Transcription

chirp-2

Google Cloud Speech-to-Text Chirp 2 for transcription and supported speech translation workflows.

声音的
Audio per minute $0.016000
Minimum hold $0.010000
Integration reference

Connect Chirp 2 Transcription

Use Omixa's unified endpoint and your workspace API key. Provider routing, billing, failover, and usage records are handled by Omixa.

POST https://omixa.cloud/api/v1/audio
  • Provider: google
  • Endpoint type: google_cloud_speech_to_text
Request schema

Request fields

Only send options supported by this model. Required fields and accepted values are listed below.

Field 类型 Required Accepted values 描述
model string Yes chirp-2 Use `chirp-2`. Omixa resolves the active provider route and failover key automatically.
task string No transcription, translation Speech workflow supported by this model.
file_data base64|string Yes Any valid value Source speech audio as raw base64 or an audio data URL.
filename string Yes Any valid value Original filename including a supported audio extension.
mime_type string Yes Any valid value Audio MIME type such as `audio/wav`, `audio/mpeg`, or `audio/flac`.
language string No Any valid value Source BCP-47 language code. Chirp 3 can use `auto` for automatic language recognition.
response_format string No json Normalized transcript response format.
target_language string No en-US, ar-EG, fr-FR, ... Target BCP-47 language for Chirp 2 speech translation.
Ready to send

Payload and response

Start with this model-safe payload and expect the normalized Omixa response shape shown beside it.

Example JSON payload
{
    "model": "chirp-2",
    "task": "transcription",
    "file_data": "data:audio/wav;base64,<base64-audio>",
    "filename": "speech.wav",
    "mime_type": "audio/wav",
    "language": "en-US",
    "response_format": "json"
}
Response shape
{
    "object": "audio.transcription",
    "text": "Transcribed speech...",
    "segments": [],
    "words": [],
    "usage": {
        "estimated_audio_minutes": "0.100000"
    }
}
Language examples

Copy-ready integration code

Replace the example API key with a workspace key and keep model-specific fields unchanged unless the table above marks them optional.

curl -X POST https://omixa.cloud/api/v1/audio \
  -H "Authorization: Bearer omx_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "chirp-2",
    "task": "transcription",
    "file_data": "data:audio/wav;base64,<base64-audio>",
    "filename": "speech.wav",
    "mime_type": "audio/wav",
    "language": "en-US",
    "response_format": "json"
}'
Production checklist

Operational notes

  • Authenticate with `Authorization: Bearer omx_live_xxx`.
  • Omixa handles provider keys, routing, billing, failover, and usage recording behind this endpoint.
  • Google Vertex requests use active Vertex accounts configured by the admin; Omixa retries the next healthy account when a route fails before output starts.
Copied Markdown