Runway Dev Model Routers

Model Routers let an application refer to a saved routing preference instead of embedding a particular model choice. Consult runway-dev for account setup, credential handling, and SDK task guidance when that skill is installed.

Existing integration

1. Inspect the application's existing configId and its server-side request path.
2. When the live configuration or access must be verified, use Dev MCP to locate the router by configId, then fetch details using the identifier returned by the tool. A router record UUID and its configId are distinct values; pass the configured configId in SDK requests.
3. Read the current overview and generation guide at https://docs.dev.runwayml.com/model-routers/ and https://docs.dev.runwayml.com/model-routers/generating/. Router request fields and types differ from direct-model endpoints; use the schema for the modality being called.
4. Integrate the documented SDK method (generate.video, generate.image, or generate.audio) behind the application's server boundary. Chain the SDK task wait helper directly from create().
5. For a non-billable routing check, the current API supports HTTP dryRun: true; SDK dry-run support is not documented. Keep the dry-run and eventual live input equivalent, and use current docs for response fields. Do not issue the live call unless the user requested or approved billable verification.

Creating or changing a router

Use live MCP tools to inspect or manage router state. Clarify missing targets or routing preferences; when the user has specified them, carry out the requested creation or update without requiring another confirmation or a JSON preview. Summarize the result in plain English unless the user asks for raw configuration.

Updating settings replaces the full settings object and clears omitted optional fields. Read the current configuration before updating it and preserve settings the user did not ask to change. Updating only name or description leaves settings unchanged. Confirm before deleting a router unless the user already explicitly requested deletion of that exact router.

Check current eligible models and constraints through Dev MCP when they affect the configuration. Do not hardcode a model catalog, pricing, or model eligibility in this skill. Check project credit balance immediately before an approved billable test.