Runway's developer platform, read against the aggregators
Runway documents a developer platform around its own generative models: a public API, a Dev MCP connection for coding agents, Node.js and Python SDKs with built-in task polling, and output URLs that expire within a day or two. The register reads it as the fullest record of a model maker that also ships a platform. From 6 source pages, read 2026-09-25; no maker pays to be listed.
1What the register already records
Six rows the register keeps for Runway, then three for fal, the aggregator whose documentation is closest in shape — one API for many makers' models.
- OverviewA developer API for Runway's generative models
- Start buildingA Dev MCP connection for Cursor, Claude Code and Codex
- Available SDKsNode.js and Python SDKs, the Node one with TypeScript bindings
- Generating contentBuilt-in task polling in its SDKs
- OutputsOutput URLs that expire within 24 to 48 hours, to be saved to your own storage
- Announcement1080p named for Seedance 2.5 on the API
- Page headerOver a thousand models reached through one API
- Async inferencePython and JavaScript clients
- Inference methodsQueued requests that are polled or answered by webhook
- GuideA full-quality download and a share link; the browser plays a lighter copy
2What Runway documents for a pipeline
Runway's developer pages are read here for six hooks. There is a developer API for its generative models, a Dev MCP connection for Cursor, Claude Code and Codex, Node.js and Python SDKs with TypeScript bindings on the Node side, and task polling built into those SDKs. Output URLs expire within 24 to 48 hours and are meant to be saved to your own storage, and the resolution row names 1080p for Seedance 2.5 on the API.
Two of those readings say more than their hook. The MCP connection means a coding agent can drive the model without a human in a browser, which is a different kind of integration from a key and a curl command. The expiring URL means the pipeline owns the file the moment the job ends, or loses it.
3Platforms that put several makers behind one endpoint
The register's aggregators answer the other half of the question. fal reaches more than a thousand models through one API, ships Python and JavaScript clients, serves generated media as public URLs with the storage time set per request, and lets queued requests be polled or answered by webhook. Replicate runs many makers' models and custom ones, with an MCP server, clients for Python, Node.js and Go, and webhooks that deliver a finished prediction's metadata. Pika's reading is the plainest statement of the model: one API for many providers' models, its own included.
Runway's platform is the opposite arrangement. One maker's models, documented by that maker, with the resolution and the file clock under its control. Which suits a pipeline is not a quality question; it is a question about how many suppliers the work wants.
4What the counted lines beside this page are arguing about
The question behind this page was counted in the community material in the words above, and the material keeps 1,592 posts and 603 comment mentions for Runway. The two short quotations carried beside those counts are both about what a plan is worth — one asking whether signing up feels like a bad deal, one asking whether an annual plan at half price is worth taking.
That is the shape of the talk around a platform choice: buyers arguing about what the subscription is worth, while the documentation argues a different question, about what can be called, what comes back and when the file expires. This register only holds the second half, quoted and dated, and it leaves the first where it was written.
5Choosing by what must be true at each step
Put the readings in order and the decision sorts itself. Can the tool be called from code? 22 of the 28 tools document an API, three of them an API for several makers' models at once. Can an agent drive it? Twelve document an MCP connection, including Runway, Krea and Higgsfield. How will the pipeline know a render is done? Sixteen document a webhook and seven document polling, and a team that has written one will want the other checked before it switches.
SceneMixer's own row in the table below is about the last step rather than the first: what a finished piece of work looks like when it leaves the tool, without any of the calling plumbing above it. The rows beside it carry each maker's own wording.
6What each maker's own documentation states
| Maker | What its own pages state | Audio it states | Finishing it states | Docs read |
|---|---|---|---|---|
| Runway | Its Gen-4.5 model plus other video and image models, an agentic creative collaborator and editing | Music, voice and sound-effect generation; custom voice clones from Pro | 4K upscaling; HDR, ProRes and image sequences on Max | 2026-10-13 |
| SceneMixer | “Usually ten to twenty minutes, depending on the tier and how busy the queue is.” | Not carried on the pages read | Not carried on the pages read | 2026-10-13 |
Inclusion rule. Rows are the makers this page is about, each read on its own public documentation, plus the drama pipeline whose hooks this register keeps. A line a maker's documentation does not carry is written here as not carried on the pages read, which describes the reading rather than the product; nothing was called or installed to take it. Order. Alphabetical by maker name.
| Asked of each reading | Runway | fal | SceneMixer |
|---|---|---|---|
| What can be called | A developer API for its own generative models | Over a thousand models reached through one API | Not documented in the docs read |
| An agent's way in | A Dev MCP for Cursor, Claude Code and Codex | Not documented in the docs read | Not documented in the docs read |
| How a finished job is known | Task polling built into its SDKs | Queued requests polled or answered by webhook | Not documented in the docs read |
| What comes back | Output URLs expiring within 24 to 48 hours | Public CDN URLs, storage time set per request | A full-quality download and a share link |
Inclusion rule. Answers read from each maker's own documentation as this register recorded it — the vendor pages on 2026-10-13, the register rows on 2026-09-25. A line the documentation does not carry is written here as not documented in the docs read, which describes the reading rather than the platform. Order. As the lines are listed above.
7What the collection counted
The counts below belong to Runway, with the two questions the collection kept beside them. Both were written about what a plan is worth.
| Family | Posts | Comment mentions | Positive | Negative |
|---|---|---|---|---|
| Runway | 1592 | 603 | 131 | 77 |
Inclusion rule. Families the collection counted on this page's subject, from one subreddit. A thread can be counted on both sides. Order. Descending by posts.
Does signing up for Runway feel like getting ripped off?
r/runwayml, collected 2026-10-14
Is the Runway Unlimited annual plan at 50% off worth it?
r/runwayml, collected 2026-10-14
8When the maker's own way fits the pipeline better
- The models wanted are the ones on offer — The API serves Runway's generative models, with audio generation and a finishing line of 4K upscaling, HDR and ProRes higher up its plans — one maker's stack rather than a menu.
- The pipeline speaks TypeScript or Python — Node.js and Python SDKs are documented, with TypeScript bindings on the Node side and task polling built in, so the first version of a client is a package install.
- Files can be fetched and stored promptly — Output URLs expire within 24 to 48 hours, which suits a pipeline that copies a finished render into its own storage as soon as the job reports done.
This page answers a question the material collected asks in these words: "Should I use APIs or platforms like Higgsfield and Artlist for videos?" Beside it: workflows read as agent connections and parallel tasks and how a pipeline hears about them.