Exa API review
Best for agent research
POST https://api.exa.ai/search Authorization: Bearer $EXA_API_KEY # type: auto → ~1s, $7 per 1,000 requests # type: instant → ~250ms, $4 per 1,000 requests # type: deep → 4-15s, $12 per 1,000 requests
The Exa AI search API is an engine built to be read by a model rather than by a person. It returns ranked pages with the text already extracted, which is the difference between an agent that can answer a research question and one that hands you ten links and a scraping problem.
Pricing is per thousand requests and it moves with how hard you ask it to think. An instant search is $4 per 1,000, the default auto mode is $7, and a deep-reasoning search that runs a multi-step research process rather than one retrieval pass is $15. Everything is pay as you go with no floor, and the free tier hands you $10 of credits a month plus a $10 onboarding bonus with no payment method attached.
For go-to-market work the Exa AI API sits at the sourcing and signal end rather than the enrichment end. It will find you the companies that just published a pricing page change or a careers post; it will not hand you a verified mobile number, though contact enrichment is sold separately at $0.02 an email and $0.07 a phone.
The rest of the category is in the Signal APIs listing.
Six modes, and the price is the speed
The Exa search API takes a type parameter that picks how much work the engine does before answering. This is the whole cost model: the mode you choose sets both the latency and the rate, and most teams leave it on the default without checking whether they needed to.
| Mode | Typical latency | Per 1,000 requests | Use it when |
|---|---|---|---|
| instant | ~250 ms | $4 | A real-time path such as autocomplete or a voice agent. |
| fast | ~450 ms | $7 | The request is latency sensitive but not interactive. |
| auto | ~1 second | $7 | The default. Best balance of quality and speed. |
| deep-lite | ~4 seconds | $12 | Lightweight research and synthesis. |
| deep | 4 to 15 seconds | $12 | Multi-step search with stronger synthesis. |
| deep-reasoning | 12 to 40 seconds | $15 | Completeness matters more than latency. |
| Contents | n/a | $1 per 1k pages | Pull page text for URLs you already have. |
| Answer | n/a | $5 | One synthesised answer rather than ranked results. |
| Monitors | n/a | $15 | Standing queries that watch for new matches. |
Two add-ons stack on top of those rates. Returning more than 10 results costs another $1 per 1,000 requests on every mode except Contents and Answer, and AI page summaries cost $1 per 1,000 pages. A deep search asking for 50 results with summaries is therefore $14 per 1,000 rather than $12, which is still cheap and is still not the number you budgeted.
Exa can return highlights, full text or a summary for each result, and its own docs are blunt about the trap: pick one view per request, because asking for both highlights and text returns and bills two views of the same page. Highlights are the recommended shape for most agent work, since they give the model the relevant excerpts without filling the context window. Reaching for text as well is the most common way an Exa bill doubles without the result improving.
Exa API pricing, plan by plan
Exa API pricing has no monthly floor and no seats. There are three plans, and the only thing two of them really change is your query concurrency.
Starter
- $10 of credits every month, plus a $10 onboarding bonus
- Access to every endpoint
- 10 search queries per second, 50 agent concurrency
- MCP server, Claude connector and ChatGPT plugin
Developer
- The per-1,000 rates in the table above
- Up to 25 search queries per second
- 50 agent concurrency
- SOC 2 Type II, card or bank payment
Enterprise
- Custom search QPS and agent concurrency
- For large-scale requirements
The free tier is unusually generous for a search API: over $120 of credits a year with no payment method on file, which at the instant rate is 30,000 searches you never pay for. Exa also advertises up to $1,000 in free credits for startup and education projects. If you are evaluating against a competitor, you can run the whole bake-off before anyone signs anything.
Email and phone enrichment sit outside the search rate card entirely, at $0.02 per email and $0.07 per phone number. That is line with Apollo's per-email rate and above most of the specialists in this directory, which is the honest reason to treat Exa as a sourcing and signal tool with enrichment attached rather than as an enrichment provider.
Concurrency, not a monthly quota
Exa API rate limits are expressed as throughput rather than as a cap on volume, which suits pay as you go: nothing stops you spending, only going fast. The free Starter plan allows 10 search queries per second and 50 agent concurrency. Developer raises the search ceiling to 25 queries per second and leaves agent concurrency at 50. Enterprise sets both to whatever you negotiate.
What this means in practice
The numbers are small, and they are almost never the thing that bites.
- At 25 queries a second a list of 100,000 companies takes about 67 minutes of wall clock, not days.
- Agent concurrency of 50 is the one to watch if you fan out deep searches, because each runs for 4 to 40 seconds.
- A deep-reasoning job at 40 seconds a call saturates 50 concurrent slots at roughly 75 calls a minute.
- Nothing here caps your monthly spend, so a runaway loop is a billing problem rather than a 429.
Where the numbers live
Exa documents billing and rate limits on one page, which is the right place to check before a large run.
- Billing and rate limits: docs.exa.ai/docs/admin/billing
- Per-plan QPS is on the pricing page rather than in the docs.
- Both were read on 8 October 2026.
Like the other pay-as-you-go providers here, Exa's rate card has no monthly floor, and its limits do not cap spend. That is a genuine advantage right up to the moment an agent retries a deep-reasoning search in a loop overnight. At $15 per 1,000 that is not catastrophic, but it is also not a number anyone budgeted, and nothing on Exa's side will stop it. Cap the call count in your own code.
How to create an Exa API key
Getting an Exa API key takes a minute and no payment method. Sign up at the dashboard, and the key appears there; the onboarding flow hands you $10 of credits immediately and another $10 every month after. The same key works across every endpoint, because Exa does not scope keys per endpoint the way Apollo does.
How the key travels
One header, every endpoint.
- Sent as Authorization: Bearer $EXA_API_KEY.
- The same key reaches search, contents, answer, monitors and enrichment.
- Keys are managed from the Exa dashboard at dashboard.exa.ai.
- The MCP server can authenticate with OAuth instead, which is the better route for a shared workspace.
Before you need a key at all
Two ways to try the API without writing code.
- The playground at dashboard.exa.ai/playground/search runs real searches in the browser.
- The hosted MCP server at mcp.exa.ai/mcp plugs straight into Claude or an editor.
- There is also a Claude connector and a ChatGPT plugin, both on the free tier.
Where the Exa API documentation lives
Exa keeps its documentation and its API reference on the same host and splits them by intent: prose on the left, endpoint contracts on the right. The Exa API docs are unusually honest about cost, which is rare enough to be worth saying.
| Surface | Where | What it answers |
|---|---|---|
| Documentation | docs.exa.ai/docs | Quickstart, search types, highlights, best practices. |
| API reference | docs.exa.ai/docs/reference/search | The contract for every endpoint and parameter. |
| Billing and rate limits | docs.exa.ai/docs/admin/billing | Credits, invoicing, QPS and agent concurrency. |
| Deep Search | docs.exa.ai/docs/search/deep-search | How the multi-step modes work and what controls them. |
| Changelog | docs.exa.ai/docs/changelog | New modes and parameter changes. |
| MCP server | mcp.exa.ai/mcp | The same search, as a tool an agent can call directly. |
The best practices page is the one worth reading before you write anything, because it is where Exa explains how to budget latency and context, and why outputSchema adds a synthesis step with its own cost. Most of the money people waste on this API is spent in the first week, on default parameters nobody revisited.
Exa also ships an MCP server, and it is on the MCP page with the others in this directory.
Exa's own product walkthrough
Exa publishes this on its own channel, so it is Exa's account of Exa, not ours. It is here because a rate card cannot show you the thing moving, and a few minutes of the product is faster than any paragraph on this page at telling you whether the shape of it fits yours.
YouTube · Exa AI Labs Introducing Exa Websets - A breakthrough toward perfect search 1:43 · Published December 2024The Websets launch, which is the hosted product rather than the search API this page reviews. It is here because it shows the index behaving the way Exa sells it, and the API queries that same index. Exa's channel has no walkthrough of the API itself.
Published 3 December 2024 on Exa AI Labs, the channel Exa's own pages link to, and read on 13 October 2026. Nothing in it is a source for a price or a limit on this page: every figure in the tables above comes from an Exa page.
Strengths and limits
Exa is a research tool that happens to have a GTM use, and it is worth judging on that rather than against the enrichment providers.
What it does well
- Clean extracted page content rather than links, which is what makes it usable by an agent without a scraper behind it.
- Six search modes with published latency and published price, so the speed and cost trade is a parameter rather than a guess.
- No monthly floor, no seats, and over $120 a year of free credits with no card on file.
- Four indexes, covering the web, people, companies and scholarly works.
- A hosted MCP server, a Claude connector and a ChatGPT plugin, all available on the free tier.
Where it falls short
- Contact enrichment at $0.02 an email is far above the specialists here, so it is the wrong tool for bulk contact data.
- Asking for two content views bills two views, and nothing warns you.
- Agent concurrency of 50 is the real ceiling on deep research fan-out, and it does not move without an enterprise contract.
- Nothing caps spend, which cuts both ways on a pay as you go rate card.
- Results are pages, not records, so anything structured has to be synthesised, which adds its own cost.
Where Exa data comes from, and what you may do with it
The question that arrives late and expensively is not how good the data is, it is who is allowed to hold it. These are the fields each one returns, the coverage it claims and the compliance it publishes.
| Provider | Fields returned | Coverage | Compliance | Redistribution |
|---|---|---|---|---|
| Exa | Firmographics, Intent and news, Work email, Mobile phone | Global | SOC 2 Type II | Not stated |
None of these states a redistribution position on its pricing or docs pages. Internally that never matters. Put the rows in something your customers can see and it becomes the question your legal team asks first.
Two practical notes that apply to every provider on this page. A compliance badge describes the vendor, not your use of it, so a GDPR DPA does not give you a lawful basis for the outreach you send. And every one of these vendors runs its own opt-out, which means a person who asks you to delete their record has to be removed from your copy as well as from theirs.
If Exa is not the answer
Four providers in the Signal APIs listing that solve the same problem differently. Each one is a trade, and the trade is named.
Tavily
$0.008/creditThe closest like-for-like: web search for agents at one credit a query, with 1,000 free credits a month and an MCP server.
Firecrawl
$16/moWhen you need the page rather than the answer. Clean Markdown from any URL, from $16 a month with 1,000 free credits.
TheirStack
$49/moIf you were searching for hiring or tooling signals, buy the dataset rather than searching for it. Structured rows, published pricing.
The full set, organized by the reason people leave, is on the Exa alternatives page.
Exa against the obvious rival
Same rate cards, read side by side, with the arithmetic done on a worked volume rather than left to you: Exa vs TheirStack and Exa vs Tavily. Every pairing in the directory is on the compare hub.
Before you build against it
Five things to settle first, each one read off Exa's own pages. The ticks are remembered in this browser, so you can come back to a half-finished integration.
Who should actually buy this
Buy Exa when the signal you want is not in anybody's database yet. A competitor quietly changing its pricing page, a company publishing a post-mortem that names the tool it just ripped out, a founder saying something on a podcast: none of that is a field in Apollo or Clay, and all of it is findable here.
Do not buy it as an enrichment provider. At $0.02 an email it is level with Apollo and above most specialists in this directory, and the enrichment is a side product rather than the thing Exa is good at.
The practical pattern is Exa in front of a cheap enrichment step, not instead of one: search to find the accounts with a reason attached, then hand the resulting domains to whichever provider sells you contacts at a fraction of a cent. Start on the free tier and run a real query set through it, because at $10 a month of credits you can answer the question properly before you spend anything.
Exa is one of the providers in the agent-driven account research stack on this site, where the cost is worked out end to end at $0.09 a record.
Search is cheap. Knowing what to search for is not.
An agent with a search API and no thesis burns credits and returns noise. The teams getting value here wrote down the trigger first: what has to be true about an account before it is worth a call. Frontal builds that trigger into a running pipeline, inside your own tools.
Worked with 300+ companies. A senior operator runs your account.
What Exa users say, in their own words
The one part of this page that is not a vendor claim. Quotes are transcribed as written and linked to the thread.
Developers who evaluate it call it infrastructure, not a search box
I've evaluated both for safety-related AI work, and Exa was much more obviously built to be infrastructure: programmatic retrieval, extraction, structured results, semantic search, throughput controls, enterprise privacy, all that boring backend stuff. Kagi was much more consumer-facing, and its API offering is newer.
r/firefox · August 2026 · 14 points
Somebody who evaluated Exa against a consumer search product for real work, and the list they reach for is the list this page is built on: retrieval you call programmatically, extraction, structured results and throughput you can control. It is the clearest outside statement of what Exa is for, which is a retrieval layer underneath something else rather than a search engine a person looks at.
The thread is about why Mozilla picked Exa and the commenter calls their own answer speculation, so the part worth keeping is the evaluation rather than the conclusion about who won it.
The unit that decides a search API is requests per job, not price per request
services like SerpAPI and Tavily are too costly to be true, and has a tight upper limit of about 5k-15k requests per month. Assuming 1 request per session, it would mean we only can use the web search tool for about 15k times in a month. That simply isn't enough for an agentic system which might need to make several calls to do a single job.
r/LLMDevs · May 2025 · 4 points
A plan sized on sessions is sized on the wrong unit, because an agent makes several calls to answer one question. That is the argument for reading the research endpoint tiers on this page alongside the per-search rate: one question answered thoroughly can cost a hundred times what one search does, and the bill is set by the loop rather than by the rate card.
The monthly ceilings quoted here are this commenter's reading of two other vendors in 2025 and not anything this site verified. Take the shape of the complaint; the limits above are Exa's own, read from its rate card on 8 October 2026.
It searches its own index, and forum content is where you notice
I tried using Exa.ai's search API endpoint and noticed that the results are not as accurate as I expected. They seem to miss important links such as Reddit or forum posts that I would typically find through a Google search. [...] In the end, I am considering using the SERP API, as it relies on Google search results which are known for their quality and relevance.
r/Rag · May 2025 · 1 point
Exa searches an index it built rather than reselling somebody else's results, which is what makes semantic search and clean page content possible and is also what this commenter ran into. If the thing you need is the top of a Google results page, a SERP API is the honest answer and this is the wrong tool for it.
It is a single-point comment from May 2025 about an index that has shipped several times since, so read it as the question to ask in your own test rather than as a current verdict. Run the same query against both and compare what comes back.
14 threads read on 13 October 2026, searched by vendor name. Scores and dates are the comment's own. Nothing here is the only source for a price or a limit on this site: every figure in the tables above comes from a vendor's own page.
Exa API, answered
Is the Exa API free?
$10 of credits every month. Paid use starts at $4/1k searches.
How much does the Exa API cost?
Exa starts at $4/1k searches, which works out at $0.007 per auto search. Billing is pay as you go and free tier. Read from Exa's own pricing page on 19 October 2026.
What are the Exa API rate limits?
10 search QPS free, up to 25 on pay as you go. 50 agent concurrency on both.
How do I get an Exa API key?
Bearer token, or OAuth through the MCP server. The current steps are in Exa's own documentation, which is authoritative on anything that has changed since 19 October 2026.
Does Exa have an MCP server?
Yes, at https://mcp.exa.ai/mcp. It is listed with the others on the MCP page.