AI and media

AI agents that use AssemblyAI

UtilitySpaces gives an AI agent scoped access to AssemblyAI through its own encrypted connection, not your password. The agent can call 4 named AssemblyAI tools, and the 2 that write wait for a person's approval unless an admin has set the connection to run without asking. Every call is written to a hash-chained audit log with its arguments and its result.

What an agent can do in AssemblyAI

Transcribe audio with AssemblyAI and run LeMUR tasks over finished transcripts. An agent calls these by name, and matching is exact.

Every tool a AssemblyAI connection exposes, and whether it writes, which waits for approval by default
Tool	What it does	Waits for approval by default
Create transcript	Queue a transcription for audio at a public URL (billed call). Poll get_transcript until status is completed or error.	Yes — it writes
Get transcript	Get a transcript's status and text.	No — read only
List transcripts	List transcripts on the account.	No — read only
LeMUR task	Run a custom LLM task over finished transcripts (billed call).	Yes — it writes

2 read tools, 2 write tools. Generated from the connector catalogue the product runs on, so it cannot list a tool that does not exist.

What teams hand an agent in AssemblyAI

Teams with recordings hand an agent the transcript pipeline in AssemblyAI: Create transcript queues audio at a public URL, Get transcript returns the status and the text, List transcripts shows the account's history, and LeMUR task runs a custom LLM pass over finished transcripts. The queue and the LLM pass are billed writes that wait for a person unless the connection is set to run without asking.

Queue a call recording for transcription and post the text into the thread when it completes (billed; after a person approves it)
Summarise or extract action items from finished transcripts with a LeMUR task (billed; after a person approves it)
Find last week's transcripts when someone needs the exact wording from a call.

Before you let it write, or keep out: The audio must sit at a publicly reachable URL, which is itself a decision about where a recording lives. Settle that before approving the first run -- that link is the thing being shared with a processor.

What waits for a person

Reads run on their own. These do not — each one waits in Approvals for an owner or admin unless an admin has set this connection to run writes without asking, and every call toAssemblyAI, approved, rejected or unattended, is logged.

Create transcript POST
LeMUR task POST

What connecting AssemblyAI takes

AssemblyAI uses an API key you create in AssemblyAI and paste in once. A workspace admin sets the connection up; the fields are:

API Key

Credentials are encrypted and bound to your workspace, never read back, and every outbound call passes one guarded fetch — the connector security posture sets out exactly how, and the security page covers the platform around it.

Where AssemblyAI fits

Give an agent AssemblyAI work by writing a message in the inbox, or put its tools in a scheduled flow. What the run cost is on the cost breakdown.

Other ai and media integrations: AnythingLLM, D-ID, Deepgram. Or see every application agents can connect to.

See it doing your actual work

Open a demo workspace, connect one app, and give an agent a real job. No card, no sales call.

Try the demo See pricing

We reply to every message within one business day.