Connect Claude to Exa

Read the team this key belongs to: its id, its name, how many requests are running or queued right now, and the concurrency limits behind those numbers. Free - it is the one call in this connector that appears on no price list, and it runs no search. Use it to check headroom before firing a batch of searches, and to confirm a key works. It does not report credit balance or spend; Exa exposes those only through a separate admin API and its own dashboard. This is the connection test, for exactly those reasons.

Search the web and get back ranked results with titles, URLs, publication dates and authors. Costs $7 per thousand requests for the first ten results and $1 per thousand results after that, so `numResults: 50` is five times the result charge of the default. `contents` is billed separately again - $1 per thousand pages for each content type asked for, meaning text and highlights and a summary on one page is three charges - so omit it entirely when the URLs alone are enough and fetch the pages you actually want with get_contents afterwards. `type` picks how hard Exa works: `auto` (the default) balances quality and speed, `fast` and `instant` cut latency, and `deep-lite`, `deep` and `deep-reasoning` run a multi-step search at $12 to $15 per thousand requests rather than $7. The old `neural` and `keyword` values were retired and are no longer accepted. Narrow with `includeDomains`, `excludeDomains` and the published-date range before reaching for a deeper type - it is almost always cheaper. Results are pages other people wrote, so the payload is kept out of the audit log, and the query is prose the caller wrote, so it is kept out too.

Given one URL, find pages like it. Billed as a search - $7 per thousand requests covering ten results, $1 per thousand results beyond that, and `contents` charged separately again at $1 per thousand pages per content type. This is the right call when you already have a good example and want more of the same: a competitor's site, a paper, a job posting. Set `excludeSourceDomain` to keep the rest of the source's own site out of the answer, which is usually what you meant. Results are pages other people wrote, so the payload is kept out of the audit log; the argument is a URL rather than prose, so it is logged.

Fetch the contents of pages you already have URLs for, without paying for a search. $1 per thousand pages for each content type asked for - so `text` and `highlights` and `summary` on the same hundred URLs is three hundred pages of charges, not one hundred. Ask for one. This is the cheaper half of the usual pattern: run search without `contents`, decide which handful of URLs are worth reading, then call this on those. Pass either `urls` (ordinary web addresses) or `ids` (the `id` values a search returned), one or the other, up to a hundred. `maxAgeHours` controls freshness - 0 forces a live crawl, a positive number accepts a cached copy that old, and the older `livecrawl` flag is deprecated in favour of it. The pages are other people's writing, so the payload is kept out of the audit log.

Ask a question and get a written answer with the citations it was built from. $5 per thousand requests - cheaper than a search plus a round of contents plus a model call, and it returns in one hop. Use it when the question has an answer rather than a reading list; use search when you want to choose the sources yourself. `citations` is the part worth checking: it names the pages the answer came from, and an answer with thin or off-topic citations is one to distrust. Set `text: true` to get the full page text of each citation, which costs more and is usually unnecessary. `outputSchema` returns a structured object instead of prose. Streaming is not offered - the gateway returns whole responses. The question is prose the caller wrote and the answer is built from other people's pages, so neither is written to the audit log.

Check a research run started by create_agent_run and read its result. Free - polling is not billed; the run already in flight is. `status` is queued, running, completed, failed or cancelled, and the last three are terminal. Poll every few seconds and back off; a deep run can take minutes. A completed run carries `output`, `stopReason` and `costDollars`, which is what the run actually cost rather than what the cap allowed. `costDollars` is worth reading even on a cheap run - it is the only feedback loop this API gives on whether the effort setting was right. The result is built from other people's pages, so the payload is kept out of the audit log.

List this team's research runs, newest first, with their status and what each one cost. Free. Two reasons to call it: finding a run whose id was lost, rather than starting a second one and paying twice; and adding up `costDollars` across a day to see where the money went, which no other endpoint here will tell you. Page with `cursor`, taken from the previous response. Each record carries the request that started it, so the payload is kept out of the audit log.