Skip to content

OpenAI: Whisper Large V3 provider comparison

openai/whisper-large-v3

Whisper Large V3 is OpenAI's open-source automatic speech recognition model offering both audio transcription and translation. It supports 99+ languages and accepts common audio formats including mp3, mp4, wav, webm,...

Endpoints:
2
Context:
0
Input:
audio
Output:
transcription

Visual comparison

Endpoint pricing chart

Compare published endpoint pricing visually.

Effective price by endpoint

USD per unit for prompt. Lower is better.

Only directly comparable published units are charted.

Server-rendered comparison

Provider endpoints

Prices are shown only in the units published by OpenRouter; cross-unit rankings are intentionally omitted. Missing speed data never removes an endpoint.

Endpoint comparison for OpenAI: Whisper Large V3
Provider / routeCurrent pricingSpeed measurementsEndpoint details
Provider / route
Togethertogether
Current pricing
  • $0.0015 per unit (prompt)
  • Free per unit (completion)
Speed measurements
500-token response
Not applicable
Response starts
Insufficient recent data
Output speed
Insufficient recent data
Endpoint details
Uptime (30 min)
100.00%
Context
0
Model format
unknown
Max output
N/a
10 parameters

frequency_penalty, logit_bias, max_tokens, min_p, presence_penalty, repetition_penalty, stop, temperature, top_k, top_p

Provider / route
Groqgroq
Current pricing
  • $0.111 per unit (prompt)
  • Free per unit (completion)
Speed measurements
500-token response
Not applicable
Response starts
Insufficient recent data
Output speed
Insufficient recent data
Endpoint details
Uptime (30 min)
100.00%
Context
0
Model format
unknown
Max output
N/a
6 parameters

max_tokens, response_format, seed, stop, temperature, top_p

Endpoint data fetched .

Whisper Large V3 deployment guide

How to choose a Whisper Large V3 inference provider

Whisper Large V3 is indexed here as a transcription model by OpenAI, with 2 provider endpoints from Together, Groq. The comparison preserves each exact OpenRouter routing tag so pricing and performance observations can be connected to the route an application would actually request.

Match the endpoint to the workload

The model publishes a 0-token context window. It accepts audio input and returns transcription output. 12 distinct supported parameters appear across the listed routes. Confirm limits on the specific endpoint rather than assuming every host exposes the same configuration.

Compare transcription billing units directly

At least one unit is published consistently across the listed endpoints, allowing a direct price chart for prompt. Other charges remain in the table using OpenRouter’s exact billing labels.

Verify route format and availability

Published endpoint formats include unknown. Availability, rate limits, and regional support can change independently of catalog pricing, so confirm the selected routing tag before production deployment.