Runway through Squiid

What Runway is

Runway builds video models and the tools around them. The developer API exposes text to video, image to video, video to video restyling and act-style character animation, with parameters for duration, aspect ratio and camera motion. Jobs are asynchronous: you submit a task, poll or receive a callback, and fetch the resulting clip from a URL. Outputs are returned as downloadable files with a limited lifetime, so a pipeline that does not copy them into your own bucket will find broken links later.

Video is the most expensive media to produce by hand and the most expensive to generate by machine, which makes it an unusual line item in a vibe-coded app. The features that justify it are marketing asset generation, product explainers built from stills, animated variants for ad testing, and turning a user's photo into a short clip. Because each job takes real time, they are almost always run as background work with the result stored in a bucket and served from a CDN. Aspect ratio and duration are chosen per job, which matters when the same asset has to exist as a square post and a vertical story.

Why connect it through Squiid

Runway is on the Squiid roadmap. Once connected, requests will go to https://api.squiid.io/v1/runway/... with Authorization: Bearer $SQUIID_API_KEY, official clients will work by pointing their base URL at the gateway (gateway convention), and generation will be metered against prepaid credits at Runway's listed rates. Prepaid metering matters more here than almost anywhere else: video is priced per second of output, so a loop that renders the wrong prompt a hundred times is the kind of mistake that is better stopped by an empty balance than discovered on a card statement.

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

• Text to video and image to video generation
• Video restyling and camera control parameters
• Async jobs with callbacks for long renders
• Hard credit ceiling on expensive renders
• Runway list pricing, no markup

How to connect Runway

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 RUNWAY_API_KEY, RUNWAYML_API_SECRET, RUNWAY_BASE_URL
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

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

Pricing through Squiid

Runway charges credits per second of generated video, varying by model and resolution, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Runway usage, with no markup and no per-request margin.

Runway 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 Runway 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: Runway is usage-metered, so leaving means creating your own Runway key and pointing the client at it. Squiid never owns your code, your schema or your domain, and the gateway speaks Runway'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

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