Exa vs Perplexity
Exa
Best for agent research $4/Perplexity
Best for raw search results at a flat request price $5/Exa vs Perplexity is closer than the brands suggest: both Search APIs return ranked pages with the text already extracted, both host an MCP server, and the difference is the meter. Perplexity charges $5 per 1,000 requests and lets a request carry five queries, so a batched query costs $0.001; Exa charges $4 to $15 per 1,000 searches by mode, with $10 of free credits a month. Pick Perplexity for volume and Exa for a free bake-off, deep-reasoning search and sustained concurrency. Run the same fifty prompts through both before deciding, because the index is the product and no rate card describes it.
Where they actually differ
Every value comes from the same record that drives the Signal APIs listing, so this table cannot disagree with the cards. Accented tags are data one provider returns and the other does not.
| Compare | Exa | Perplexity |
|---|---|---|
| What sets it apart | Web search built to be read by a model | Ranked web results at $5 per 1,000 requests, no tokens |
| Entry price | $4/1k searches | $5/1k searches |
| Unit cost | $0.007 per search, default auto type | $0.005 per search request |
| Billing model | Pay as you go Free tier | Pay as you go Credit packs |
| Free tier | $10 of credits every month | No free tier. Credits are bought in advance, and keys are blocked at a zero balance unless auto reload is on. |
| GTM motion covered | Signal Source Enrich | Source Signal |
| Data returned | FirmographicsIntent and newsWork emailMobile phoneWeb pages | Intent and newsWeb pages |
| MCP server | Yes https://mcp.exa.ai/mcp | Yes https://api.perplexity.ai/mcp |
| Interfaces | REST API MCP server n8n node | REST API MCP server |
| Auth | Bearer token, or OAuth through the MCP server | Bearer API key from the API console |
| Rate limits | 10 search QPS free, up to 25 on pay as you go. 50 agent concurrency on both. | Search 50 query units a second on every tier. Agent API 1 to 33 QPS by spend tier. |
| Coverage | Global | Global |
| Compliance | SOC 2 Type II | None published |
| Best for | Best for agent research | Best for raw search results at a flat request price |
Pick each one when
Exa
- You want to test on free credits: $10 a month, no card.
- Searches run in parallel and 50 agent concurrency matters.
- Some questions need a deep-reasoning search, not one pass.
Perplexity
- Volume decides it: $0.001 a query when five share a request.
- A flat rate per request suits you better than search modes.
- You also want a model to write the answer, via the Agent API.
Both run their own search, so judge them on the answers they return. Take a hundred of the queries your agent really sends, run them through one free tier and a small paid top-up on the other with the mode pinned, and count the results you could use without a second search.
What each one costs, tier by tier
Both publish a full rate card, so this comparison runs on numbers rather than on adjectives. Exa lists 3 tiers and Perplexity lists 4. Every figure is read off the vendor's own pricing page, and the pages they came from are listed at the foot of this one.
| The short version | Exa | Perplexity |
|---|---|---|
| Cheapest paid plan with the API | Developer, $4/1k searches | Search API, $5 per 1,000 requests |
| Tiers published | 3 | 4 |
| Free tier | $10 of credits every month | No free tier. Credits are bought in advance, and keys are blocked at a zero balance unless auto reload is on. |
| Unit cost at entry | $0.007 per search, default auto type | $0.005 per search request |
The cheapest paid plan is rarely the plan you end up on, because what moves you up a tier is usually volume rather than a feature. The two rate cards below are what you are choosing between.
Exa
Exa publishes 3 tiers, one of them free, and pay as you go with no minimum above the free allowance.
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
Perplexity
Perplexity publishes 4 tiers, none of them free, and pay as you go with no minimum.
Search API
- Ranked results, titles, URLs and extracted text
- No token costs; up to five queries a request
- Invalid, rate-limited and failed requests are not billed
Search API, fast
- Set search_type to fast
- Lower latency, same billing unit
- The cheapest search Perplexity sells
Agent API
- Each model at its published input and output rate
- web_search $0.0025, fetch_url $0.0005 per call
- Replaces Sonar Chat Completions
Enterprise
- Custom pricing and dedicated support
- Credits also sold through AWS Marketplace
What Exa and Perplexity cost at your volume
Put your own volume in. The model picks the cheapest published plan that covers it on each side, which is the question a rate card cannot answer and the one that decides the bill.
Exa
Priced on the volume you use, so the plan that covers a normal month is the one that decides the bill.
Perplexity
Priced on the volume you use, so the plan that covers a normal month is the one that decides the bill.
Plans are read from each vendor's own pricing page and the model picks the cheapest one that covers you, so these are pay-as-you-go list rates, before any volume discount you negotiate.
What a year costs at three volumes
The same plan-fit arithmetic as the model above, run out to a year, because an annual number is what a budget actually asks for.
Every column moves with volume, through a bigger plan or more seats.
| A year at | Exa | Perplexity |
|---|---|---|
| 1,000 a month | $0 Developer | $60 Search API |
| 10,000 a month | $720 Developer | $600 Search API |
| 50,000 a month | $4,080 Developer | $3,000 Search API |
These are list prices on the published plan that covers each volume, on the billing term each vendor publishes, so they are the number before you negotiate.
How this plays out once it is running
The products have converged. Perplexity's Search API returns ranked results with titles, URLs and extracted text and no generated answer, at $5 per 1,000 requests with no token costs. Exa returns ranked pages with the text already extracted at $4 per 1,000 for a lite search, $7 for the default auto mode and $15 for deep reasoning. For an agent that needs to read sources rather than receive prose, either one does the job.
What differs is how each one counts. Perplexity bills a request and rate limits a query: a request can carry five queries, so batching takes the price to $0.001 a query, and the flat 50 query units a second becomes 10 batched requests a second. Exa bills each search and caps throughput at 10 queries a second free and 25 on pay as you go, with 50 agent concurrency on both. Perplexity has no free tier at all; credits are prepaid and keys are blocked at a zero balance unless auto reload is on.
What each one is genuinely good at
These are the things that keep somebody paying after the first month, which is a different question from what the marketing page leads with.
Exa
A bake-off that costs nothing
Ten dollars of credits every month plus a $10 onboarding bonus, with no payment method on file and every endpoint available, including the hosted MCP server. At the lite rate that is 2,500 searches a month. Perplexity sells credits in advance only, so testing it starts with a purchase.
Search depth you choose per call
Lite at $4 per 1,000, auto at $7 and deep reasoning at $15, which runs a multi-step research process rather than one retrieval pass. A hard question has somewhere to go that is not a loop of shallow searches, and an easy one can run at the cheaper rate.
Concurrency built for an agent fan-out
Fifty agent requests at once on the free and pay-as-you-go plans, and 25 search queries a second on Developer. Perplexity's Search ceiling is 50 query units a second for everybody, which is generous for single queries and works out to 10 a second once you batch five.
Perplexity
A lower price per query than Exa, if you batch
Five dollars per 1,000 requests and up to five queries in each, so $0.001 a query, and the fast mode drops a request to $1 per 1,000. Exa's cheapest search is $4 per 1,000. Invalid, rate-limited and failed requests are not billed.
A limit that does not depend on what you spend
The Search API allows 50 query units a second with a burst of 50 on every tier, so a new account runs at the same speed as an old one. Exa's 25 a second needs the paid Developer plan.
A model as well as the search, if you want one
The Agent API runs models from OpenAI, Anthropic, Google, xAI and Perplexity itself, with web_search billed at $0.0025 a call on top of the tokens. When the job is an answer rather than a list of sources, the same account covers it.
Where each one falls down
Every provider on this site has a case it handles badly, and the people who find out are the ones who bought it for that case. These are the ones worth knowing before you sign rather than after.
Exa
The default mode is not the cheap one
Auto search is $7 per 1,000 and lite is $4, so a pipeline that never sets the mode pays 75% more than it has to on queries that need no reasoning. Pin the mode the way you would pin Tavily's search depth.
Contact data is a side product
Exa sells email enrichment at $0.02 and phone at $0.07, outside the search rate card. That is a convenience for an agent that already has the key, not a reason to treat Exa as an enrichment provider.
Perplexity
No free tier, and a blocked key at zero
Credits are bought in advance and Perplexity blocks the API keys when the balance runs out. Leave auto reload off on an experimental key and a runaway loop stops there; leave it off in production and a blocked key looks like an outage.
The Sonar migration is not optional
Perplexity's migration guide says Sonar Chat Completions support ended on September 27, 2026. Synchronous calls are being reformulated as Agent API requests and asynchronous Sonar calls no longer work, so an old integration is running on a different meter whether or not anybody migrated it.
The Agent API meters tokens again
The Search API has no token costs, but the Agent API bills each model at its published rate plus the tool calls, and starts at 1 request a second on Tier 0 until $50 of credits have been bought.
Using Exa and Perplexity together
Teams comparing these two often end up running both, and the arrangement below is the one they settle on.
Running both is cheap enough to be the default while you decide. Exa's free credits cover the first 2,500 lite searches, and fifty test queries through Perplexity's Search API cost five cents at the batched rate, once credits are bought. Compare what each one returns for your own prompts, because that is the only number neither vendor publishes.
If you keep both, split by the job rather than by the price. Perplexity's batched Search API for the bulk lookups that run on a schedule, where $0.001 a query adds up to the saving, and Exa for agent fan-outs and the questions that need a deep-reasoning search.
Both host MCP servers, at mcp.exa.ai and api.perplexity.ai, so an agent can hold both tools at once and let the prompt decide. Log Perplexity's usage.cost.total_cost on Agent API calls and Exa's mode on every search, or the split will drift toward whichever tool the agent happens to prefer.
Exa or Perplexity, for you
Five questions, answered from the same records as the rest of this page. Nothing is sent anywhere and there is no result to email yourself.
Each answer leans one way. The recommendation appears here once you have picked at least two.
A tool like this can only weigh what is on the page. It does not know your workload, and the one test that does is the bake-off on this page: your own rows, queries or records, run on the cheapest entry each side offers.
Where an answer leans on a certification or an integration, it means that vendor publishes it on the pages this directory read, which is not the same as the other one lacking it. The sources are listed at the foot of the page.
Where the data comes from, and what you may do with it
The question that arrives late and expensively is who is allowed to hold the data. 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, Web pages | Global | SOC 2 Type II | Not stated |
| Perplexity | Intent and news, Web pages | Global | None published | 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 rather than 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.
Moving between Exa and Perplexity
Most readers of this page are already on one of these two, and the order below catches the expensive mistakes while they are still free.
Measure the thing you are about to lose
Replay 100 of the queries, URLs or lookups you really send through Exa and record the usable results, the failures and what each one cost. Without that baseline every provider looks cheaper per call than the one you are paying for today.
Check which fields change
Perplexity does not return firmographics, work email and mobile phone, which Exa does. If anything downstream reads those fields, the switch changes your pipeline as well as your vendor.
Rewrite the auth and the limits, in that order
Exa authenticates with a bearer token, or OAuth through the MCP server. Perplexity uses a bearer API key from the API console.
The limits are the part that bites later. Exa's limits: 10 search QPS free, up to 25 on pay as you go. 50 agent concurrency on both.
Perplexity's limits: search 50 query units a second on every tier. Agent API 1 to 33 QPS by spend tier. A loop tuned to the first will either crawl or get throttled on the second.
Run both for one billing cycle
Keep the old key live and route a slice of real traffic to the new one. A month is the shortest honest test, because credit expiry, rollover and the overage rate only show up at renewal and those are where the surprises live.
Cancel on the renewal date
Annual seats and prepaid usage rarely refund mid-term. Check what the contract says about the time you have already paid for, and time the switch to the renewal date.
The step people skip is the first one, and it is the only one that cannot be done after the fact. Once the old key is off you have nothing to compare the new one against, so a provider that is quietly worse on your workload looks like a provider that is fine.
What practitioners say about Exa
The one part of this page that is not a vendor claim. Quotes are transcribed as written, linked to the thread, and nothing here is the only source for a figure in the tables above.
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 Agent API 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.
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.
Where each one sits in a working pipeline
Neither of these is bought in isolation. These are the worked stacks on this site that use one or both, with the cost run end to end.
The wider field for both
Sometimes the answer is neither, and the reason you are comparing these two points somewhere else entirely: Exa alternatives and Perplexity alternatives both start from the reason people leave.
Exa alternatives
3Search designed to be read by a model. The reasons to leave are price per search and the shape of the index.
See the alternatives →Perplexity alternatives
4This page is about the Perplexity API, not the Perplexity app: the Search API at $5 per 1,000 requests and the Agent API that replaced Sonar.
See the alternatives →Everything in Source
28The full category these two sit in, filtered by data returned, billing model and entry price.
Browse the category →Related comparisons
The 52 providers behind every pairing here are in the main listing.
Pairings that share a side with this one: Exa vs TheirStack, Exa vs Parallel and Exa vs Tavily. Every comparison in the directory is on the compare hub.
Exa vs TheirStack
Live web research against structured hiring and technology signal.
Compare them →Exa vs Tavily
Two search APIs built for agents, priced within a tenth of a cent of each other.
Compare them →Exa vs Parallel
Two agent search APIs that price per request, not per token. The cheap mode costs $1 per 1,000 on one and $4 on the other, and neither is the default.
Compare them →Testing providers one at a time? Run the waterfall in Clay.
Clay runs a waterfall across 150+ data providers from one table, without a separate contract with each. A lookup that finds nothing costs no data credit, and the free plan includes 500 actions a month.
Frontal is a Clay Elite Studio Partner.
Exa and Perplexity, answered
Read from the same records that drive the table above.
Is Exa or Perplexity cheaper?
Exa is cheaper to start, because its free tier carries the API: $10 of credits every month. Perplexity starts at $5/1k searches. Per search, Perplexity is cheaper: $0.005 per search request, against Exa's $0.007 per search, default auto type.
Can I try Exa and Perplexity for free?
Exa: $10 of credits every month. Perplexity: No free tier. Credits are bought in advance, and keys are blocked at a zero balance unless auto reload is on.
What are the rate limits on Exa and Perplexity?
Exa: 10 search QPS free, up to 25 on pay as you go. 50 agent concurrency on both. Perplexity: Search 50 query units a second on every tier. Agent API 1 to 33 QPS by spend tier.
Do Exa and Perplexity both have MCP servers?
Both do. Exa: https://mcp.exa.ai/mcp. Perplexity: https://api.perplexity.ai/mcp.
Which is better, Exa or Perplexity?
Exa vs Perplexity is closer than the brands suggest: both Search APIs return ranked pages with the text already extracted, both host an MCP server, and the difference is the meter. Pick Perplexity for volume and Exa for a free bake-off, deep-reasoning search and sustained concurrency.
What are the downsides of Exa and Perplexity?
Exa: the default mode is not the cheap one; contact data is a side product. Perplexity: no free tier, and a blocked key at zero; the Sonar migration is not optional; the Agent API meters tokens again. The Limits section above has each one in full.
Can you use Exa and Perplexity together?
Running both is cheap enough to be the default while you decide. Exa's free credits cover the first 2,500 lite searches, and fifty test queries through Perplexity's Search API cost five cents at the batched rate, once credits are bought.
Can I migrate from Exa to Perplexity without losing data?
Not without losing a field. Perplexity does not return firmographics, work email and mobile phone, which Exa does, so anything downstream that reads those fields has to change. Either way, replay a hundred real queries through both and count the usable results before you switch.