> ## Documentation Index
> Fetch the complete documentation index at: https://cloro.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use only the endpoint paths in https://cloro.dev/docs/skill.md. Do not derive a path from a docs page URL.
> For many requests, use the async API (POST /v1/async/task or POST /v1/async/task/batch). It has no sync surcharge.
> To call cloro as tools, use the MCP server at https://mcp.cloro.dev/mcp.
> Plan prices are at https://cloro.dev/pricing/. Credits for each request are at https://cloro.dev/docs/guides/providers.md.

# AI Overview changelog

> All cloro changelog entries for AI Overview, newest first.

See [every entry](https://cloro.dev/docs/changelog.md).

**17th November 2026**

**Google Search: expand the AI Overview in the HTML page**

You can now expand the AI Overview in the `include.html` page. Send [`include.aioverview.expand: true`](https://cloro.dev/docs/api-reference/endpoint/google/ai-overview#example-request) and the stored page shows the full AI Overview, as if **Show more** were clicked. This works on desktop only: on phones, Show more opens AI Mode. `result.aioverview` does not change.

**12th November 2026**

**Google AI Overview: product cards with merchant offers**

The [Google Search endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-google.md) now returns the product cards in an AI Overview answer as `result.aioverview.inlineProducts`, with title, price, store and rating. A card that links to a Google product viewer has a `productResultToken`: send it to [`POST /v1/monitor/google/product`](https://cloro.dev/docs/api-reference/endpoint/google/product) to get the merchant offers. See [AI Overview inline products](https://cloro.dev/docs/api-reference/endpoint/google/ai-overview/inline-products.md).

Google AI Mode [inline products](https://cloro.dev/docs/api-reference/endpoint/aimode/inline-products.md) now also have `rating`.

**21st October 2026**

**Async: the idempotency `409` returns the existing task ID**

When you reuse an `idempotencyKey`, the `409 RESOURCE_ALREADY_EXISTS` from [`POST /v1/async/task`](https://cloro.dev/docs/api-reference/endpoint/create-async-task) now has `error.details.taskId`: the ID of the task that already holds the key. If your submit request timed out before you received the `taskId`, resubmit with the same key and poll the returned ID. The [batch endpoint](https://cloro.dev/docs/api-reference/endpoint/create-batch-tasks.md) returns it too, except for a key repeated inside the same batch.

**Google: the AI Overview is expanded in the HTML**

When a [Google Search](https://cloro.dev/docs/api-reference/endpoint/monitor-google.md) request sends `include.aioverview` and `include.html`, the stored HTML now shows the AI Overview expanded, as it looks after a click on "Show more". Before, it was collapsed. The cost does not change.

**18th September 2026**

**Place cards carry `phone` and `website`, and `placeId` is now a Google ID**

Place cards render Call, Directions and Website buttons. `places[]` and `map[]` now read all three, on AI Mode and AI Overview alike:

```json theme={null}
{
  "title": "The Dagny Boston",
  "placeId": "/g/1tglgvbk",
  "address": "89 Broad St, Boston, MA 02110",
  "phone": "+18776865313",
  "website": "https://www.thedagnyboston.com/"
}
```

`address` is the full postal address from the Directions link. It used to be the short line printed on the card — a street line, a "city, region" line, or nothing at all.

`placeId` was a hash of the title and address. It is now the place's Google Knowledge Graph ID, the same id its `map` entry carries, so the two join on it. Two things change for you: the value differs from what you stored before, and it is omitted on a card Google did not geo-tag.

`phone` and `website` are omitted when the card renders no Call or Website button.

See the [places](https://cloro.dev/docs/api-reference/endpoint/aimode/places.md) and [map](https://cloro.dev/docs/api-reference/endpoint/aimode/map.md) schemas.

**18th September 2026**

**Google AI Overview ships place cards as `places` and `map`**

Local answers show place cards. Their Directions and Website buttons used to reach you in `sources`; the cards now come back as `result.aioverview.places` and `result.aioverview.map`, with the same structure as in AI Mode.

On both surfaces:

* `places[].link` is the place's Google viewer URL, the same URL as its entry in `sources`.
* `map[].link` is a Google Maps URL that opens the place, for example `https://maps.google.com/?cid=11340480041048787817`.

See the [AI Overview schema](https://cloro.dev/docs/api-reference/endpoint/google/ai-overview/places-and-map.md).

**22nd July 2026**

**Google AI Mode and AI Overview: France (`FR`) is now supported**

You can now send `country: "FR"` to the [Google AI Mode endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-aimode.md) and use `include.aioverview` on the [Google endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-google.md) for `FR` requests. Previously these were rejected as unsupported regions; regular Google Search already accepted `FR`. The [`/v1/countries`](https://cloro.dev/docs/api-reference/endpoint/countries) endpoint now lists `FR` under `model=aimode` and `model=aioverview`.

**8th July 2026**

**Google AI Overview: new `relatedLinks` field**

Google AI Overview responses now expose a `relatedLinks` array on `result.aioverview`. These are a citation chip's "View related links" flyout items — URLs Google groups under a pill that are **not** in the `sources` rail (for example a Google Shopping comparison link). Previously these rendered inline in `markdown` with no structured home, which made `markdown` appear to carry more URLs than `sources` / `citationPills`. Each related link now shares the `citationPillId` of its chip (so you can group it with that chip's citation pills) and carries `label`, `url`, and `domain`. The field is additive and omitted when no chip carries related links. See the [AI Overview schema](https://cloro.dev/docs/api-reference/endpoint/google/ai-overview/related-links.md).

**21st May 2026**

**Structured `citationPills` array on Google AI Overview and AI Mode**

Both Google AI surfaces now emit an additive `citationPills` array alongside the answer text and sources. Each entry is one (pill, source) pair carrying a per-source `label` (the source's own page title from the sources rail), a `citationPillId` that groups entries from the same chip, and per-source `url`/`domain`/`description`/`position`. Cross-provider iteration over AI surface citation pills now uses one shape.

```json theme={null}
"citationPills": [
  {
    "label": "Best laptops for programmers in 2026",
    "citationPillId": 1,
    "url": "https://example.com/best-laptops-2026",
    "domain": "example.com",
    "description": "A guide to the top laptops for software development this year.",
    "position": 1
  },
  {
    "label": "MacBook Pro for developers",
    "citationPillId": 1,
    "url": "https://example.com/macbook-pro-review",
    "domain": "example.com",
    "description": "Why the MacBook Pro is a popular pick for developers.",
    "position": 3
  }
]
```

When a pill cites N sources, the array contains N entries sharing the same `citationPillId` but carrying distinct per-source `label`, `url`, and `domain`. Group by `citationPillId` to recover the pill-level structure.

Markdown rendering is unchanged — inline `[anchor](url)` links remain the canonical in-text citation form. The `citationPills` array gives type-aware consumers per-source access without re-parsing markdown.

Additive change — existing consumers are unaffected. Learn more in the [AI Overview citation pills](https://cloro.dev/docs/api-reference/endpoint/google/ai-overview/citation-pills.md) and [AI Mode citation pills](https://cloro.dev/docs/api-reference/endpoint/aimode/citation-pills.md) documentation.

**19th May 2026**

**AI Overview ads now carry a `type` discriminator**

Every entry in `aioverview.ads[]` on the Google Search endpoint now carries an explicit `type` field. Mirrors the same convention already in place for top-level `ads[]` (added 13th May), so callers can route ads to per-sub-type rendering without re-implementing the price/store presence heuristic.

* **`type: "TEXT"`** — text/lead-gen ads. Carry `domain` + `description` (+ shared `position` / `title` / `url` / `image`).
* **`type: "SHOPPING"`** — shopping/product ads. Carry `price` + `store` (+ optional `old_price`, + shared fields).

Each ad is exactly one sub-type — the two sub-schemas are disjoint. Sub-type-exclusive fields are only present when they apply to that ad, matching what the Google SERP actually renders. `image` is the one field that appears in either sub-type (product photo on shopping cards, hero image on text ads), so consumers should treat it as optional regardless of `type`.

```json theme={null}
"ads": [
  { "position": 1, "type": "TEXT",     "title": "...", "url": "...", "domain": "dell.com", "description": "..." },
  { "position": 2, "type": "SHOPPING", "title": "...", "url": "...", "price": { "value": 1499, "currency": "$" }, "store": "Best Buy" }
]
```

Additive change — existing consumers ignoring the new field are unaffected. No opt-in, no extra credit charge. Learn more in the [AI Overview ads documentation](https://cloro.dev/docs/api-reference/endpoint/google/ai-overview/ads.md).

**19th May 2026**

**AI Overview and AI Mode markdown citations now match ChatGPT**

When you opt into markdown output, in-text citations from Google AI Overview and Google AI Mode are now rendered as **standard inline `[anchor](url)` links** in the `markdown` field — the same shape ChatGPT already uses.

```text theme={null}
... the iPhone 17 is the best choice for most people.[CNET](https://www.cnet.com/tech/mobile/best-iphone/)[The best iPhone to buy!!](https://www.youtube.com/shorts/z1aZ3CYcaRE)
```

Anchor text resolves via a deterministic fallback chain: matched source title → Google's pill-chip label → URL host. Multi-source pills (Google's `+N` chips) expand to N adjacent stacked links at the citation point. `result.markdown` is now fully self-contained — no parallel index resolution needed to render citations.

Learn more in the [AI Overview](https://cloro.dev/docs/api-reference/endpoint/google/ai-overview/citation-pills.md) and [AI Mode](https://cloro.dev/docs/api-reference/endpoint/aimode/sources.md) documentation.

**18th May 2026**

**AI Overview videos now carry full metadata**

`aioverview.videos[]` entries on the Google Search endpoint now populate `title`, `source`, `platform`, `date`, `thumbnail`, and `duration` whenever Google renders them. Previous responses returned only `url` for the vast majority of video cards because the extractor was matching stale Google class names.

`url` remains the only guaranteed field. `title`, `source`, `platform`, and `date` are present on roughly 98% of videos; `thumbnail` (\~60%) and `duration` (\~15%) appear only when Google renders the rich carousel preview. Check for field presence before reading.

No schema change, no opt-in, no extra credit charge — existing requests start receiving the richer payload automatically. Learn more in the [AI Overview documentation](https://cloro.dev/docs/api-reference/endpoint/google/ai-overview/videos.md).

**17th April 2026**

**Sponsored ad extraction for AI Overview**

Google AI Overview responses now include structured sponsored ad data when Google injects advertising inside the AI Overview. Ads are exposed as a new `ads` array alongside the existing `text`, `sources`, and `videos` fields.

Each ad includes:

* **Ad details**: Title, destination URL, domain, and description
* **Position tracking**: Position index within the AI Overview ad block

Ads also remain visible in `text` and `markdown` output for full transparency. No additional parameters required -- ads are automatically included when present.

Learn more in our [AI Overview documentation](https://cloro.dev/docs/api-reference/endpoint/google/ai-overview).

**5th February 2026**

**Updated Google Search pricing structure**

We've updated the Google Search endpoint baseline pricing to a more predictable tiered structure for multi-page requests.

**What's changed:**

* **Multi-page pricing** is now tiered instead of per page:
  * 2-3 pages: +1 credit (was +2-4 credits)
  * 4-10 pages: +2 credits (was +6-18 credits)
* **Base cost and AI Overview** remain unchanged:
  * Base request: 3 credits
  * AI Overview addon: +2 credits

**New pricing examples:**

* 1 page, no AI Overview: **3 credits** (unchanged)
* 1 page, with AI Overview: **5 credits** (unchanged)
* 3 pages, with AI Overview: **6 credits** (was 9 credits)
* 10 pages, with AI Overview: **7 credits** (was 23 credits)

Costs are more predictable, with reduced pricing for bulk multi-page extraction.

**11th January 2026**

We've expanded our geographical coverage across all Google endpoints:

* **Google Search**: Now available in all 250 countries worldwide
* **AI Mode**: Expanded from 58 to 211 countries
* **AI Overview**: Expanded from 59 to 230 countries

Remember to check the [model-specific country list](https://cloro.dev/docs/api-reference/endpoint/countries.md) before deploying to ensure availability for your target endpoint.

**16th December 2025**

**More fields extracted for AI Mode and AI Overview**

Google AI Mode and AI Overview endpoints now automatically extract rich structured data:

* **Places in AI Mode**: Location information with ratings, reviews, price levels, addresses, Google Places IDs, and operating status
* **Shopping cards in AI Mode**: Structured product data with currency-aware pricing, merchant details, ratings, and purchase links
* **Video content in AI Overview**: Videos with thumbnails, titles, duration, platform info, and source attribution

No additional parameters required. All structured data is automatically detected and included when available in responses.

Learn more in [AI Mode](https://cloro.dev/docs/api-reference/endpoint/monitor-aimode.md) and [AI Overview](https://cloro.dev/docs/api-reference/endpoint/google/ai-overview).

**31st October 2025**

**New dedicated endpoints**

Each AI model now has its own dedicated endpoint for better performance and clearer documentation:

* [Extract Google AI Overview](https://cloro.dev/docs/api-reference/endpoint/google/ai-overview) (via `POST /v1/monitor/google` with `include.aioverview`)
* [Extract Microsoft Copilot](https://cloro.dev/docs/guides/providers.md#unsupported-providers) (`POST /v1/monitor/copilot`)
* [Extract Perplexity](https://cloro.dev/docs/guides/providers.md#unsupported-providers) (`POST /v1/monitor/perplexity`)
* [Extract Google AI Mode](https://cloro.dev/docs/api-reference/endpoint/monitor-aimode.md) (`POST /v1/monitor/aimode`)
* [Extract ChatGPT](https://cloro.dev/docs/api-reference/endpoint/monitor-chatgpt.md) (`POST /v1/monitor/chatgpt`)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.