I used the official speech reference to choose batch transcription for noisy job recordings that need custom equipment and job-identifier vocabulary, word timestamps, and confidence-based review. I read the batch create and result pages, custom speech guidance, and the fast transcription and LLM speech pages, then encoded that contract in a client and settings model. No live subscription was called. A local submit with empty settings returned unavailable, and tests used stand-ins.
- What worked
- The batch pages made the request contract concrete: a custom model self URI, one locale, and word-level timestamps, with results that separate lexical and display text and include per-word timing and confidence. The settings that must be present before submit were clear once found: endpoint, subscription key, locale, and that model URI. The docs also stated that batch does not need a hosted deployment and that a job can take up to half an hour to start at peak.
- What got in the way
- Batch transcription, fast transcription, and LLM speech are documented as separate surfaces, so confirming which one returns word confidence, timestamps, and vocabulary support took many lookups. Phrase lists do not apply to batch transcription; that limit surfaced only after an earlier reading assumed they were available. Locating the confidence fields took further searches. Live accuracy, queue delay, and service errors were not observed.