Quick Answer
Runway Dev is a developer platform for adding generative media to an application. It is broader than a single video endpoint: the current official documentation includes direct image, video, audio, edit, upscale, and character APIs; a Model Router; packaged Recipes; published Workflows; real-time Characters; organization reporting; and task management.
The practical integration choice is:
| Need | Start with | Why |
|---|---|---|
| Exact model and request control | Base model endpoint | Your application selects the model and owns the task-specific logic. |
| Flexible model choice | Model Router | A saved configuration can optimize among qualifying models for cost, latency, or quality. |
| Known creative outcome | Recipe | Runway packages model selection, prompting, and post-processing into one endpoint. |
| Private multi-step pipeline | Workflow | Build and publish a custom pipeline, then invoke its private endpoint. |
| Live interactive avatar | Characters | Use the real-time character, voice, knowledge, and tool-calling surface. |
This page was checked against Runway’s live developer documentation on July 31, 2026. Models, endpoints, prices, limits, and lifecycle can change. Treat the official portal, API reference, pricing page, and contract for your organization as the final sources.
Keep the Product Surfaces Separate
Three similarly named surfaces answer different questions:
- Runway creative app: interactive generation and editing for creators.
- Runway Dev: developer account, API organization, credits, model identifiers, rate limits, SDKs, and production integrations.
- Flowith: a separate workspace whose live model selector must be checked independently.
A provider announcement can prove that Runway offers a capability. It cannot prove that the capability is enabled for a particular plan, organization, region, API version, creative-app account, or Flowith workspace.
Start from the Runway Dev access guide when the decision is still about product surface. Use the Aleph 2.0 model guide when the task is specifically video-to-video editing.
Direct Model Calls
Use a base model endpoint when the product needs an exact model or a request schema that should not be routed elsewhere. Runway’s current model catalog includes first-party and third-party models across video, image, audio, editing, upscaling, and real-time avatar tasks.
For each model, record:
- the exact API identifier;
- accepted input types;
- output type and duration;
- current endpoint and API version;
- credits and minimum charge;
- moderation and task-failure behavior;
- output URL lifetime and storage plan;
- known lifecycle or deprecation status.
Do not copy a consumer-facing model label into code. Use the identifier documented for the API surface and keep it in configuration so it can be changed without rewriting application logic.
Model Router
Runway’s Model Router is useful when several current models can satisfy a request. A router configuration can set:
- cost, latency, or quality preference;
- a price cap;
- allowed or denied models and providers;
- hard capability constraints.
The application calls a routed endpoint with the configuration ID. Runway says the response metadata reports which model was selected and the realized credit cost. Router generations are billed at the standard rate for that selected model, with no separate router premium documented on the current pricing page.
Routing does not remove the need for evaluation. Build an acceptance set for the output task and review whether the selected model stays inside the required safety, rights, latency, quality, and cost boundaries.
Recipes
Recipes are Runway-built endpoints for defined creative outcomes. Current official examples include:
- Product Ad;
- Product Swap;
- Product UGC;
- Multi-Shot Video;
- Ad Localization;
- Marketing Stock Image;
- Product Campaign Image.
Use a Recipe when the output matches a supported outcome and you prefer one call over maintaining the underlying prompting and post-processing. Use a base model when you need full pipeline control or the use case does not fit a current Recipe.
Do not treat “production-ready” marketing language as automatic approval for a real campaign. Review brand accuracy, product geometry, claims, text, people, rights, disclosure, destination format, and local policy for every accepted asset.
Workflows
Workflows are for custom pipelines that combine models, modalities, and tasks. The current API reference exposes endpoints to list published workflows, retrieve details, run a workflow, and retrieve invocation detail.
A safe integration boundary is:
- build and test the pipeline in the authorized Runway environment;
- publish a version;
- store the workflow ID in configuration;
- invoke it from the application;
- capture the invocation ID and returned task state;
- validate the final output and costs;
- roll forward or back deliberately when the workflow changes.
Do not silently edit a production workflow without an acceptance run. The endpoint can stay the same while the internal graph changes.
Characters
Runway Characters covers real-time avatar interactions. The developer documentation includes custom avatars, conversations, knowledge documents, custom voices, client and server tools, camera and screen sharing, and meeting integrations.
Before enabling a character:
- obtain permission for the source face, voice, documents, and brand;
- tell users when they are interacting with an AI character;
- restrict tool calls to the minimum authority needed;
- validate knowledge and response boundaries;
- define retention, deletion, and access controls;
- test interruption, escalation, abuse, and failure behavior.
An interactive avatar is a user-facing agent surface, not only a media asset.
A Minimal API Workflow
Runway’s getting-started guide shows Node, Python, and cURL examples. The exact syntax can change, but the durable flow is:
- create a Runway Developer account;
- store the API secret outside source control;
- install and pin a tested SDK or call the versioned HTTP API;
- validate and authorize the input asset;
- submit a task with the current model ID and request fields;
- store the returned task ID;
- wait or poll with a timeout and bounded retry policy;
- handle failed and moderated tasks explicitly;
- validate the output;
- copy accepted assets into storage you control;
- log the model, API version, credits, latency, attempt, and review result.
Runway’s current HTTP examples include an Authorization bearer token and an X-Runway-Version header. Follow the live reference rather than copying an old header or request schema from a third-party tutorial.
Budget Cost per Accepted Result
Runway Dev currently sells credits at $0.01 per credit, while each model and Recipe has its own rate. For example, the July 31 pricing page lists:
aleph2: 28 credits per second, 56-credit minimum;gen4.5: 12 credits per second;gen4_turbo: 5 credits per second;act_two: 5 credits per second.
These figures are a dated snapshot, not a quote.
Use:
accepted-result cost = live request cost × attempts + review + storage + post-production
If a 5-second Gen-4.5 clip costs 60 credits and four attempts produce one accepted result, generation credits total 240, or $2.40 before tax and other workflow costs. If a Recipe reduces prompt engineering but costs more per call, compare the full accepted-result cost rather than the lowest per-second number.
Production Checklist
Before launch, verify:
- current model and endpoint availability;
- API version and pinned SDK;
- input file types, sizes, and URL access;
- task timeout, cancellation, and retry rules;
- rate and spend ceilings;
- moderation and failure handling;
- output URL lifetime and controlled storage;
- attribution or disclosure requirements;
- consent and rights for people, products, brands, footage, images, audio, and text;
- account roles, secret rotation, logs, retention, and deletion;
- acceptance tests for visual accuracy, continuity, text, identity, and unwanted additions;
- a model, Recipe, Router, or Workflow migration path.
Provider enterprise claims do not replace your own security review or signed terms.
Frequently Asked Questions
What is Runway Dev?
Runway Dev is Runway’s developer platform for integrating image, video, audio, editing, and real-time character capabilities. Current surfaces include direct model APIs, Model Router, Recipes, Workflows, Characters, SDKs, and a versioned HTTP API.
Should I use a base model, Model Router, Recipe, or Workflow?
Use a base model for exact model control, Model Router for a reusable cost, latency, or quality policy, a Recipe for a known packaged outcome, and a Workflow for a custom multi-step pipeline. Choose Characters for real-time avatar interactions.
How do Runway API tasks work?
A generation request creates an asynchronous task. Store the task ID, wait or poll for completion, validate the output, handle failed tasks, and copy accepted assets into storage you control before temporary URLs expire.
How much does the Runway API cost?
Runway Dev bills in credits and currently sells credits at $0.01 each. Model and Recipe rates differ, and Router calls are billed at the selected model’s standard rate. Verify the live pricing page and measure attempts per accepted output.
Are Runway Dev and the Runway creative app the same account surface?
Treat them as separate product and billing surfaces. The creative app, developer portal, API organization, model catalog, credit balance, limits, and terms can differ even when they belong to the same provider.
Does Runway Dev prove a model is available in Flowith?
No. Provider API availability does not establish a Flowith model mapping. Verify the current Flowith workspace separately from Runway’s creative app and developer portal.
Bottom Line
Start with the narrowest surface that meets the acceptance task. Direct models maximize control, Router adds reusable selection policy, Recipes package known outcomes, Workflows package your own pipeline, and Characters create a real-time agent experience.
Keep product access, API identity, credits, safety, rights, review, and Flowith availability separate. Build for model change from the first request.