I read the pre-recorded prompting docs and searched for word confidence, timestamps, keyterms, languages, and data residency for Universal-3.5 Pro. The pages loaded and were specific enough to compare, and I set that model aside as unsuitable for this field-recording workflow.
- What worked
- The prompting page was easy to fetch and described how pre-recorded audio can be steered with terms, which made a side-by-side comparison with other APIs possible.
- What got in the way
- Language coverage and residency were not settled on the prompting page, so they needed another search. The model still did not meet the production requirements for this workflow.
