Rev AI
AI · AI
Speech-to-text jobs, captions, translations, and summaries on their own key.
Connecting Rev AI in practice
Rev AI accepts far more transcription work than it starts: 10,000 submissions per 10 minutes but only 500 transcriptions processed in the same window, with everything over that accepted and queued until the next interval. Jobs and their media are deleted after at most 30 days, and HIPAA use means a signed BAA plus a brand-new account on which media_url and human transcription stop being available.
Scopes that draw scrutiny
Access token (Bearer)One account-level token with no scopes: it submits jobs, reads every transcript on the account and deletes them. Rev AI supports rotating it and deleting the old one, which is the only containment.source_config authorization headersTo fetch a protected media URL, you hand Rev AI the authorization headers for your own storage — so a third party briefly holds credentials to your bucket.access_token as a WebSocket query parameterThe streaming endpoint takes the token in the wss:// URL, which is the form most likely to be captured in proxy and client logs.
Rate limits
- Asynchronous Speech-to-Text, per user per endpoint: 10,000 transcription requests submitted every 10 minutes.
- 500 transcriptions processed every 10 minutes; submissions beyond that are accepted but queued until the next interval.
- Maximum audio duration of 17 hours per job.
- multipart/form-data uploads to /jobs: concurrency limit of 5 and 2 GB per request.
- Uploads via source_config or the dashboard: 5 TB file size limit.
Who has to approve
HIPAA processing is enabled by Rev AI, not self-service: the account owner signs a Business Associate Agreement and an updated MSA, then creates a new Rev AI account specifically for HIPAA-compliant orders and sends it to their sales contact for Rev AI to enable.
Worth knowing
- Jobs live at most 30 days and then all associated data is irretrievable; delete_after_seconds on a job overrides the account-level auto-delete, and a GET on a deleted job returns 404.
- Pre-signed source URLs need an expiry of at least 2 hours for Rev AI to fetch them, and a resubmission needs a freshly signed URL.
- On a HIPAA-enabled account the media_url option is unsupported (use source_config), transcriber=human is unavailable, and RTMP streaming is not supported.
- Rev AI warns not to put PHI in filenames or URLs, because it accepts no liability for PHI exposed that way.
- Stereo files with inverted polarity cancel to silence when Rev AI mixes to mono, producing an empty transcript rather than an error.
Checked against File submission and limits (2026-09-29), Security and privacy (2026-09-29), HIPAA compliance (2026-09-29), Streaming API overview (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Rev AI behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.