SEO Data Bench/Guides/google-ai-overview-api
Is there an API for Google AI Overviews? What three routes actually return
Google publishes no AI Overview API. Three third-party routes claim to return the block: a rendered-page capture, a SERP API flag, and a two-step token exchange. Measured on 90 and 100 requests on the same day: how often the overview came back, with what, and at what price.
Written for people asking: Is there an API for Google AI overview?How do I get Google AI Overview text and sources through an API?Which SERP API returns the AI Overview?
Google offers no API for AI Overviews; every route is a third party reading the results page. On 15 September 2026, Cloro's rendered Google capture returned the AI Overview text and its cited sources on 87 of 90 requests where it was asked for, at $0.0028 a query; the three misses were queries where Google showed no overview. DataForSEO's live SERP endpoint flagged an AI Overview on 50 of 50 queries but returned its content on only 15, because the overview loads asynchronously and the cohort run did not request the async load. SerpApi's Google engine returned an AI Overview object on 50 of 50 queries, but as a page token that needs a second call to its AI Overview engine at $0.015. If you want the overview text and sources in one call, the rendered capture is the route that delivered it.
What Google offers
Nothing. Google’s Search Console reports AI Overview impressions inside ordinary Web search data and offers no endpoint for the overview itself. Every route below is a third party fetching or rendering a Google results page on your behalf, and Google’s terms restrict automated access; whether that fits your own position is a question for you, not for this page.
Three routes, measured on the same day
Cohort v1 is 50 US-English buyer queries for data APIs. The full prompt panel is 30 buyer questions captured three times each. Both ran on 15 September 2026; raw responses are on the evidence page.
| Route | Ask | Overview present | Overview content returned | Cost per query | Median latency |
|---|---|---|---|---|---|
Cloro rendered capture (monitor/google, include.aioverview) |
90 (30 prompts × 3) | 87 | 87, text plus cited sources plus citation pills | $0.0028 | about 4.6 s |
DataForSEO live SERP (serp/google/organic/live/advanced) |
50 | 50 (ai_overview item present) |
15 with text, 35 as an empty placeholder | $0.002 | 7.9 s |
SerpApi (engine=google) |
50 | 50 (ai_overview object) |
0 inline; a page_token for a second call to google_ai_overview |
$0.015 + $0.015 | 1.5 s + second call |
Reading the table:
- The rendered capture returned the block itself. Text, the list of cited URLs and the citation pills, in one response, because it renders the page as a browser would and waits for the overview to load. Its three misses were captures where Google did not show an overview at all, which happens on repeat fetches of the same query.
- DataForSEO tells you an overview exists more reliably than it gives you the content. Its response marks the overview item on every query, but the overview loads after the page, and unless the asynchronous load is requested the item is often a placeholder. DataForSEO documents an option for that load; the cohort run did not set it, which is why 15 of 50 carried text. Treat this as a route that can return the overview with the right parameter, at extra latency, not as one that failed.
- SerpApi splits it into two calls. The Google engine returns an
ai_overviewobject containing a page token; the text and sources come from the separate AI Overview engine at another $0.015. Two calls, about $0.03 a query, the most expensive route here.
What the overview data looks like
From the rendered captures: a text answer of a few hundred words, a sources list with position, title and URL, and citation pills that map sentences to sources. That is enough to compute, per query, which domains Google’s overview cites, which is what the weekly citation measurement on this site network is built on. Sources are URLs, often with text-fragment anchors (#:~:text=) appended; strip them before deduplicating.
Who each route fits
- You want the overview text and sources per query, in one call: the rendered capture.
- You already use DataForSEO for SERPs and can tolerate the async wait: request the async overview load and keep one provider.
- You already pay SerpApi and need overviews occasionally: the two-call route is fine; it is the price per query that argues against it at volume.
What this run cannot tell you
One day, US desktop, one query cohort. Whether DataForSEO’s async option returns content on every query was not measured, because the run did not set it. Overview presence varies by query, country and repeat, so the 87 of 90 figure is for these prompts on this day.
Next step
- Routes: Cloro monitor/google, DataForSEO Google SERP, SerpApi Google AI Overview.
- The rest of the SERP measurement, organic completeness and latency: SERP completeness and latency and cost.
Questions this page answers
Is there an API for Google AI Overviews?
Not from Google. The routes that return the overview are third parties reading the results page: Cloro renders the page and returns the overview text with its sources (87 of 90 requests on 15 September 2026, $0.0028 each); DataForSEO's SERP endpoint flags the overview and returns its content when the asynchronous load is requested (15 of 50 with content in our run, which did not request it); SerpApi returns a token you exchange in a second $0.015 call.
Which SERP API returns the AI Overview text and its cited sources?
On the cohort measured, Cloro's rendered capture returned both in one call; DataForSEO returned content on 15 of 50 queries without the async-load option; SerpApi required a second call. All three are pay per call with no subscription, at $0.0028, $0.002 and $0.015 plus $0.015 respectively.
How often does Google show an AI Overview on buyer queries for data APIs?
On 30 buyer prompts captured three times each on 15 September 2026, an overview appeared on 87 of 90 attempts; the three without one were repeat captures of two prompts. Overviews are the norm on these questions, not the exception.
Spotted an error or a changed price? Email corrections@seodatabench.com with the page URL and a source. Corrections are logged on the corrections page.