OpenRouter Routing Choice #663
tumblewader
started this conversation in
Feature Requests
Replies: 1 comment 1 reply
-
|
It would also be great if custom routing and disable fallback could be enabled. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
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 |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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.
Beta Was this translation helpful? Give feedback.
All reactions