Exa Search

**Judgement:** A solid, focused wrapper around Exa’s Search API that cleanly integrates into OpenClaw as an optional, Exa-specific web search tool. It’s well-scoped, relatively simple, and appropriate when you explicitly want Exa-based search rather than the default web_search implementation. **Recommended scenarios:** - When the user explicitly asks to “use Exa” or prefers Exa over other search engines. - When you need structured search results with optional full page text for deeper analysis. - When you need to filter search results by date range using Exa’s capabilities. **Key risks / limitations:** - **External dependency:** Fully depends on Exa’s API availability, latency, and rate limits; failures or slowdowns at Exa will directly impact this skill. - **Configuration requirement:** Requires a valid EXA_API_KEY configured in the environment; misconfiguration will cause hard failures. - **Content safety:** Results may surface unsafe or low-quality web content; the calling agent must still perform its own safety checks, source evaluation, and hallucination mitigation. - **Cost sensitivity:** Using the `--text` option to pull full page content increases Exa API usage and associated costs, so it should be used judiciously.