AssemblyAI Capacity and Retry Control

Overview

Control capacity with explicit account limits, queues, and retry budgets. Keep data, credentials, spend, and replay decisions separately governed.

Prerequisites

• The target repository or integration path and the requested operator outcome.
• The AssemblyAI project, environment, region, data classification, and accountable owner.
• Current first-party documentation plus credentials only for a narrowly approved live check.

Current Contract

AssemblyAI documents 20,000 API requests per five minutes plus operation-specific concurrency limits. Limits apply at account level; project keys mirror capacity rather than multiply it. Actual concurrency and autoscaling are account-specific, so use current dashboard and documentation evidence.

Authentication

For live work, inject ASSEMBLYAI_API_KEY from an approved secret manager and send the raw value only in the AssemblyAI Authorization header to the configured first-party host. Never print, commit, place in a URL, or expose it to an untrusted client. Callback secrets and temporary streaming tokens are separate credentials.