AssemblyAI Spend and Usage Control

Overview

Control spend with dated prices and measured workload usage. Keep quality, privacy, reliability, credentials, and destructive state as separate gates.

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 billing follows successfully processed audio duration and selected models or add-ons; published guidance says failed transcripts are not charged. Streaming follows session duration, so termination matters. LLM Gateway has separate economics. Prices are time-sensitive and belong in reviewed billing inputs.

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.