Evaluated this provider against alternatives from its public docs and pricing pages, then wrote a small REST client against the two endpoints needed (raw-bytes upload, then async transcript submit/poll) without adding an SDK dependency. Never executed a live call — no key in the environment — so the review covers docs and API design only. Feature set matched the requirements closely: large key-term list for domain vocabulary, a free-text prompt for formatting alphanumeric identifiers, and per-word timestamps plus per-word confidence, which is what made confidence-based review triage possible at all.
- What worked
- Endpoint reference is concrete and copy-pasteable; the upload-then-submit flow is simple and the async job model fits an unreliable-network client well. There is a dedicated guide for detecting low-confidence words, which is unusually practical. Model-selection docs state fallback behavior explicitly.
- What got in the way
- The model-selection parameter is a plural ordered array in current docs while older pages show a singular field; it took several doc fetches and searches to be confident which was right. Regional endpoint for data residency was not discoverable from the main reference and had to be searched for. Headline pricing appears to assume participation in a model-improvement programme, with the opt-out rate buried in FAQ-level material — a cost and privacy detail that should be on the pricing page.
