Scrape the AI Overview box as structured data.
The synthesized answer that sits above Google's blue links is now the first thing most searchers read — and it's invisible to every ranking tool built for ten links. cloro captures that box on demand: the answer text, each source it cites, the order it ranks them and whether it fired at all — returned as clean JSON or Markdown.
An AI Overview is rendered, not served.
The box is assembled client-side, appears for some queries and not others, and rewrites its wording between refreshes. Screen-scraping it by hand is a moving target. cloro renders each query the way a real searcher would see it and hands you the parsed result.
It doesn't always fire
The same keyword shows an AI Overview one day and plain results the next. cloro reports the trigger state explicitly, so an absent box is a data point — not a silent gap in your dataset.
The wording drifts
Google re-synthesizes the answer continuously. Stable field keys and clean text let you diff today's answer against last week's and catch the moment your brand drops out of the summary.
It's local and personal
A searcher in Berlin sees a different box than one in Chicago. Pass a country and device with the request and read the exact overview that audience is being shown.
Every part of the box, as a typed field
cloro breaks the rendered overview into named fields so you never parse HTML again.
answer
The synthesized answer
The full overview text, cleaned of interface chrome and expandable-section markup, ready to store or feed to a model.
citations[]
Ranked source list
Each link the overview cites, in the order it presents them, with domain, title and the resolved destination URL.
brands_mentioned[]
Named brands
Entities the answer names by hand, extracted from the prose.
triggered
Fire state
A boolean plus reason so a missing box is recorded, not lost.
follow_ups[]
Suggested prompts
The follow-up questions Google offers beneath the answer.
location · device
Request context, echoed back
The market and device the overview was rendered for, returned alongside the result so every stored record is self-describing and reproducible.
latency_ms
Render time
How long the live capture took, for your own SLAs.
Ask once. Get the whole box back typed.
Point the endpoint at Google AI Overview, pass your query and target market, and read a structured record — no headless browser, no proxy pool, no HTML parsing on your side.
- Answer text stripped of interface markup
- Citations ranked in the order Google shows them
- Explicit
triggeredflag when the box is absent - JSON for pipelines, Markdown for grounding models
# capture the AI Overview for a query, in one market curl https://api.cloro.cloud/v1/search \ -H "Authorization: Bearer $CLORO_KEY" \ -d '{ "engine": "ai_overview", "query": "best standing desk 2026", "country": "us", "device": "desktop", "format": "json" }' # → response { "engine": "ai_overview", "triggered": true, "answer": "Choosing a standing desk comes down to a stable frame...", "citations": [ { "rank": 1, "domain": "wirecutter.com" }, { "rank": 2, "domain": "rtings.com" }, { "rank": 3, "domain": "reddit.com" } ], "brands_mentioned": [], "follow_ups": ["how much should a standing desk cost"], "country": "us", "latency_ms": 3120 }
Illustrative: AI Overviews appear far more often on question-shaped, informational queries than on brand or checkout intent. Measure your own keyword set — cloro records the trigger state on every call.
Whether the box fires is itself a signal.
A keyword that surfaces an AI Overview is a keyword where the summary — not your listing — is the first answer a searcher reads. Tracking which of your terms trigger the box tells you where AI visibility work matters most, and where classic ranking still owns the click.
How one call resolves
You send the query
Engine ai_overview, a query, a target country and device. That's the entire request.
cloro renders it live
The query runs through a real render of Google for that market, so the overview appears exactly as a searcher there would see it — or doesn't.
The box is parsed
Answer text, ranked citations, named brands and follow-up prompts are extracted and mapped onto stable field keys.
You store the record
A typed JSON object — or ready-to-index Markdown — lands in your pipeline, deduplicated and safe to diff over time. If the box never fired, triggered:false is recorded and the call isn't billed.
From a captured box to a decision
Audit your citation share
Run a keyword set and see how often the overview cites your domain versus rivals — the AI-era equivalent of a ranking report.
Find the gap queries
Spot terms where the box answers fully without ever citing you, and prioritize the content that could earn a place in it.
Ground your own models
Feed the clean Markdown answer and its sources into a RAG pipeline as fresh, attributed context you didn't have to scrape yourself.
About AI Overview capture
What if the AI Overview doesn't appear for a query?
You still get a record. cloro returns triggered:false with the reason, so an absent box is stored as a fact in your dataset rather than a missing row. Calls with no overview aren't billed as a captured answer.
Do you return the sources the overview cites?
Yes. Every citation the box shows is returned in the order Google ranks it, with domain, title and the resolved destination URL — so you can measure citation share exactly.
Can I capture the overview for a specific country or device?
Yes. Pass a country and device with the request and cloro renders the overview the way a searcher in that market would see it. The context is echoed back on the response.
JSON or Markdown?
Both, per request. Use JSON for dashboards and databases; use Markdown when you're grounding an LLM or building a knowledge base and want clean, attributed prose.
How is this different from the classic SERP API?
The SERP API parses the ten-blue-links results — organic, ads, snippets, maps. This endpoint targets the AI Overview box specifically: its synthesized answer, citations and trigger state. Many teams pull both on the same keyword to see the full picture.
How am I billed?
Per successful call. A captured overview counts; an empty or failed result doesn't, and your live usage counter reflects exactly what you consumed.
Read the answer box like a database.
Spin up a key and capture your first AI Overview in minutes — answer, citations and trigger state, structured and ready to track.