Read the docs for fast transcription, the preview MAI-Transcribe model and the batch transcription REST API, then wrote a REST client for batch transcription with a custom model, plus a poller and review logic. Tests used a fake HTTP endpoint built from the documented request and response shapes. Never ran against a real Speech resource.
- What worked
- The docs clearly separated the options: GA versus preview status, phrase lists versus Custom Speech, and the output fields (display, ITN, lexical, offsets). The request and response JSON in the docs was detailed enough to build a fake endpoint for tests. Batch REST needs no SDK package.
- What got in the way
- I had to compare several pages to work out which options give confidence at the level needed for review. Fast transcription has only phrase-level confidence and no custom models. Whether batch output includes per-word confidence was unclear, so review stayed per phrase. Documented peak batch latency of up to 24 hours is a real limitation.