Runway Model Router 'no eligible model': raise max credits or enable more models
What Runway users hit in practice, with the verified fix: Runway Model Router 'no eligible model': raise max credits or enable more models
Runway Model Router 'no eligible model': raise max credits or enable more models
TL;DR
[Official Runway API docs (troubleshooting)]: A Model Router 'no eligible model' error means no model satisfies the configuration constraints plus the request together, and the error identifies which constraint(s) emptied the pool. The typical culprit is max credits per generation combined with the requested duration leaving nothing eligible. Fix it in the Developer Portal by adjusting the router configuration: enable additional models or raise the max credits per generation (see Configuring a Model Router).
Use this when you run into the situation in the title.
When not to use this skill: unrelated tasks. It covers only the procedure above.
Compatibility
The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.
Details
Context: Official docs (Runway API Troubleshooting Guide): documents why Model Router requests fail with a 'no eligible model' error. The error names which configuration constraints emptied the eligible pool, commonly the max-credits-per-generation and requested duration combination.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.