Web Search Plus is a unified search aggregator that connects to seven search providers and automatically selects the best one for each query. Instead of manually choosing between Google, research-focused engines, or privacy-focused alternatives, the skill analyzes your search intent and routes queries intelligently.
With support for Serper, Tavily, Exa, Perplexity, You.com, Querit, and SearXNG, you only need one API key to get started and can expand coverage by adding more providers over time.
Key Features
- Seven search providers including Serper (Google), Tavily (research), Querit (multilingual), Exa (neural search), Perplexity (AI answers with citations), You.com (real-time/RAG), and SearXNG (privacy-focused self-hosted)
- Intelligent auto-routing using multi-signal analysis to automatically select the best provider based on query type, language, and intent
- Automatic fallback that seamlessly switches to the next available provider when one fails due to rate limits or errors
- Minimal setup requiring only one API key to get started, with additional providers added incrementally for broader coverage
- Routing transparency with an --explain-routing flag that shows why a specific provider was selected for each query
Use Cases
- Run product research and price comparisons routed automatically to Google via Serper
- Conduct deep academic or technical research routed to Tavily or Exa for semantic results
- Search in multiple languages with automatic routing to Querit for multilingual support
- Find similar companies, papers, or products using Exa's neural search capabilities
How It Works
The skill examines query characteristics — keywords, intent signals, language, and context — to score each configured provider's suitability. The highest-scoring provider handles the query, with automatic fallback to alternatives if the primary choice fails. Users can override routing with command flags or request explanations of routing decisions.
Getting Started
Run the interactive setup wizard with python3 scripts/setup.py, or manually configure API keys in a .env file or config.json. You only need one provider key to start. Add more providers over time for better coverage and fallback resilience.
