What problem does it solve? Setting up web search in Hermes Agent requires choosing among 7 provider plugins, installing the right SDKs, managing API keys, and wiring search versus extract backends correctly. This Skill guides that configuration so web_search and web_extract tools work without trial and error. ## Core Features & Use Cases - Provider Setup: Step-by-step configuration for DuckDuckGo, Exa, Firecrawl, Tavily, Parallel, Brave Free, and SearXNG, including SDK installation and API key placement in ~/.hermes/.env. - Backend Switching: Change search_backend and extract_backend independently via hermes config set, with the shared web.backend field as fallback; changes apply immediately without restart. - Pitfall Avoidance: Covers secret redaction masking keys in output, search-only versus extract-capable providers, case-sensitive provider names, and SDK-versus-plugin separation. - Use Case: You start with free DuckDuckGo search, then upgrade to Exa for both search and full-page extraction by installing exa-py, adding EXA_API_KEY, and setting both backends to exa. ## Quick Start Ask the agent to configure Hermes web search to use Exa for both search and extract, including installing the SDK and verifying the provider works.