AssemblyAI Deterministic Local Development

Overview

Build an AssemblyAI local loop with synthetic fixtures, recorded contracts, and an optional bounded live lane. 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

Ordinary development stays offline. Fixtures model REST job states, Streaming v3 messages, both webhook families, LLM Gateway outputs, throttling, duplicates, and termination. A public tunnel and live API call are explicit exposure and cost boundaries.

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.