I have searched the existing issues and discussions.
Problem Description
When an API (e.g., Google PSE) reaches its daily quota, users must manually switch alternatives.
Desired Solution you'd like
Quota Tracking
Backend silently records daily usage per API (counted by requests).
Allow users to set custom daily quotas (e.g., Google PSE: 100 calls/day).
Priority-Based Auto-Switch
Let users define API priority chains (e.g., Primary: Google PSE → Backup1: Brave → Backup2: DuckDuckGo).
Automatically use next API in the chain when current API's quota is exhausted or returns errors.
Alternatives Considered
If this feature is beyond current development scope, at minimum allow users to:
Modify Search API base URLs (e.g., redirect to a user-hosted proxy server that handles quota routing).
Additional Context
No response
Originally created by @Meo597 on GitHub (Mar 29, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/12178
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
When an API (e.g., Google PSE) reaches its daily quota, users must manually switch alternatives.
### Desired Solution you'd like
**Quota Tracking**
Backend silently records daily usage per API (counted by requests).
Allow users to set custom daily quotas (e.g., Google PSE: 100 calls/day).
**Priority-Based Auto-Switch**
Let users define API priority chains (e.g., Primary: Google PSE → Backup1: Brave → Backup2: DuckDuckGo).
Automatically use next API in the chain when current API's quota is exhausted or returns errors.
### Alternatives Considered
**If this feature is beyond current development scope, at minimum allow users to:
Modify Search API base URLs (e.g., redirect to a user-hosted proxy server that handles quota routing).**
### Additional Context
_No response_
I don't think this will be implemented as it adds a lot of complexity and this feature is not really needed for 99% of users. Google PSE has very high quotas by default (much more than 100) and if the 10000 an hour (which should be the default) is not enough for you, you can request higher quotas on Google Cloud Platform and they'll give it to you no problem.
If you consistently hit quota limits, you should try to look into different or cheaper search engines. Brave is, I think a bit cheaper than Google PSE and searxng is free.
Alternatively, you can implement your own web search logic using tools or functions which has this priority chain - you will not use Open WebUI's web search but your own. There are many web search templates you can build something like this off of on the Open WebUI community.
<!-- gh-comment-id:2763356807 -->
@Classic298 commented on GitHub (Mar 29, 2025):
I don't think this will be implemented as it adds a lot of complexity and this feature is not really needed for 99% of users. Google PSE has very high quotas by default (much more than 100) and if the 10000 an hour (which should be the default) is not enough for you, you can request higher quotas on Google Cloud Platform and they'll give it to you no problem.
If you consistently hit quota limits, you should try to look into different or cheaper search engines. Brave is, I think a bit cheaper than Google PSE and searxng is free.
Alternatively, you can implement your own web search logic using tools or functions which has this priority chain - you will not use Open WebUI's web search but your own. There are many web search templates you can build something like this off of on the Open WebUI community.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Meo597 on GitHub (Mar 29, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/12178
Check Existing Issues
Problem Description
When an API (e.g., Google PSE) reaches its daily quota, users must manually switch alternatives.
Desired Solution you'd like
Quota Tracking
Backend silently records daily usage per API (counted by requests).
Allow users to set custom daily quotas (e.g., Google PSE: 100 calls/day).
Priority-Based Auto-Switch
Let users define API priority chains (e.g., Primary: Google PSE → Backup1: Brave → Backup2: DuckDuckGo).
Automatically use next API in the chain when current API's quota is exhausted or returns errors.
Alternatives Considered
If this feature is beyond current development scope, at minimum allow users to:
Modify Search API base URLs (e.g., redirect to a user-hosted proxy server that handles quota routing).
Additional Context
No response
@Classic298 commented on GitHub (Mar 29, 2025):
I don't think this will be implemented as it adds a lot of complexity and this feature is not really needed for 99% of users. Google PSE has very high quotas by default (much more than 100) and if the 10000 an hour (which should be the default) is not enough for you, you can request higher quotas on Google Cloud Platform and they'll give it to you no problem.
If you consistently hit quota limits, you should try to look into different or cheaper search engines. Brave is, I think a bit cheaper than Google PSE and searxng is free.
Alternatively, you can implement your own web search logic using tools or functions which has this priority chain - you will not use Open WebUI's web search but your own. There are many web search templates you can build something like this off of on the Open WebUI community.
@Meo597 commented on GitHub (Mar 29, 2025):
Allow users to modify Search API base URLs.