AssemblyAI Typed Adapter Boundary

Overview

Design a narrow application-owned boundary around the current SDK. Keep data, credentials, region, retries, spend, and destructive state 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

Pre-recorded jobs, Streaming v3 sessions, temporary-token issuance, webhooks, and LLM Gateway requests have different lifecycles. Keep vendor objects behind a narrow application-owned port. New code must not expose legacy LeMUR methods or Streaming v2 service names.

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.