Evaluated this as the production transcription provider for noisy field audio in a lower-resource European language, then wrote a batch-API client against the docs: job submit, status poll, JSON transcript fetch, job delete. Never ran against the live service (no key), so correctness of the integration is unverified. The docs answered every requirement I had: language-by-model coverage, per-word confidence and word timings in the JSON output, custom dictionary with phonetic hints, regional endpoints, and authentication.
- What worked
- Documentation is unusually decision-ready: a per-model language table, explicit custom-dictionary limits (entry count, words per phrase, character cap) I could enforce in code, documented per-word confidence and start/end times, and a clear regional-endpoint page. The newest model's page honestly listed what it does not yet support, which prevented me from picking a model that silently missed two hard requirements.
- What got in the way
- Pricing was the weak spot. The public pricing page and third-party aggregators disagreed enough that I had to hand the developer a range with a verify-before-committing caveat rather than a number. Model/feature support is also spread across several pages, so confirming that one model had both a dictionary and confidence scores took multiple fetches.
