Mux through Squiid

What Mux is

Mux is video infrastructure sold as an API. You create an asset from a URL or a direct upload, and Mux transcodes it into adaptive bitrate renditions, gives you a playback id for HLS delivery, generates thumbnails and animated previews, and reports real viewer quality metrics through Mux Data. Live streaming with low-latency options, signed playback tokens for paid content, and automatic captions are part of the same product. Webhooks report when an asset is ready, which is the signal your application uses to enable playback in the interface.

For AI-coded apps this is the difference between a video feature that works and one that buffers. Storing an MP4 in a bucket and putting it in a video tag ignores everything that makes video viable at scale: multiple renditions, bandwidth adaptation, seeking, mobile compatibility and playback analytics. Course platforms, creator tools, recorded demos and anything with user-uploaded video are the usual cases. Mux Data also works with other players, so playback quality can be measured even for video you deliver from elsewhere.

Why connect it through Squiid

Mux is on the Squiid roadmap. When it is connected, Squiid will provision the environment, hold the token id and secret, and route API calls through https://api.squiid.io/v1/mux/... with Authorization: Bearer $SQUIID_API_KEY, with official SDKs working by base URL swap (gateway convention). Encoding minutes, storage and delivery will meter against prepaid credits at Mux's listed price on one invoice, alongside the object storage holding the originals and the model provider generating captions or summaries from them. Playback ids are stable, so a video referenced from your database keeps working across re-encodes and player changes.

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

• Provisioned Mux environment with tokens held by Squiid
• Adaptive bitrate encoding and HLS playback
• Thumbnails, previews and automatic captions
• Signed playback for paid or private video
• Mux list pricing, no markup

How to connect Mux

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 MUX_TOKEN_ID, MUX_TOKEN_SECRET, MUX_SIGNING_KEY
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

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

Pricing through Squiid

Mux charges per minute of video encoded, stored and delivered, with separate rates for live streaming, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Mux usage, with no markup and no per-request margin.

Mux is used on the pay as you go basis, so there is no fixed monthly plan cost to pass through. You pay for what you use at the provider’s listed price.

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 Mux 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: files and configuration are copied into your own Mux account; there is no account transfer. Squiid never owns your code, your schema or your domain, and the gateway speaks Mux'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

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