Issue: OpenRouter Custom Base URL Integration Not Fully Implemented

[cobra91]

Description

The current implementation (webview-ui/src/components/settings/providers/OpenRouter.tsx) fails to properly support custom OpenRouter base URLs when retrieving model providers and model lists. While the UI allows users to input a custom base URL, this value is not being passed to the useOpenRouterModelProviders hook or used in the underlying API calls. As a result, the application continues to fetch model data from the default OpenRouter endpoint (https://openrouter.ai/api/v1) instead of the user-specified URL.

This creates two key problems:

Model List Mismatch: The ModelPicker component displays models from the default OpenRouter API rather than the custom endpoint
Provider Data Inconsistency: Model provider information is fetched from the default endpoint, not the custom base URL
The required fixes involve:

Modifying useOpenRouterModelProviders to accept and utilize a baseUrl parameter
Updating the underlying getOpenRouterModelProviders API call to use this custom URL
Ensuring the ModelPicker component uses the correct service URL for model display
Adding baseUrl to the query key for proper React Query caching
Without these changes, users cannot effectively utilize self-hosted OpenRouter-compatible services or alternative endpoints. The current implementation only works with the default OpenRouter service, making the custom URL feature non-functional. The issue affects both model selection and provider routing functionality.

Would you like me to provide the exact code modifications needed for this fix? The changes are relatively straightforward but require updates across multiple files to ensure proper URL propagation through the application stack.

[Juice10]

Seems like its related to this but wasn't solved over there:

• OpenRouter provider doesn't respect baseurl when fetching generation details & when getting models RooCodeInc/Roo-Code#1571

Maybe you could come up with a solution for this @cobra91, if you are open to it?

[cobra91]

Here’s a summary of the changes made to fully support custom OpenRouter base URLs in your code:

Summary of Changes

Hook Signature Update
The useOpenRouterModelProviders hook now accepts a baseUrl parameter (in addition to modelId and options). This allows the hook to fetch model provider data from a user-specified OpenRouter-compatible endpoint, not just the default.

/webview-ui/src/components/ui/hooks/useOpenRouterModelProviders.ts
add const apiBase = baseUrl?.trim() || "https://openrouter.ai/api/v1" line 45
replace ``https://openrouter.ai/api/v1` by ${apiBase.replace(/\/$/, "")} line 47 old 46

API Call Update
The internal function getOpenRouterProvidersForModel also takes a baseUrl parameter and uses it to construct the API endpoint for fetching model provider data. If baseUrl is not provided, it defaults to https://openrouter.ai/api/v1.

/webview-ui/src/components/ui/hooks/useOpenRouterModelProviders.ts
add , baseUrl?: string line 42 for parameter member of function

React Query Cache Key
The React Query queryKey now includes baseUrl as part of its key:
["openrouter-model-providers", modelId, baseUrl]
This ensures that data is cached and refetched correctly when the base URL changes.

in export const useOpenRouterModelProviders
add baseUrl?: string, parameter line 118 old 115

add , baseUrl line 122 old 117
add , baseUrl line 123 old 118

Component Integration
Components that use this hook (such as the OpenRouter provider settings and model picker) now pass the custom baseUrl from user configuration, ensuring all model/provider data is fetched from the correct endpoint.

/webview-ui/src/components/settings/providers/OpenRouter.tsx
add apiConfiguration?.openRouterBaseUrl, line 61

Test Adaptation
Unit tests and mocks for the hook have been updated to support the new signature and ensure compatibility.

/webview-ui/src/components/ui/hooks/useSelectedModel.ts
add , apiConfiguration?.openRouterBaseUrl line 45

Result:
With these changes, users can now specify a custom OpenRouter-compatible API URL, and the application will correctly fetch model and provider data from that endpoint. This enables support for self-hosted or alternative OpenRouter services, not just the default public API.

[chrarnoldus]

The PR is merged. We did make some changes, so if you encounter any issues @cobra91 feel free to reach out!