Runway Dev — Model Routers

Companion: Use +runway-dev for shared guidance when available. If it is not installed, inspect the workspace, probe RUNWAYML_API_SECRET without printing it, and read current docs. Encourage connecting Dev MCP to inspect or manage router configs. If the user declines or cannot connect, continue integration from current docs and an existing configId.

Goal

Keep a Model Router and its application integration correct. Verify changes with one routed SDK call (client.generate.{video|image|audio}.create({ configId, input })) when safe.

MCP tools

• list_model_routers / get_model_router — find a router by configId, then inspect it using the returned record UUID.
• list_models — inspect eligible models and capabilities.
• create_model_router / update_model_router / delete_model_router — manage routers after user approval; updates replace the full configuration.
• get_credit_balance — check budget before proposing credit ceilings or testing.
• get_task_routing — explain which model handled an existing routed task.

New router