You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow users to select from multiple search API options or input their own API credentials during app deployment or via a configuration interface post-deployment.
Why the solution needed
It appears that the Internet search feature stops working completely when you hit the DuckDuckGo search API limit. Although this potential rate limit error is mentioned in the documentation, it would be best if users can choose search APIs when they build the app or even after deploying it. This would not only help avoid service interruption due to rate limits but also allow users to choose APIs that best fit their needs in terms of search results quality, privacy considerations, or existing API subscriptions.
Additional context
Currently, Internet search is handled by internet_search.py, in which the DuckDuckGo search API is hardcoded. I confirmed that modifying the internet_search() function with SerpAPI worked as well.
Implementation feasibility
Are you willing to collaborate with us to discuss the solution, decide on the approach, and assist with the implementation?
Yes, I am able to implement the feature and create a pull request.
No, I am unable to implement the feature, but I am open to discussing the solution.
The text was updated successfully, but these errors were encountered:
I tested the following with v2.0.0. Now that the return value type of internet_search() changed since then, it might not be as straight forward to use another search API.
I confirmed that modifying the internet_search() function with SerpAPI worked as well.
Describe the solution you'd like
Allow users to select from multiple search API options or input their own API credentials during app deployment or via a configuration interface post-deployment.
Why the solution needed
It appears that the Internet search feature stops working completely when you hit the DuckDuckGo search API limit. Although this potential rate limit error is mentioned in the documentation, it would be best if users can choose search APIs when they build the app or even after deploying it. This would not only help avoid service interruption due to rate limits but also allow users to choose APIs that best fit their needs in terms of search results quality, privacy considerations, or existing API subscriptions.
Additional context
Currently, Internet search is handled by internet_search.py, in which the DuckDuckGo search API is hardcoded. I confirmed that modifying the
internet_search()
function with SerpAPI worked as well.Implementation feasibility
Are you willing to collaborate with us to discuss the solution, decide on the approach, and assist with the implementation?
The text was updated successfully, but these errors were encountered: