OpenRouter Routing Choice

[tumblewader]

OpenRouter automatically routes requests to providers based on cost and uptime. However, the best provider for a specific task may not always be the one selected by OpenRouter—for instance, you might prefer a provider with a larger context size. Currently, we rely on OpenRouter's routing decisions, but it would be beneficial to allow users to configure their API keys to select a preferred provider manually.

[IntranetFactory]

It would also be great if custom routing and disable fallback could be enabled.

[Oscarvdm]

Look at R1 for example: some providers are dreadfully slow, others dreadfully expensive, while others have a very limited context window. Also, different providers use different quantization of the models, which also means different quality. The default routing within OpenRouter for R1 is not ideal for Roo code.

As a bonus: support attaching suffixes like :nitro or :floor, see #1026

[PhunkyBob]

I wanted to request this feature.
I maybe can work on it, but I would like to know beforehand if such a PR would be approved?

(I don't want to put effort in the void)

Workaround : use LiteLLM proxy and specify the desired provider.

Also, I asked to the OpenRouter team if it would be possible to access a direct provider in the model id (eg. qwen/qwen-2.5-coder-32b-instruct:groq).

[PhunkyBob]

I have created a PR : #1376

[it-sha]

Thanks a lot for your work!
Could you please take a look at #1919 ?
It seems like not all providers are included in select (e.g. for DeepSeek R1)