GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
GeezerVison is showing quanticdata.io — Google search scraper API — $0.0005/result | QuanticData
All collectors
Google search scraper APISearch engines · v1.1.0 · $0.0004 / result $0.40 / 1K · pay per delivered result A Google search results API returns the organic block of a search as rows instead of a page you have to parse. Send a query, a country and a language: back come position, title, URL, breadcrumb, snippet, date and sitelinks, from Google, Bing or DuckDuckGo, and you pay only for the results actually delivered. By Aldo Morese, founder of QuanticData · Published · Updated $0.0005 per delivered result · $2 free every month · Failed runs never billed What it does What a Google search results API doesSearch results are the cheapest ranking signal there is, and the most annoying to collect: the markup changes, the consent screen fires, and one datacenter IP is throttled after a handful of queries. This endpoint hands you the parsed organic block and keeps the exit rotation, the consent cookie and the pagination on our side. Google is answered from a stateless HTTP tier — the no-JS results page — so a query costs a fraction of a rendered one and never queues behind a browser. Bing and DuckDuckGo are plain requests. Ask for 30 results and the collector walks the pages, merges them, drops duplicate URLs and stops when the engine runs out.
Input is meaning, not a URL
queryenginecountrylanglocation
InputsThe whole request. Anything you leave out falls back to the default shown in the catalog.
Outputs — 12 fields, one row per result What one result looks likeEvery delivered result carries these fields. Nullable means the source did not publish it — the field stays empty instead of being guessed.
Integration One POST, typed rowsBase URL curl -X POST https://api.quanticdata.io/v1/scraper/collectors/web_search/run \
-H "Authorization: Bearer $QD_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"best running shoes","engine":"google","country":"us","lang":"en","max_results":20}'
import requests
r = requests.post(
"https://api.quanticdata.io/v1/scraper/collectors/web_search/run",
headers={"Authorization": f"Bearer {QD_API_KEY}"},
json={
"query": "best running shoes",
"engine": "google",
"country": "us",
"lang": "en",
"max_results": 20
},
timeout=120,
)
for row in r.json()["payload"]["results"]:
print(row)
const res = await fetch(
"https://api.quanticdata.io/v1/scraper/collectors/web_search/run",
{
method: "POST",
headers: {
Authorization: `Bearer ${process.env.QD_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({"query":"best running shoes","engine":"google","country":"us","lang":"en","max_results":20}),
},
);
const { payload } = await res.json();
console.table(payload.results);
claude mcp add quanticdata \ -e QUANTICDATA_API_KEY=qd_live_your_key_here \ -- npx -y quanticdata-mcp # then, in the chat: > run the web_search collector with query="best running shoes" and engine="google" Example response POST /v1/scraper/collectors/web_search/run
$ curl $QD/web_search/run \
-H "Authorization: Bearer $QD_API_KEY" \
-d '{"query": "best running shoes", "engine": "google", "country": "us", "lang": "en", "max_results": 20}'
{ "status": "done", "count": 20,
"results": [
{
"title": "…",
"link": "…",
"display_link": "…",
"source": "…" } ],
"cost": 0.01 }
# 20 results × $0.0005 · nothing delivered, nothing charged
Try it Web search, running nowChange the input and run it against the live collector — nothing to install, no sign-up. Run it from your own code, on your own inputs Same collector, same rows — $2 of free API credit every month, no card.
$0.0005 / result4,000 results on the free $2 every month
Semantic inputquery, engine, country — no URL lists
Up to 100results per run, pagination handled for you
No browserread over HTTP/TLS — cheaper and faster than rendering
Pricing Google search results API pricing$0.0005 per delivered result. A run that delivers nothing costs nothing: blocked pages, challenges and retries are on us, and the $2 monthly allowance covers about 4,000 results before you spend anything. $0.0005per delivered result$0.5 per 1,000 delivered results
5,000 resultson the free allowance$2 every month, no card
Zero rowszero chargeblocks, captchas and retries are on us
−30%on volume tiersthe catalog returns your key's price
Pay as you go$0/mo
Starter$19/mo
Growth$79/mo
Scale$299/mo
Same wallet, same key and same $2 monthly allowance as every other Data API. Prices are launch pricing read live from the billing config — What people build with the Google search results APIThree shapes of work this endpoint was designed around. Rank trackingRun the same keyword daily per country and store the position of your domain and of every competitor above it. SERP research at scaleFeed a keyword list in and get the top-10 landscape for each: who ranks, with what title, with what snippet. AI groundingGive an agent live search results with the URL and snippet already separated, instead of an HTML blob to clean up. Google search results API versus rolling your ownThe differences that actually cost time when you build this in-house.
What people search forLive autocomplete demand around Web search, pulled with our own Keyword ideas collector. Why an agent cannot just call GoogleGoogle publishes a Custom Search JSON API, and it answers a different question than the one an agent asks. It queries a Programmable Search Engine — an index you configure — not the public results page, so what comes back is neither the ranking a user sees nor a complete view of the web. Its free tier is a hundred queries a day, which is a demo budget, not a retrieval budget. That gap matters most when a model is the consumer. A retrieval step that silently returns a partial index produces answers that are confidently wrong, and nothing downstream can tell. Delivering the organic block as typed rows — position, title, URL, snippet, date — gives a model something it can cite, and gives you something you can audit when it cites it badly. This is also the collector most often wired in as an MCP tool. An agent that can search before it answers stops relying on a training cutoff, and the per-result price means a chatty agent is a rounding error rather than a budget conversation. Limits, freshness and the legal bitUp to 100 results per run, merged across pages and de-duplicated by URL. Ask for more than the engine has and you get fewer rows and pay for fewer rows. Throughput is your plan's rate limit rather than anything about the collector: 20 requests/minute on pay-as-you-go (300 on real balance), up to 1,200 on the top tier. Results are live rather than cached, which is the point for grounding but means two runs minutes apart can legitimately differ — rankings move. If you are building a time series, store the collection timestamp with every row and treat the pair as the observation. Collecting publicly visible data is generally lawful in most jurisdictions, and courts have repeatedly declined to treat reading a public page as unauthorised access. Search snippets are third-party text: quoting them with attribution is ordinary practice, republishing them wholesale is not. Google's terms restrict automated access independently of any of that. None of this is legal advice — get some for your actual use case.
Sources and standardsThe platform documentation and standards this collector is built against — check any claim on this page against the primary source:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| You are visitor 01402605 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |