AssemblyAI through Squiid

What AssemblyAI is

AssemblyAI is a speech to text API whose distinguishing feature is what it returns besides the words. Universal transcription handles files and real-time streams, and the audio intelligence endpoints layer on auto chapters, summarisation, topic detection, sentiment analysis, entity detection and PII redaction that can blank sensitive spans in both the transcript and the audio. LeMUR lets you run a prompt over one or many transcripts without building your own retrieval step. Word-level timestamps make it straightforward to link a summary back to the exact second of audio it came from, which is what turns a transcript into a usable interface.

For a product built by coding agents that is a lot of features you do not have to write. A call review tool gets chapters and a summary from the same request that produced the transcript, and a healthcare or fintech app gets redaction without a separate scrubbing pass. The usual shape is an upload to storage, a transcription job, a webhook when it completes, and rows written to your database. Pricing is per hour of audio with extras billed per feature, so turning on four intelligence models multiplies the cost of the same file.

Why connect it through Squiid

AssemblyAI is on the Squiid roadmap. When it lands, requests will go to https://api.squiid.io/v1/assemblyai/... with Authorization: Bearer $SQUIID_API_KEY, the official SDKs will work by pointing their base URL at the gateway (gateway convention), and audio minutes plus any intelligence features will meter against the same prepaid credits at AssemblyAI's list price. Squiid will hold the upstream key, so rotating one credential in the dashboard cuts off every agent, deployment and teammate at once, and the spend will appear on the single monthly invoice with your other services.

• One account, one key, one bill, one dashboard. AssemblyAI sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the AssemblyAI credentials. Your code carries SQUIID_API_KEY, so ASSEMBLYAI_API_KEY, ASSEMBLYAI_BASE_URL never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what AssemblyAI costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• File and streaming transcription through one key
• Summaries, chapters and topic detection included
• PII redaction for regulated workloads
• Per-minute metering against prepaid credits
• AssemblyAI list pricing, no markup

How to connect AssemblyAI

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces ASSEMBLYAI_API_KEY, ASSEMBLYAI_BASE_URL
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/assemblyai/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

AssemblyAI charges per hour of audio transcribed with additional per-hour rates for audio intelligence features, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of AssemblyAI usage, with no markup and no per-request margin.

AssemblyAI has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so AssemblyAI usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Nothing to move: AssemblyAI is usage-metered, so leaving means creating your own AssemblyAI key and pointing the client at it. Squiid never owns your code, your schema or your domain, and the gateway speaks AssemblyAI's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

AssemblyAI through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on AssemblyAI usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.