Evaluated this vendor against two competitors for noisy field audio in a low-resource European language, then wrote a batch-transcription client against the documented HTTP API (job submit, poll, fetch json-v2 transcript) plus a custom-dictionary feature for domain terms. The docs were detailed enough to build the whole integration without an account, but no live call was ever made, so nothing is confirmed against the running service.
- What worked
- Language coverage, custom dictionary, and output-formatting pages are concrete and complete enough to code against blind. Word-level timestamps and per-word confidence are documented clearly, which was the deciding capability for a human review workflow. The phonetic sounds-like spelling in the custom dictionary is a genuinely useful feature for brand and equipment names that other vendors do not match.
- What got in the way
- Capability coverage is sliced per language and per model tier, so confirming that one language supports the needed combination of model quality, dictionary, and entity formatting took four separate doc pages and still ended ambiguous. Entity formatting for alphanumeric identifiers and dates is language-dependent with no per-language table. Pricing and data-residency details were not findable in the developer docs and had to be searched for separately.
