Most search APIs give an agent ten URLs and leave it to fetch each one, burning turns and context. Exa returns usable text from the search itself, and only when that is insufficient do you spend a call on the full page. Two tools, no key required to start, and the ordering is obvious — which is why this is one of the easiest connections to justify leaving in place.
Exa's endpoint, which listed two tools to our probe as exa-search-server. Search returns usable content rather than a link list, and the fetch tool is for when the highlights are not enough.
- web_search_exa — search any topic and get clean, ready-to-use content, with a result count you control
- web_fetch_exa — read a page's full content as clean markdown, with a character limit
Nothing to start — no API key needed. An optional dashboard key enhances it. Pricing is pay-as-you-go credits, with sign-up credits noted on their pricing page.
Paste a URL — add the endpoint to your client