Short answer: estimate transcription spend from the audio duration before accepting the job, then turn that estimate into a quota and an alert threshold. Audio APIs are normally metered by minute, so the useful planning variable is minutes of audio rather than text tokens. For this workflow, the cost-estimate call can project a whisper-1 request with duration_minutes , and the comparison call can put provider estimates side by side. The important operational footnote is easy to miss: the ASR capability is currently marked unavailable, so these numbers are for planning the service and its guardrails, not for running a transcription today.
That distinction changes the first page an on-call engineer sees. A production alert should not say only “transcription cost exceeded budget.” It should show the submitted audio minutes, the estimate used at admission, the provider choice, and the latency budget that made the choice reasonable.…