Transcript pricing that stays predictable.

Every accepted transcript request uses one monthly unit. Job polling is included. Annual plans provide twelve months for the price of ten.

Free

For testing an integration or a small personal project.

€0/ month

No payment required

50 requests per month

  • 15 generated minutes
  • Native captions
  • Timestamped JSON
  • 1 active API key
Start free

Launch

For products moving from prototype to regular usage.

€12/ month

Billed monthly

3,000 requests per month

  • Native captions
  • AI fallback
  • Shared transcript cache
  • Multiple API keys
Get started

Business

For teams processing video at higher volume.

€249/ month

Billed monthly

300,000 requests per month

  • Native captions
  • AI fallback
  • Request logs
  • Multiple API keys
Get started

Choose a plan from your actual workload

Free: test your videos, output format and integration with 50 monthly requests. Move to a paid plan when recurring usage exceeds that allowance.

Launch: up to 3,000 requests per month. For example, 50 videos each working day uses about 1,100 requests over 22 days, before retries and repeated reads.

Scale: up to 30,000 requests per month. A workload of 500 videos each working day uses about 11,000 requests over 22 days.

Business: up to 300,000 requests per month. Plan for peaks and repeated reads as well as the number of unique videos.

These are request-volume examples, not generated-minute allowances or throughput guarantees. Start with the free Inspector, then check your workspace usage before choosing a plan.

How usage is counted

One accepted transcript request reserves one unit, whether the result is native, generated or served from cache.

Polling an asynchronous job does not reserve another unit. Usage resets monthly, including on annual subscriptions.

Prices exclude VAT. Videos and requests remain subject to the documented technical limits.