Subscription figures are provider list prices recorded in treg.to’s own catalog grid; per-call prices are what treg.to charges today, with $0.000 added.
set up treg — https://treg.to/llms.txt
Using treg, get the top 10 Google organic results for best crm for startups in the United States, in English. Show me the price first, then list the ranking domains with their titles.
These take a query the way a person types it. Keep multi-word phrases together.
A result set is location specific. Leave it out and you get whichever default the provider picked.
Depth is the cost dial on every row here: ten results is one unit of work, a hundred is ten.
treg.to returns the cost before the call, so the agent can say what it will spend.
treg.to holds the provider keys. Neither you nor the agent sees them.
The provider's own rate, $0.000 markup, from a prepaid balance.
Charged per call. $1.00 free per new team, no card to start.
Already pay Hunter? Register it and those calls are never metered.
Another provider is a different word in the prompt, not a new integration.
No SDK, no OAuth dance per vendor, no seats.
treg.to does not choose for you. It hands ChatGPT this comparison, with the price shown before any call, and ChatGPT picks. Or you tell it how: "cheapest", "most reliable", "the one that takes what I have", or a provider by name.
ScrapeCreators at $0.00188
SerpApi at $0.015
Serpstat at $0.0005
Those units are not interchangeable: one call can return many results, so compare on the unit you will actually be billed in.
| Provider | Success | Median | Sample |
|---|---|---|---|
| 100% | 421ms | 1501 calls | |
| 100% | 3.4s | 331 calls | |
| 100% | 5.5s | 5304 calls | |
| 99% | 1.8s | 2419 calls |
Measured on treg.to traffic: real calls, real inputs, and sample sizes differ by provider. Live reliability, not a controlled benchmark.
| Provider | Price | Accepts | Success rate | Verified |
|---|---|---|---|---|
| $0.0005 per result | method, params, id, params.keyword, params.se, params.size | 100% (1501 calls) | unverified | |
| $0.00188 per call | query, region, date_posted, page | 99% (2419 calls) | 2026-07-28 | |
| $0.002 per call | keyword, location_code, location_name, language_code, depth, device | 100% (5304 calls) | 2026-07-28 | |
| $0.015 per found | engine, q, gl, hl, location, uule | 100% (331 calls) | 2026-07-28 | |
| no dollar rate published | type, phrase, database, display_limit, display_offset, display_sort | not yet measured | unverified |
treg call scrapecreators.x.v1-google-search --query query=austen allred
Swap the id for any provider above. All 6 endpoints behind this job, with their parameters and captured responses, are on the Google Keyword Data shelf.
From roughly 180 Reddit and X posts read in August 2026. The X half was almost entirely promotion; Reddit carried the signal, and thirteen posts from four confirmed vendor rings were excluded, including one account running the same question through three scraping subreddits with a different persona each time. These five are organic.
“My current take is that most “search APIs” are really context providers for LLM grounding.” r/AI_Agents, 2 points
What this page can do about it: This was the most useful distinction in the whole research pass, and it decides whether this page is for you. Tools that return cleaned passages for a model to read are solving grounding. The rows here return the result set itself, in order, with the domains that hold each position. If you need to know who ranks where, cleaned context will not tell you, and if you only need something true to quote, you are overpaying here.
“What bothers me mostly is that there's no pay-as-yo-go option for SerpAPI or Firecrawl as far as I can tell.” r/TypingMind, 3 points
What this page can do about it: The complaint that came up most often was about the shape of the bill rather than the size of it: a monthly plan is the wrong instrument for someone running twenty searches a day. Every row here is charged per call from a prepaid balance, at the provider's own rate with nothing added, so the honest counterpoint is that at that volume the price differences between providers are noise and the real cost is your setup time.
“The removal created a 10x increase in the workload for data collection.” r/AgentsOfAI, 204 points
What this page can do about it: This is the single best explanation of why a cheap looking per search rate can still surprise you. When one fetch stopped returning a hundred results, reading the top hundred became ten fetches, and every provider passes that through somewhere: as depth billed in tens, as rows, or as ten separate searches. Read the unit column above before the price column.
“APIs like SerpAPI have pretty limited free tiers, so I'm looking into alternative ways to handle search without running into those limits.” r/Playwright, 2 points
What this page can do about it: A new treg.to team starts with a dollar of prepaid balance and no card, which at these rates is hundreds of searches rather than a fortnight of a trial. What that does not buy you is a decision: the same dollar spread across three of these providers on your own queries is a better answer than any table, and it is the experiment this page would rather you ran.
“please be understandable and provide your take, examples and opinion, not just straight up promo bs” r/ProxyEngineering, 10 points
What this page can do about it: This page is one of those threads, so the only decent thing it can do is show its working. Every price above is read from the provider's own rate card or documentation on the date in the row, where a provider publishes no dollar price the row says so rather than guessing, and any reliability figure comes from live treg.to traffic rather than a benchmark we designed. What no comparison can tell you is which of these companies still exists in eighteen months. Nobody selling you a table knows that either.
DataForSEO charges a flat rate per request but bills depth in tens of results, and multiplies the price by five if you use advanced search operators. Serpstat bills one credit per returned row and still bills the one credit minimum when the result is empty. SerpApi bills per successful search and charges nothing for a failure or for a repeat it serves from cache.
It prices in API units, ten per line returned, bought in packages up front, so a full top hundred pull is a thousand units and what that costs depends on the package you bought rather than on a public per call rate. The comparison prints a price only where the provider publishes one.
Its light endpoint returns a trimmed, faster payload for when you only want the ranking URLs, while its full endpoint accepts the whole parameter surface, including an explicit location or coordinates, device, the search vertical and a starting offset, which is what you need for city level results or for anything past the first page.
A SERP API returns what Google returns for one query, already parsed: the organic results in order, with titles, URLs and snippets. You are not renting an index, you are paying for one search run somewhere else on the parameters you send. That is why it is priced per search rather than per month, and why the parameters that change what a person would have seen, the location, the language, the device and how far down the page you go, are also the parameters that change what you are billed.
The provider's own rate with $0.000 added by treg.to, taken from a prepaid balance rather than a subscription. The live figure per provider is in the comparison above, and the units differ: one row bills the request, one bills each returned row, one bills only the searches that succeed.
No, and conflating the two is the commonest mistake in the research behind this page. Those return cleaned text for a model to read. These return the Google result set itself, in position order, with the domains holding each slot. If the question is who ranks, you need this kind; if the question is what is true, you probably do not.
Because Google stopped serving a hundred results on a single page, so what was one fetch became ten. Providers pass that through as depth, as rows, or as separate searches, which is why the depth or size parameter is the real cost dial on every row here.
Yes, on the rows that take it. SerpApi accepts a location string or explicit coordinates with a radius, and DataForSEO accepts a location code or name. A national result set is not a local one, so if you are checking a local pack you have to say where you are standing.