Chose this hosted async model after comparing alternatives, then implemented upload plus transcribe via HTTP instead of the official SDK. Public docs covered the model id, word timestamps, confidence scores, keyterm limits, and formatting well enough to ship a mocked client and review flow. The live service was never called.
- What worked
- Docs made the async contract clear: raw upload, model selection, word-level start/end and confidence, and a large keyterm list for names and identifiers. That was enough to skip the SDK, inject fetch for tests, and map low-confidence spans into a review step.
- What got in the way
- Async jobs cannot combine a contextual prompt with keyterms, so domain boosting had to be keyterms-only. Upload body typing against fetch was awkward. Live transcription, auth, and latency were never observed.
