Muse Voice Transcribe API: Pricing, Documentation

Authentication

All requests require an API key passed via header.

Webhook (Optional)

Instead of polling, you can receive a Webhook callback when the request reaches a terminal state. Provide a Webhook URL via header on the submit request.

Example: enable Webhook

curl -X POST 'https://gateway.pixazo.ai/muse-voice-transcribe/v1/speech-to-text' \
  -H 'Content-Type: application/json' \
  -H 'Ocp-Apim-Subscription-Key: YOUR_SUBSCRIPTION_KEY' \
  -H 'X-Webhook-URL: https://your-server.com/webhook' \
  --data-raw '{"audio_url": "https://example.com/interview.wav", "audio_encoding": "WAV", "mode": "DIARIZATION"}'

Callback Payload (success)

{
  "request_id": "muse-voice-transcribe_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "COMPLETED",
  "model_id": "muse-voice-transcribe",
  "output": {
    "media_url": "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/{request_id}/output.json",
    "media_type": "application/json"
  },
  "created_at": "2026-09-04T11:18:56.746Z",
  "completed_at": "2026-09-04T11:19:32.000Z"
}

Failure callback shape

{
  "request_id": "muse-voice-transcribe_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "ERROR",
  "model_id": "muse-voice-transcribe",
  "error": "Description of the failure"
}

Delivery semantics

• terminal mode: one Webhook callback when the request is COMPLETED or ERROR.
• sync mode: a Webhook callback on each status change.
• Callbacks are idempotent on request_id — de-duplicate on it.
• Respond 200 within a few seconds; the Webhook endpoint must be HTTPS.

Request Parameters

Audio requirements

• Audio must be mono, signed 16-bit little-endian PCM, at 16 kHz or 24 kHz. Stereo and 8-bit audio fail once the file is read, reported as status: "ERROR". Audio is not converted for you.
• At most 10 minutes per request, and at most 32 MB. Split longer recordings and submit each part.
• audio_encoding must match the bytes at audio_url. A declaration that disagrees with the file — WAV for headerless audio, or a PCM_* value for a RIFF/WAVE file — fails once the file is read, reported as status: "ERROR".
• audio_url must be an https URL and publicly reachable.
• Cost scales with the length of the audio; the current rate is in the pricing panel on this page.

Choosing a mode

An empty turns[] under PUSH_TO_TALK is expected behaviour, not a failure.

Transcript Format

The completed request returns output.media_url, a JSON file containing the transcript. Fetch that URL to read the result.

{
  "request_id": "50ad7353-7814-4a9f-a059-1465e86c12dd",
  "transcript": "Good morning everyone. Thanks for joining. Let's start with the quarterly numbers.",
  "turns": [
    {
      "turnId": 0,
      "startMs": 60,
      "endMs": 2180,
      "transcript": "Good morning everyone. Thanks for joining.",
      "speaker": "A"
    },
    {
      "turnId": 1,
      "startMs": 2240,
      "endMs": 5010,
      "transcript": "Let's start with the quarterly numbers.",
      "speaker": "B"
    }
  ],
  "audio_duration_ms": 5010,
  "mode": "DIARIZATION"
}

Speech that is silent or below the confidence floor transcribes to an empty string rather than failing. That is a successful, billable request.

Request Headers

Response Handling

Only what can be judged from the request body itself is rejected synchronously. Everything that needs the audio to be fetched and read is reported through the status endpoint instead, as status: "ERROR". Failed requests are not billed — the hold is released in full.

Note the two audio_encoding failures are different checks at different moments: an unrecognised value is caught before the request is accepted, while a value that disagrees with the file can only be caught once the audio has been downloaded.

Retrieving Results

Poll the status endpoint with the request_id from the submit response until status is COMPLETED (or FAILED/ERROR), then fetch output.media_url for the transcript.

curl 'https://gateway.pixazo.ai/v2/requests/status/muse-voice-transcribe_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' \
  -H 'Ocp-Apim-Subscription-Key: YOUR_SUBSCRIPTION_KEY'

Completed response

{
  "request_id": "muse-voice-transcribe_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "COMPLETED",
  "model_id": "muse-voice-transcribe",
  "output": {
    "media_url": "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/{request_id}/output.json",
    "media_type": "application/json"
  },
  "created_at": "2026-09-04T11:18:56.746Z",
  "completed_at": "2026-09-04T11:19:32.000Z"
}

Response Fields

Status Values & Flow

QUEUED → PROCESSING → COMPLETED (success) or FAILED/ERROR (failure).

How billing is measured

Billing is measured on the length of the audio you submit, rounded up to the next whole minute — not on the size of the transcript, and not on how long transcription takes. A hold is placed when the request is submitted, because the audio length is not known until the file has been read; the hold is reduced to the real cost once the duration is known, and released in full if the request fails.

The current rate is shown in the pricing panel on this page.