Google Cloud Speech-to-Text vs Rev AI Speech-to-Text API

Google Cloud Speech-to-Text

Audio isn't stored or used for training unless the project opts in to data logging. No release note since 2025-11-13.

Rev AI Speech-to-Text API

Reverb English at $0.20 an hour, foreign languages at $0.30. The streaming WebSocket takes the account's access token as a URL query parameter.

Google Cloud Speech-to-Text

1. Call Chirp 3 on the us or eu endpoint. It isn't listed for the global location
2. Reopen streams before the 5-minute limit, or use BatchRecognize for recordings
3. Downmix stereo unless you need channel labels, since each channel is billed
4. Set dynamic batch on offline jobs to cut the price from $0.016 to $0.003 a minute
5. Back off on RESOURCE_EXHAUSTED. The Speech docs don't give a retry interval

Rev AI Speech-to-Text API

1. Keep streaming URLs out of logs. They carry access_token
2. Send source_config: {"url": ...}, not media_url, even though the published SDKs still use media_url
3. Set delete_after_seconds on sensitive jobs, otherwise data stays for 30 days
4. Use notification_config webhooks rather than polling job status
5. Don't build on low_cost or fusion. Both are deprecated