TL;DR: Do not discover a speech model by sending it a customer recording. Keep a small capability registry, check that registry immediately before transcription, and still treat the transcription call as fallible. The check decides whether to proceed, queue, or use a declared fallback; it does not prove that the next request will succeed.

For a support system answering from a private knowledge base, the real contract is structured output correctness. A transcript that looks readable but loses a negation, speaker turn, or ticket identifier can produce a confident answer from the wrong evidence. The availability gate is therefore one input to a larger decision, not a green light to skip validation.

What is the bill actually made of?

Count one recording as four operational units: an upload, a transcription attempt, a validation pass, and a retention decision. A retry adds another transcription attempt and often another validation pass.…