AssemblyAI Production Readiness Gate

Overview

Gate production on evidence across the entire AssemblyAI lifecycle. Treat data, credentials, spend, deployment, rollback, and deletion as separately owned boundaries.

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

Production requires current REST and Streaming v3 contracts, explicit models, protected keys and tokens, authenticated idempotent callbacks, bounded retries, explicit streaming termination, deletion propagation, cost controls, monitoring, and tested rollback. One happy-path transcript is insufficient.

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.