Direct model control
Base models
Call current image, video, audio, edit, upscale, or character models through their documented endpoints.
Developer access guide · July 31, 2026
Runway Dev is an API platform, not an embedded Flowith tool
Use Runway Dev when an app needs programmatic media generation, editing, packaged creative outcomes, custom pipelines, routing, or interactive characters. Choose the narrowest current surface that satisfies the task, then build around asynchronous tasks, live pricing, review, and model change.
Choose the layer
Five surfaces solve different integration problems
Cost, latency, or quality routing
Model Router
Create a reusable routing configuration, set hard constraints, and let Runway select a qualifying model. The response reports the selected model and realized credit cost.
Known creative outcomes
Recipes
Use a Runway-built endpoint for tasks such as product ads, product swaps, UGC, multi-shot video, ad localization, and marketing stock images.
Private multi-step pipelines
Workflows
Publish a custom workflow, trigger its private endpoint, and retrieve invocation status. Build and version the workflow separately from the calling application.
Real-time avatars
Characters
Integrate interactive avatars with voice, knowledge, and tool calling. Treat consent, disclosure, data, and moderation as product requirements.
A bounded route from test to production
01
Choose one acceptance task
Define the input, desired output, maximum latency, cost ceiling, safety rules, and human review before selecting a model or packaged endpoint.
02
Create a Runway Developer account
Use the official developer portal. Keep Runway creative-app credentials, developer credentials, and any Flowith account separate.
03
Test in the Playground
Confirm the current request schema, model ID, limits, moderation behavior, output format, and likely attempt count before writing integration code.
04
Submit and monitor tasks
Use Runway's SDK or versioned HTTP API, store the task ID, poll or wait for completion, validate the response, and handle failed tasks explicitly.
05
Add production controls
Set timeouts, retry and spend ceilings, input validation, moderation, secure asset handling, logging, deletion, and a fallback path.
06
Review accepted output
Measure cost and latency per accepted result, not per request. Recheck rights, factual content, brand details, disclosure, and destination requirements.
Product boundary
Do not transfer access claims between surfaces
A Runway announcement can prove provider availability. It cannot prove that a model is enabled in a particular Runway account, creative-app plan, region, organization, or Flowith workspace.
Runway creative app
Interactive creation and editing
Web plans, credits, controls, and exports belong to the live app.
Runway Dev
Developer API and production integrations
Developer credits, model IDs, API versions, rate limits, and billing are separate.
Flowith
Independent AI workspace
No Runway Dev endpoint or model access is implied by this page.
Cost and launch checks
Measure accepted cost
Include retries, filtered tasks, unused variants, human review, storage, and downstream editing—not only credits per request.
Version the contract
Send the documented API-version header, pin tested SDKs, validate responses, and keep model IDs and routing configs outside application logic.
Review rights and safety
Verify input authority, consent, moderation, disclosure, output accuracy, contract terms, and destination policy for the exact workflow.
Continue by decision intent
Aleph 2.0 model guide Check the current video-to-video model ID, cost, edit role, and Gen-3 migration boundary. API implementation guide Turn the surface choice into an asynchronous, cost-bounded, reviewable integration plan. Gen-3 migration guide Replace retired Gen-3 modes with Gen-4.5, Animate Frames, and Aleph 2.0 paths. AI video workflow pricing Compare revision and accepted-output cost across provider-specific video workflows.
Official sources
- Introducing Runway Dev — platform surfaces and current launch framing.
- API getting-started guide — account, SDK, authentication, versioning, and task examples.
- Model catalog — current identifiers, inputs, outputs, and references.
- Recipes guide — packaged outcome endpoints and base-model boundary.
- Developer pricing — current credit and endpoint rates.
Runway Dev questions, answered
Runway Dev is Runway's developer platform for integrating image, video, audio, editing, and real-time character capabilities. Its current surfaces include base models, Model Router, Recipes, Workflows, Characters, SDKs, and a versioned API.
No. This is a source-checked access and decision guide. Create an account, test, buy credits, and call endpoints through Runway's official developer portal and documentation.
A Recipe is a Runway-built endpoint for a known outcome such as a product ad or ad localization. A Workflow is a custom multi-step pipeline that you build, publish, and trigger through a private API endpoint.
Use Model Router when several models can satisfy a request and the product needs a reusable cost, latency, or quality policy. Keep direct model calls for tasks that require a specific model or exact behavior.
Runway Dev bills generations in credits and currently sells credits for $0.01 each. Per-model and per-Recipe rates differ, so use the live developer pricing page and measure total cost per accepted result.
No. Runway Dev, the Runway creative app, and Flowith are separate product surfaces. Verify each current account and model selector independently.