| name | exa-search |
| description | Search the web using Exa AI instead of Brave (MCP-compatible endpoint) |
| homepage | https://exa.ai/ |
| metadata | {"openclaw":{"emoji":"🔍","requires":{"bins":["curl","jq"],"env":["EXA_API_KEY"]}}} |
Exa Search
Search the web using Exa AI. Use this INSTEAD of the built-in web_search tool (which uses Brave).
Quick Start
export EXA_API_KEY="your_key_here"
~/.openclaw/workspace/skills/exa-search/search.sh "your query" 5
Get API Key
- Go to https://dashboard.exa.ai/api-keys
- Create a new API key
- Set it in your environment:
EXA_API_KEY=...
Why Exa?
- Semantic search - understands meaning, not just keywords
- Better for AI/tech content - designed for LLM workflows
- Clean results - structured, relevant output
- MCP-ready - uses Model Context Protocol (future-proof)
Comparison
| Feature | Exa | Brave |
|---|
| Semantic search | ✅ | ❌ |
| Real-time web | ✅ | ✅ |
| Code/examples focus | ✅ | ⚠️ |
| Free tier | ✅ | ✅ |
| MCP support | ✅ | ❌ |
MCP Server
The full Exa MCP server is available at https://mcp.exa.ai/mcp.
When OpenClaw adds native MCP support, this skill will connect directly.
For now, use the search.sh script which calls the Exa REST API.