AssemblyAI Reversible Deployment

Overview

Deploy AssemblyAI workers, Streaming v3 token services, and authenticated callback receivers with reversible controls. Treat live audio, transcript content, credentials, spend, and destructive state as separately governed 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

REST workers need HTTPS egress to the chosen regional host. Streaming needs WebSocket support and shutdown cleanup. Token issuance stays on a trusted backend. Callback ingress uses TLS, authentication, fast durable enqueue, deduplication, and dead-letter handling.

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.