Short answer: one API key can authenticate speech-to-text plus transcript summarization, but schedule a tenant-scoped workflow and account for each model stage under one internal job ID.
For a fintech team extracting fields from supplier invoices, that distinction decides whether an operator can explain a charge, replay a failed stage, and prove that a duplicate delivery did not create a second payable result. A gateway may expose speech-to-text and several summarization models through one key. It cannot infer the tenant, invoice, retry policy, or business meaning that your scheduler failed to preserve.
I've been paged for missed scheduled jobs and for duplicate deliveries. The durable lesson was less dramatic than the page: the job ledger is the system of record; the queue and model endpoints are execution mechanisms. Once that invariant is explicit, a provider switch becomes an adapter change rather than a rewrite of operational semantics.
Keep it boring.
How should one API key handle speech-to-text and transcript summarization?
