Manage Runway model routing with AI
Use a saved Model Router configuration for media generation, verify the correct identifier and inspect the route taken by a particular task.
To manage Runway model routing with AI, point runway-dev-model-routers at the application's existing generation path. A team that keeps a routing preference in its Runway project needs the application to use the proper configuration identifier. The internal record used to inspect the setting is a different value, and mixing them up can break the integration.
The agent checks the saved preference and the request shape for the selected media type. It can also inspect a previous task when the team wants to understand why a particular model handled it. Changes to a shared configuration affect the applications that use it, so identify the project and intended change before editing or removing a router.
What it does
- Find a saved routing configuration.
- Distinguish its configuration ID from its management record.
- Connect image, audio or video generation to that preference.
- Inspect routing information for an existing task.
- Check eligible models and project credit before a live test.
Install and use
- Install the skill in a supported coding agent. Connect Runway Dev MCP for account information and keep the application's SDK secret on the server.
- Ask “Identify the router our audio page uses and inspect the route taken by this task. Do not submit another generation.”
- Verify the chosen configuration before requesting changes or authorising a billable test.
FAQ
Source
Made by Runway. Original skill: runway-dev-model-routers, published on GitHub under the MIT licence.
View on GitHub