—cost / query
—search-API share of cost
—LLM synthesis share of cost
Static RAG-equivalent cost vs. actual answer-engine cost
Same LLM inputs and outputs, minus the live web-search API fee — this is what the exact same query would cost as a pre-indexed, no-live-search static RAG system. The gap is the live-search premium.
| Cost basis | Cost / query | Monthly cost |
|---|
| Static RAG-equivalent (LLM synthesis only, no live search fee) | — | — |
| Actual answer-engine cost (LLM synthesis + live search API) | — | — |
Cost by snippets retrieved (top-K)
Everything else held at the values above, swept across how many search results get stuffed into the LLM's context per query. More snippets can mean better-grounded answers, but every extra snippet is extra input tokens billed on every single query.
| Snippets (top-K) | Input tokens/query | Cost / query | Monthly cost |
|---|
How this connects to other tools
This page prices a live-search answer engine — a Perplexity / You.com / Bing Copilot-style pipeline where every query hits a third-party web search API before the LLM ever sees the question. That's a different architecture from a system built around a corpus you already own: if your retrieval step is a vector lookup against documents you indexed yourself, with no live search-API fee on any query, price it on the RAG Cost Calculator instead, or the RAG Chatbot Cost Calculator for a conversational interface with history on top of that same static corpus. If you're specifically weighing a knowledge-graph architecture instead of plain vector retrieval, the GraphRAG Indexing Cost Calculator prices the one-time extraction pass that builds it. And because every query here pays full input-token price for the same system prompt and overhead tokens on repeat, check whether prompt caching can cut that recurring cost on the Prompt Caching Savings Calculator. Note this is also unrelated to adding a search box to your own website or app — if that's what you need, that's typo-tolerant instant search over your own content via Algolia, Typesense or Meilisearch, priced on the Site Search API Cost Calculator.
How this calculator works
The AI Search / Answer Engine Cost Calculator starts from what actually happens on one query: the pipeline calls a live web search API and gets back a fixed number of snippets (top-K), each averaging some number of tokens per snippet. Those snippet tokens, plus the system prompt + query overhead tokens and 20 tokens for the user's own question text, add up to the total input the LLM has to read before it can answer — at the defaults, 8 snippets × 150 tokens + 300 overhead + 20 is 1,520 input tokens. That input is priced at the input price per million tokens, the output tokens (the answer plus its citations) are priced at the output price, and summing the two gives the pure LLM synthesis cost per query — $0.0078 at the defaults.
On top of that LLM cost sits a cost that a static RAG system never pays: the search API price, charged per 1,000 queries, converts to a flat per-query search fee that applies no matter how the LLM side is priced — $5.00 per 1,000 queries is $0.005 per query. Adding the two gives the total cost per query ($0.0128 at the defaults), and multiplying by queries per month gives the monthly cost — $12,800 at a million queries a month. The search-API share and LLM synthesis share show how that total splits between the two cost sources, and the search premium — search cost divided by LLM cost — states directly how much the live-search layer adds on top of what the identical query would have cost as a static, pre-indexed RAG system with no live search fee: roughly 64% at the defaults. Search-API pricing is a labeled illustrative default; substitute your actual contracted rate for a real budget.
How is a live-search answer engine's cost structure different from a static RAG cost calculator?
A static RAG system retrieves from a corpus you already indexed — the retrieval step is a vector lookup against your own database, and once you've paid to build that index, running a query against it costs essentially nothing beyond the embedding of the question itself. An answer engine in the Perplexity / You.com / Bing Copilot mold works differently: instead of a pre-built index, every single query triggers a live call to a third-party web search API, and that API charges per query or per 1,000 queries, every time, forever. There's no equivalent line item in a static RAG cost model, because static RAG has no live search step to pay for. This calculator adds that recurring search-API fee on top of the usual input/output token cost of feeding the returned snippets into the LLM, so the two costs stack rather than substitute for each other — you're paying for a search engine call and an LLM completion on every query, not one or the other.
Why isn't retrieving more snippets for a better answer free?
Every snippet you pull back from the search API and stuff into the LLM's context is input tokens, and input tokens are priced per token. Doubling the number of snippets you retrieve — going from, say, 8 to 16 — roughly doubles the token count contributed by search results, which increases the input side of the LLM bill in direct proportion. It doesn't change the per-query search API fee, which is typically charged per call regardless of how many results you ask for, but it does change everything downstream of that call. Teams tune top-K upward because more retrieved context tends to reduce missed citations and improve answer completeness, and that's a real, defensible reason to do it — but it's a token cost decision, not a free quality lever, and the cost scales linearly with however many snippets you decide to keep.
Which providers charge per-query search fees, and roughly how much do they cost?
Brave Search API, Tavily, SerpApi and Bing Search (via Azure) are the commonly used options for wiring live web search into an LLM answer pipeline, and all of them price on a per-query or per-1,000-query basis rather than a flat subscription. Roughly speaking, per-1,000-query pricing across these providers tends to land somewhere in the low single digits to around ten dollars, depending on the provider, the tier you're on, and whether you need extras like fresher indexes or higher rate limits — treat any specific number here as illustrative rather than current, since search-API pricing changes and varies by plan more than LLM token pricing does. The default in this calculator, $5 per 1,000 queries, is a labeled illustrative assumption in that range, not a quote from any single provider — swap in your actual contracted rate before using this for a real budget.
How does this differ from the RAG Cost Calculator and from a plain LLM pricing comparison?
The RAG Cost Calculator prices a system built around a corpus you control and have already indexed — documents you own, chunked and embedded once, retrieved by vector similarity with no per-query fee to any outside search provider. This calculator prices a different architecture: no pre-built corpus at all, just a live call to a third-party web search API on every single query, which is why it has a cost line — the search API fee — that the RAG calculator simply doesn't model, because static RAG doesn't have it. A plain LLM pricing comparison is one step further removed still: it prices only the model's per-token input/output rates with no retrieval step of any kind, static or live, so it's the right tool when you're just calling a model directly with a prompt and no external context. Use this calculator specifically when your architecture is 'search the live web on every query, then synthesize a cited answer from what comes back' — that's the Perplexity-style pattern with a cost structure distinct from both of the others.