exa-searchlisted

# Exa Search Use Exa as an API-backed `web_search` provider when ArkSpace routes a semantic or technical discovery task to Exa, or when the user explicitly asks for Exa search. Exa configuration is managed by `provider-manager`; do not ask the user to edit config files by hand. ## Source References - Official Search API: `https://exa.ai/docs/reference/search` - Official Contents API: `https://exa.ai/docs/reference/get-contents` - Official Find Similar API: `https://exa.ai/docs/reference/find-similar-links` - Official Answer API: `https://exa.ai/docs/reference/answer` - OpenClaw guide: `https://docs.openclaw.ai/tools/exa-search` ## Before Use Resolve the installed ArkSpace package root before running commands. Replace `<installed-arkspace-path>` with the directory two levels above this loaded `SKILL.md`, such as `/Users/<user>/.claude/plugins/cache/ark-space/ark-space/0.1.2`. Use the installed package path, not a repository-relative command. Check configuration: ```bash python3 <installed-arkspace-path>/scripts/arkspace.py provider check exa --capability web_search ``` Set up Exa once: ```bash python3 <installed-arkspace-path>/scripts/arkspace.py provider setup exa --wizard ``` For multiple API keys: ```bash python3 <installed-arkspace-path>/scripts/arkspace.py provider setup exa --wizard --key-count 2 ``` ## Missing Configuration Recovery If the provider check reports a missing Exa API key: 1. Ask the user whether to start setup now: "Exa is not configured. Sho