Most AI reads arented search result.This one reads the web.
Giving a model web access usually means paying someone to pass your question to a search engine and hand back what it returned. askFinz reads pages itself, keeps what they mean, and files each one as the kind of document it actually is — 30 collections, answered from a standing index rather than fetched while you wait.
research-and-data/ — works news-and-briefings/ — articles encyclopedia/ — entries industry-and-sector/ — documents markets-and-filings/ — filings medicine-and-clinical-research/ — records products-and-reviews/ — products property-and-construction/ — listings trademarks/ — marks code-repositories/ — repositories books-and-manuals/ — documents course-material/ — courses
- askFinz runs its own crawler and its own index — it reads pages first-hand rather than passing your question to a search engine.
- A call returns the matched passage and the address it came from, not a ranked list you then have to fetch and read.
- askFinz runs its own search and its own ranking, so an answer can draw on as many relevant results as the question needs — most of this market sells the first ten and bills for the rest.
- Every page is filed by what the document actually is — a judgment, a standard, a filing — across 30 collections, rather than as undifferentiated web pages.
- $1.00 per 1,000 searches with the extension or a paid plan, $0.75 as a top-up, $3.50 standalone. One provider matches that rate on its own index; the table below names them.
- Buy something else if you already know the URL and just need it read cleanly, or if ranked links with no page text are genuinely all you need. Both cases are argued further down, with links.
Four things that are true here and rare elsewhere.
None of these is a claim about being biggest or fastest. They are claims about shape. A library is not useful because it owns the most paper; it is useful because someone shelved the law reports with the law reports, and will hand you the page rather than the catalogue. Each of these is checkable on a page of this site.
Filed by what it is, not where it was found
A judgment, a standard, a filing and a clinical study are not the same kind of document, and flattening them into "web pages" throws away the structure that makes each one checkable. askFinz keeps each as its own kind of record, with the identifiers, jurisdiction and dates attached.
See every collectionRead ahead of time, not fetched on demand
A relay passes your question to a search engine and hands back what it returned, which means it can only reach what that engine chose to show. askFinz reads pages continuously and holds what they mean, so the answer is a lookup rather than a live fetch — and it can reach material no engine surfaced.
How the index worksThe passage comes back with the answer
Not a link to go and read, and not a summary you have to trust. The matched passage arrives with every result, and every record keeps the address it was read from, so any answer can be followed back to the publisher.
What the index holdsA platform, not an endpoint
Search, research, chat, code, news and the rest run on the same index, with one sign-in. That is the part no search API sells: a rate card gives you results to build on, not a place to do the work.
Every workspaceNot our opinion. The record.
Owning the index used to be an eccentric thing to do. Over two years the case for it stopped being an argument and became a series of events, none of which we had any hand in. Here they are, most recent first, with the source for each — move along the track to read back through them. Only the two at the front are ours, and they are marked.
- September 2026
A new way to keep what was read, for people and for agentsours
Holding the web affordably is the other half of the problem. What askFinz keeps is what a page means plus the address it came from, filed by what the document is, moving between hot, warm, cold and archived storage as it is asked for more or less. One index, answering with the passage and its source, whether a person or an agent is asking.
This page
- September 2026
askFinz builds the network instead of renting the capacityours
If owning an index is so plainly better, why does almost nobody do it? Because reading the web has meant renting a great many machines. askFinz built an Indexer OS instead, so the reading is shared across pools of ordinary hardware — a spare desktop, a container on a server someone already runs, a dedicated box. Capacity grows by adding a machine, not by moving up someone else’s plan.
This page. Rates and capabilities re-read 7 September 2026
- August 2026
Amazon ships an index of its own
Bedrock Web Search launches on “a web index operated by Amazon, spanning tens of billions of documents refreshed continually.” Anyone claiming that everybody else rents is now wrong; the true and sufficient claim is that most AI products do.
AWS product documentation
- April 2026
The list of independent indexes gets shorter
Stract is archived read-only; Gigablast has been offline since 2023. Of the handful of search indexes built from an operator’s own crawl, two of the named ones are now gone. Running one is not merely rare — it is getting rarer.
Reported by serp.fast
- December 2025 – July 2026
Relaying an engine turns out to carry legal risk
Google sues SerpApi over DMCA claims; a court dismisses the core claims in July 2026, with leave to amend part of them. The outcome matters less than what it exposes — a business built on passing queries to somebody else’s engine has a dependency it cannot settle itself.
Reported by serp.fast
- September 2025
Cloudflare names re-crawling as the waste
Announcing an index of its own, Cloudflare writes that for AI builders “crawling and recrawling unstructured content is costly, wastes resources.” Its answer is an index that sites opt into, so its reach is whatever sites choose to join.
Cloudflare blog, 26 September 2025
- August 2025
The budget option disappears
Microsoft retires the Bing Search API with limited notice, breaking products built on it. Much of this market ran on that one endpoint, and its replacement costs considerably more — a large part of why web access is priced as it is today.
Reported by Firecrawl and by serp.fast
- October 2024
The biggest AI product on the web launches on someone else’s index
OpenAI introduces ChatGPT search and says plainly how it works: it “leverages third-party search providers, as well as content provided directly by our partners.” Bought results, plus content licensed from publishers. At the time, that was simply how it was done.
OpenAI, 31 October 2024
The entry worth sitting with is the first one, because of who wrote it. In 2024 the biggest AI product on the web launched by leveraging third-party search providers, and said so plainly. Everything after it is the market finding out what that dependency costs — an endpoint retired at short notice, a lawsuit over relayed results, two independent indexes going dark. The conclusion is not ours to argue; it is what the record already says. What that looks like here is 30 collections you can open and read.
Many small machines, not one rented service.
Reading the web continuously is the expensive part of running an index, and it is the reason most products rent their results instead. askFinz spreads the work across pools of ordinary machines — a spare desktop, a container on a server already running, or a dedicated box booted from an image — each joining a pool and taking work when it has capacity.
Compute follows the work. A pool takes what it can handle and no more, so a busy hour spreads across more machines rather than queueing behind a fixed plan.
Storage is what a page means. What is kept is the meaning and the address it came from, not a copy of the web — which is why a stored page costs a fraction of what the original weighed.
Read under our own name. Requests identify themselves and are answerable to a published crawler policy — no rented proxy pool standing between us and the site being read.
The node programme is open — lend a machine, run it as a container , or boot a dedicated box from an image. Why we do not use a rented proxy pool is set out in how askFinz reaches a site.
At the floor, and honest about it.
Every rate below was read off the vendor’s own pricing page, and every capability off their own documentation, on 7 September 2026. The table is grouped by the thing that matters most and is hardest to see from a rate card: whether a provider holds an index of its own, borrows one, relays a search engine, fetches a page you already named, hands you an archive to process, or meters the web inside a model. Cheaper rows are in here rather than hidden underneath — most of them sell a call that never returns the words on the page, which is a column now instead of a footnote.
| Provider | What comes back | Filed by document type | Workspaces on top | From, per 1,000 | vs askFinz bundled |
|---|---|---|---|---|---|
| Holds its own indexRuns its own crawler and answers from what it holds — a library with its own shelves. The only group that decides what is on them. | |||||
askFinz | The passage that answered you, and the address to check it against — as many as the question needsIncluded | Shelved by what it is: a judgment comes back as a judgment, with its citation. 45+ collections | Open it in Search, keep it in Research, work in a browser extension or the desktop app | $0.75top-up; $1.00 with the extension or a paid plan, $3.50 standalone | — |
Parallel | Ranked links, with shortened extractsIncludedextracts, not the full page | —Ranked web pages | —An API endpoint | $1.00turbo and fast; covers the first 10 results, then $1.00 per 1,000 further results. Basic and advanced $5.00 | about the sameat 10 results a call. A call returning 100 costs about $91 per 1,000 on the same published rates |
Keiro | Ranked links. Page text costs more creditsIncluded3 credits; links alone cost 1 | —Ranked web pages | —An API endpoint | $2.40best tier; $4.00 and $7.20 below it. Links only $0.80 | 2.4× more |
Keenable | Ranked links, with long snippetsBilled extrasnippets, not the page | —Ranked web pages | —An API endpoint | $4.00pay as you go; $1.00 only on dedicated capacity | 4.0× more |
Yep | Ranked links, plus the sentence that matchedBilled extrathe matching sentence only | —Ranked web pages | —An API endpoint | $4.00advanced tier $8.00 | 4.0× more |
Brave Search API | Ranked links, each with a descriptionNot returned | —Ranked web pages | —An API endpoint | $5.00answers tier $4.00 plus tokens | 5.0× more |
Exa | Ranked links. Page text is billed per pageBilled extra$1.00 per 1,000 pages on top | —Ranked pages, matched by vector similarity | —An API endpoint | $5.00answer tier; search $7.00 for 10 results, then $1.00 per 1,000 more; deep $12.00, deep-reasoning $15.00 | 5.0× more |
Linkup | Links with content, or a composed answerIncluded | —Ranked web pages | —An API endpoint | $5.00standard depth; deep search roughly ten times this | 5.0× more |
Amazon Bedrock | Passages, returned inside BedrockIncluded | —Ranked web pages | —Inside Bedrock, with the rest of AWS | $7.00Amazon's own index, launched August 2026 | 7.0× more |
| Partly its ownRuns some crawling of its own and leans on an outside engine for the rest. | |||||
You.com | Ranked links. Page content is billed per pageBilled extracontents $1.00 per 1,000 pages | —Ranked web pages | —An endpoint, plus a consumer chat app | $5.001–100 results per call | 5.0× more |
Perplexity | Ranked links, with filtersNot returned | —Ranked web pages | —An endpoint, plus a consumer chat app | $5.00Search API, per 1,000 requests | 5.0× more |
Google Vertex AI Search | Results from Google's index, with groundingIncluded | —Your own data store, plus Google’s index | —A cloud console you configure | not per searchper query PLUS per GB indexed — no single per-1,000 figure | — |
| Relays a search engineHolds no index. Passes your query to a search engine and returns what came back. Cheaper, and a different product. | |||||
DataForSEO | A search engine's result page. No page textNot returned | —The engine's ranked links | —An API endpoint | $0.60queued mode; live calls $2.00 | cheaper, thinner call |
SearchAPI | A search engine's results — no page textNot returned | —The engine's ranked links | —An API endpoint | $1.00at volume; $4.00 at the entry plan | about the same |
Bright Data | A search engine's result pageNot returned | —The engine's ranked links | —An API endpoint | $1.30SERP API; $1.50 without a commitment | 1.3× more |
SerpApi | A search engine's results — no page textNot returned | —The engine's ranked links | —An API endpoint | $1.97at the largest published tier; $25.00 entry | 2.0× more |
Tavily | Sources gathered from other engines, with content and a summaryIncluded | —Sources from other engines, behind one summary | —An API endpoint | $5.00largest plan; $8.00 pay as you go, advanced double | 5.0× more |
Serper | A search engine's results — no page textNot returned | —The engine's ranked links | —An API endpoint | not per searchno public per-1,000 rate published | — |
| Metered by what you consume, not per searchSold as a pool you spend on whatever you do with it — reading a URL you already have, running a scraper, or a search — so there is no single per-search rate to set beside the rows above. Both publish their arithmetic; neither publishes where a search result comes from. | |||||
Firecrawl | One URL you name, as markdown. Search is billed from the same creditsBilled extraa search costs 2 credits, scraping each result costs 1 more | —The page you asked for, or ranked links | —An API endpoint | not per searchcredits, not calls — about EUR 5.60 per 1,000 searches on the entry plan and EUR 1.14 at the top one, or EUR 2.80 and EUR 0.57 per 1,000 pages. Published in euros, so no dollar figure here | — |
Apify | Whatever the scraper you picked collectsIncluded | —Whatever the scraper you chose collects | —A marketplace of scrapers you run | not per searchpriced per run and per result, not per search | — |
| A bulk archive you process yourselfNo queries and no ranking. A snapshot of the web delivered as files, which you store, parse and search on your own hardware. | |||||
Common Crawl | A monthly archive of raw pages. You process itIncludedraw, unparsed, months old | —Raw archive, unsorted | —Files you download | not per searchfree to download; you pay in storage and compute | — |
| Web access billed inside a modelNot an index you can query — the model's own access to one, metered per call by whoever runs the model, with the pages it read arriving as tokens you also pay for. Read the multiplier here as a rough guide only: it sets a per-call tool beside an index subscription, which is a different shape of purchase. Worth noting anyway that five companies publish a figure for the same verb and the spread runs six times end to end. | |||||
xAI web search | Searches, and opens pages, for the modelBilled extraarrives as tokens in the completion | —Whatever its search returned | —Inside that model's own product | $5.00per 1,000 web_search tool calls — the cheapest published figure in this group | 5.0× more |
OpenAI web search | Results passed to the model, inside the completionBilled extrasearch content tokens billed at model rates | —Whatever its search returned | —Inside that model's own product | $10.00web search, and the preview tool on reasoning models including gpt-5 and the o-series. $25.00 on non-reasoning models, where search content tokens are free | 10.0× more |
Anthropic web search | Results handed to the model, inside the completionBilled extracharged on top of token costs | —Whatever its search returned | —Inside that model's own product | $10.00per 1,000 searches through the API, on top of token costs | 10.0× moreand US-only data residency via inference_geo adds 10% to all Opus 4.7 and above token costs, which base model pricing does not show |
Google grounding | A grounded answer, not an index you can queryBilled extraarrives as tokens in the completion | —Whatever its search returned | —Inside that model's own product | $14.00per 1,000 grounded queries | 14.0× more |
Mistral web search | Results with citations, inside the model's replyBilled extraarrives as tokens in the completion | —Whatever its search returned | —Inside that model's own product | $30.00per 1,000 calls | 30.0× more |
How to read this. Check how many results a rate covers before setting two side by side: much of this market sells the first ten and meters everything after, so a question that has to weigh forty sources can cost several times the advertised figure. Then read the middle three columns — half the cheapest rows return no page text at all, and only askFinz files what it reads by what the document actually is or puts workspaces on the index rather than handing back an endpoint. Several rows beat askFinz at something: Parallel matches the price at ten results a call, Firecrawl reads a named URL askFinz will not, the relays are far cheaper for ranked links, and Common Crawl costs nothing if you own the hardware to process it — each of those pages says so. Every figure is the vendor’s best published self-serve rate, read from their own pricing page on 7 September 2026, matched on what the call returns and excluding free tiers. Bing’s Search API, which much of this market was built on, was retired in August 2025; the rest reprice often enough that you should check theirs before relying on this.
Five questions that settle it faster than a rate card.
- 01
Do you need the page, or a link to it?
The cheapest services hand back a search engine's ranked links. If your model then has to fetch and read each one, that fetch is the real cost — and it is not on the rate card you compared. Ask how many results the rate covers, too: a top-ten window is the norm, and a question that needs to weigh more than ten sources is priced accordingly.
Compare the rates, and what each call returns - 02
Does it matter what kind of document it is?
For general questions, no. For a judgment, a standard, a filing or a clinical study it decides everything: those carry identifiers, jurisdiction and status that a generic page index throws away.
See every collection and how it is filed - 03
Who owns what you are searching?
A provider relaying an engine can only reach what that engine chose to show, and their price moves when the engine's does. A provider with its own index sets both.
Owning an index versus renting one - 04
Is this a call in a loop, or work someone does?
If you are building an agent framework, an API with good integrations may save more in engineering time than it costs in rate. If people are doing the work, a workspace they can open beats an endpoint.
The workspaces built on the index - 05
What happens when the answer is questioned?
Ask whether you can get back to the source. An answer with the passage and its address survives being challenged; a summary of a summary does not.
How the index works, end to end
Affordable to run is why it is affordable to buy.
A search index has three running costs: reaching pages, understanding them, and keeping what you learned. Rent any of the three and the price of your product is set by somebody else’s margin — which is why so many AI products charge per web call, and why those calls cost what they do.
askFinz owns all three. Reading spreads across pools of ordinary machines rather than reserved capacity billed by the request, so capacity grows by adding a machine instead of moving up a plan. Understanding a page runs on the hardware in those machines, bounded by what the fleet already has rather than by a per-token bill. And what is stored is what a page means plus the address it came from, not a copy of the page — a fraction of what the original weighed.
None of that is charity, and none of it makes askFinz cheapest at any price: the matrix above shows one provider matching the bundled rate. What it does mean is that the rate is set by hardware we can add to, not by a contract we have to renew.
Compute you add to, not rent
A pool takes what it can handle and no more. Reading more of the web means another machine in a pool, so cost tracks hardware rather than a plan that has to be upgraded.
Storage of meaning, not of pages
What is kept is what a page means plus the address it was read from. That is a small fraction of what the page weighed, and it is what makes holding a standing index affordable at all.
Reading done once, reused forever
A page is read when it is found and re-read when it changes — not once per question. Every question after the first is a lookup, which is why the rate does not rise with how often you ask.
The point of keeping it cheap to run is that the people who most need an index rarely have a budget for one — a researcher, a small firm, a team automating something nobody has automated before. A rate that tracks hardware rather than a rented plan is what makes building on the web affordable for them, which is the argument for owning the thing rather than renting it. Owning an index versus renting one sets that out in full.
When something else is the better buy.
You need to fetch a named URL
askFinz answers from what it has already read. If your job is “give me this page, now”, a scraping service is the right tool. Compared with Firecrawl · with Apify
You want ranked links, as cheaply as possible
Relay services start well below anything here, because they hand back a search engine’s results rather than the pages behind them. What SERP APIs are · compared with SerpApi
You are building an agent framework
Several search APIs are built to be called from inside a loop you own, and their integrations save real engineering time. Compared with Tavily · with Exa
Every comparison on this site is written to survive the other company reading it. Rates come from their own pages, capabilities from their own documentation, and where a rival is cheaper or does something askFinz does not, the page says so. The full set is at compare, and the two category explainers are owning an index versus renting one and indexing versus scraping.
The ones worth asking first.
- Is askFinz the cheapest web index?
- It is at the floor rather than below it, and the honest answer depends on what the call returns. Among services that hold their own index and return the matched passage, askFinz's bundled $1.00 per 1,000 is the cheapest published rate, tied with one other. Services that return ranked links without the page text are cheaper — that is a thinner call, and a fair comparison says so. The full table, with every rate read off the vendor's own page, is on the pricing page.
- What makes this different from a search API?
- A search API gives your code results to reason over. askFinz gives an answer with the passage it came from, on an index filed by document type, inside workspaces you can actually work in. If what you want is an endpoint to build against, several of the services compared here are a better fit and the comparison pages say which.
- Does askFinz rent its search results from a search engine?
- No. The index is read and held by askFinz. That is unusual but not unique — a small number of others run their own index too, and the comparison pages name them rather than implying otherwise.
- How does the reading fleet keep costs down?
- Reading is spread across pools of ordinary machines rather than concentrated in rented capacity billed per request. Adding capacity means adding a machine to a pool, so the cost of reading more of the web tracks hardware rather than someone else's rate card. That is the mechanism behind the published rate.
- Can I use askFinz for crawling or scraping?
- Not directly. Scraping and crawling services take a URL you name and return its content; askFinz answers a question from material it has already read and filed. If your job is to fetch specific pages on demand, the crawling comparison explains which tools do that and why askFinz is the wrong answer for it.
Everyone else in that table sells you an endpoint.
A rate per thousand calls is the whole product for most of the rows above. Here it is one way in. The same index answers in askFinz Search, is read by the workspaces, and reaches the browser through the extension — so a price you can compare is attached to a product your team can actually open.
It answers, not just responds
askFinz Search reads this index directly. An answer arrives as the passage that addresses the question with the address it came from, rather than a list of links to go and read.
Try the searchThe workspaces read the same shelf
Research, Finance and the rest read the collections this index is filed into, so what you are comparing on price is also what your team opens on a Tuesday morning.
Every workspaceAnd it follows you into the browser
The extension puts the index and the models on the page you are already looking at — no tab to switch to, and on a compatible graphics card the models run on your own machine.
Get the extensionAnd the models are not metered either.
Multiple frontier models in one place, with no per-model subscription. The extension and the desktop app are one flat monthly price, and nothing you do inside them is metered — no per-token meter running while you work, and no cap to plan around. Put beside a search rate that bills per call and a model that bills per token, that is the part of the comparison the table has no column for.
Open a collection and see what is actually in it.
Every collection page publishes its own size, how it divides, and what one record holds — read from the running system rather than written down.