LiveKit through Squiid

What LiveKit is

LiveKit is open-source WebRTC infrastructure with a hosted cloud. Rooms carry audio, video and data tracks between participants with an SFU handling routing, and client SDKs exist for web, mobile and server languages. The Agents framework is the piece that matters for AI products: it lets a program join a room as a participant, receive the audio stream, run speech to text, a model and text to speech, and publish the reply back with the turn-taking, interruption handling and latency management already solved.

That is the difference between a voice demo and a voice product. In an AI-coded app LiveKit is how a support agent, a language tutor, an interview practice tool or an in-app assistant actually talks to someone in real time, and it connects to telephony so the same agent can answer a phone call. It usually sits alongside a fast model provider, a speech to text service and a text to speech service. Egress and ingest options also cover recording a session or piping a stream in, which is how transcripts and replays are produced.

Why connect it through Squiid

That is also three or four more keys. LiveKit is on the Squiid roadmap, and when it lands Squiid will provision the project, hold the API key and secret, and route calls through https://api.squiid.io/v1/livekit/... with Authorization: Bearer $SQUIID_API_KEY, with SDKs working by base URL swap (gateway convention). Participant minutes and plan cost will bill at LiveKit's listed price on one invoice, next to the model and speech services the same agent uses.

• One account, one key, one bill, one dashboard. LiveKit sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the LiveKit credentials. Your code carries SQUIID_API_KEY, so LIVEKIT_URL, LIVEKIT_API_KEY, LIVEKIT_API_SECRET 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 LiveKit 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

• A provisioned LiveKit project with secrets held by Squiid
• WebRTC rooms for audio, video and data
• Agents framework for realtime voice AI
• Telephony integration for phone-based agents
• LiveKit list pricing, no markup

How to connect LiveKit

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 LIVEKIT_URL, LIVEKIT_API_KEY, LIVEKIT_API_SECRET
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

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

Pricing through Squiid

LiveKit Cloud charges by participant minutes and bandwidth on plan tiers, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of LiveKit usage, with no markup and no per-request margin.

LiveKit 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 LiveKit 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

Export: channels, keys and delivery configuration are re-created in your own LiveKit account from the documented setup. Squiid never owns your code, your schema or your domain, and the gateway speaks LiveKit'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

LiveKit 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 LiveKit 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.