> ## 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.

# ChatGPT changelog

> All cloro changelog entries for ChatGPT, newest first.

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

**19th November 2026**

**ChatGPT: what each inline product card is**

ChatGPT shows brands, companies, software, places and ideas in the same cards as shop products. Each product in [`inlineProducts`](https://cloro.dev/docs/api-reference/endpoint/chatgpt/inline-products) now has `kind` and `entityCategory`. `kind` is `product` for a shop product, `entity` for a named entity such as a brand, and `row` for any other card. `entityCategory` is the category that ChatGPT gives to the entity in the card title, such as `brand` or `tv_show`, or `null`. To keep only shop products, filter on `kind: "product"`.

`price` now holds only a price. Before, a card for a business could have its rating or address in `price`. That line now stays in `subtitle` or `description`.

**19th November 2026**

**ChatGPT: call-to-action links on product cards**

A gpt-6 product card can show a call-to-action line, such as "Acheter chez TennisPro". Each product in [`inlineProducts`](https://cloro.dev/docs/api-reference/endpoint/chatgpt/inline-products) now has `ctaLinks`, with the label and URL of each merchant link on that line. Use it to tell these links apart from citation chips (`citationPillIds`) and product sheet offers (`offers`). A product with no call-to-action line has `ctaLinks: []`. `url` does not change.

**2nd November 2026**

**ChatGPT: answers kept when ChatGPT does not search or cite**

The [ChatGPT endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-chatgpt.md) forces web search, and it used to fail any attempt that showed no sign of search. Two things changed:

* An answer where ChatGPT searched but cited nothing now succeeds, with empty `sources` and `citationPills`.
* If ChatGPT does not search on attempts 1 and 2, cloro keeps the answer from the third attempt on, searched or not.

Successful responses can now have empty `sources`, `citationPills`, and `searchQueries` even without `disableWebSearch`. Retrying these prompts rarely changes the result. See [Why are `sources` and `citationPills` empty when web search is forced?](https://cloro.dev/docs/api-reference/endpoint/monitor-chatgpt#why-are-sources-and-citationpills-empty-when-web-search-is-forced)

**29th October 2026**

**ChatGPT: product rationale and reviews**

Set `include.productDetails: true` with `include.shopping: true` on the [ChatGPT endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-chatgpt.md) to get the "What to know" rationale and the "What people are saying" reviews that ChatGPT shows when you open a product. They come back as `productDetails` on each product in `shoppingCards` and `inlineProducts`, and on each [entity listing](https://cloro.dev/docs/api-reference/endpoint/chatgpt/entities.md) in `entities[n].product`. This adds +2 credits to the request, on top of the +2 credits for `include.shopping`. See [product details](https://cloro.dev/docs/api-reference/endpoint/chatgpt/product-details.md).

**ChatGPT: all offers on shopping products**

`offers` on shopping-card and inline products now has every offer ChatGPT shows under "Compare offers". Before, it had only the first one. Answers from ChatGPT's mobile interface now have `offers` and `url` too, as desktop answers already did.

**ChatGPT: gpt-6 product cards are in `inlineProducts`**

Each gpt-6 product card is now an inline product. A card with a listing has it in [`inlineProducts`](https://cloro.dev/docs/api-reference/endpoint/chatgpt/inline-products), not in `entities[n].product`. An entity keeps its listing only when it is outside a card. A card with no listing is an inline product too: its `product` comes from the card (title, link, price text, badge, subtitle, description, "Label: value" lines such as "Best for: …" in `attributes`, and image), with no `id` and no `offers`. Each card also has `citationPillIds`: the `citationPillId` of each citation chip in the card, so you can find in `result.citationPills` which sources back each product.

**16th October 2026**

**ChatGPT: entities now have their product listing**

When ChatGPT attaches a product listing to an entity, the [ChatGPT endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-chatgpt.md) now returns it as [`entities[n].product`](https://cloro.dev/docs/api-reference/endpoint/chatgpt/entities): the price, the URL and the merchant offers, in the same structure as a shopping card product. It needs `include.shopping: true`, at no extra cost over that add-on.

**14th October 2026**

**ChatGPT: multi-turn conversations**

The [ChatGPT endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-chatgpt.md#multi-turn-conversations) now accepts `prompt` as an array of up to 5 prompts. ChatGPT answers them in order, in the same conversation, and `result` is an array with one response for each prompt. Use it to measure what ChatGPT says, cites and advertises after the first answer.

```json theme={null}
{
  "prompt": ["What are the best running shoes for flat feet?", "Which of these costs less than $100?"],
  "country": "US"
}
```

Each prompt after the first costs +1 credit. A `prompt` string works as before and returns one object.

ChatGPT currently shows ads only in answers to a follow-up prompt, not in the answer to the first prompt of a conversation. To get [`result.ads`](https://cloro.dev/docs/api-reference/endpoint/chatgpt/ads), send two or more prompts with `include.ads: true` and `legacy: true`, and read the ads from the second response or a later one. Follow-ups on the default mobile-web interface return ads far less often.

**10th October 2026**

**ChatGPT: the follow-up form is now in the response**

ChatGPT now ends many answers with a form that refines the prompt, such as "What's your budget?" with a list of ranges. The [ChatGPT endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-chatgpt.md) returns it as [`result.followUpForm`](https://cloro.dev/docs/api-reference/endpoint/chatgpt/follow-up-form), with no flag and at no extra cost: the questions, their options, the one ChatGPT selects by default, and the follow-up prompt it would send.

`followUpForm` is `null` when the answer has no form. The form text no longer shows in `text` and `markdown`.

**24th September 2026**

**ChatGPT: Czech Republic (`CZ`) is supported again**

The [ChatGPT endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-chatgpt.md) accepts `country: "CZ"` again. We removed it on 30th June 2026 because ChatGPT showed a login wall to anonymous users from Czech IPs. ChatGPT no longer shows that wall, and answers for `CZ` are localized to the Czech Republic. The [`/v1/countries`](https://cloro.dev/docs/api-reference/endpoint/countries) endpoint lists `CZ` under `model=chatgpt` again.

**2nd September 2026**

**ChatGPT: opt out of forced web search with `disableWebSearch`**

The [ChatGPT endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-chatgpt.md) forces ChatGPT's web search on every request. Set `disableWebSearch: true` and cloro returns the answer ChatGPT gives on its own, searching only when it decides to. Most prompts then come back without search, so `result.sources`, `result.citationPills`, and `result.searchQueries` are often empty, and the answer text can differ from the search-forced one. Use it to see what ChatGPT says without search, and keep the default to measure citations. The cost is unchanged, and requests that do not send the flag behave exactly as before.

**28th August 2026**

**ChatGPT: request the legacy interface with `legacy`**

The [ChatGPT endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-chatgpt.md) accepts a `legacy` boolean. Set it to `true` and cloro asks ChatGPT for its legacy desktop interface instead of the mobile-web one that now serves almost all traffic. That interface streams the answer as an event stream, so `result.model`, `result.searchQueries`, and `result.mapSearchQueries` come back filled in rather than empty. Unset, requests behave exactly as before.

> [!WARNING]
>
> This is a temporary workaround, not a supported switch. OpenAI decides which interface it serves and is rolling out mobile-web as the default, so `legacy: true` is best-effort and can stop working without notice. Keep your parsing working for both shapes: even with the flag set, treat `result.model`, `result.searchQueries`, and `result.mapSearchQueries` as possibly empty, and handle `rawResponse` in both the event-stream and HTML-fragment shapes.

**26th August 2026**

**ChatGPT: the mobile-web format now serves 98% of responses**

OpenAI completed the rollout of the mobile-web response format on **25 August 2026**. It served approximately 10% of successful ChatGPT responses through early August, approximately 50% between 18 and 24 August, and **98%** from 25 August.

Nothing changed in the cloro API. The effects are the ones in the 21st July 2026 entry below: `result.model`, `result.searchQueries`, and `result.mapSearchQueries` come back empty, `result.sources` holds fewer entries, and `rawResponse` uses the HTML-fragment shape. The answer `text` / `markdown` and inline `citationPills` are unaffected.

> [!NOTE]
>
> An empty field does not mean the field is gone. Providers have restored this kind of metadata later, so keep your parsing for `result.model`, `result.searchQueries`, and `result.mapSearchQueries` in place.

OpenAI selects the format per request on their side. cloro replicates a real user and does not force a particular interface, so we cannot select the event-stream format for you.

**21st July 2026**

**ChatGPT: new mobile-web response format**

OpenAI now serves a share of logged-out ChatGPT traffic through a new mobile-web format that streams the answer as HTML fragments rather than the usual event stream. On responses served this way:

* `rawResponse` (when you opt in) has a different, HTML-fragment shape alongside the existing event-stream shape.
* `result.model`, `result.searchQueries`, and `result.mapSearchQueries` come back **empty** — the mobile format carries none of the stream metadata these are parsed from.
* `result.sources` is **shorter**; the format exposes fewer full source entries.
* The answer `text` / `markdown` and inline `citationPills` are **unaffected**.

Which format OpenAI serves is decided on their side, per request. cloro replicates a real user, so it does not — and by design should not — force a particular interface; a share of responses will therefore arrive in the mobile-web format.

> [!WARNING]
>
> Fields that were previously always populated can now be empty on mobile-web responses. Treat `result.model`, `result.searchQueries`, and `result.mapSearchQueries` as possibly empty, and expect fewer entries in `result.sources`. If you consume `rawResponse`, handle the HTML-fragment shape in addition to the event-stream shape.

**20th July 2026**

**ChatGPT: `visibility`, `adsResponseIndex`, and `rendered` on ads**

Each ad in `result.ads` (set `include.ads: true`) now carries three fields that separate what OpenAI **served** from what the user actually **saw**. OpenAI serves candidate ads but the interface renders at most one; previously `result.ads` listed the served candidates with no way to tell which was shown. `rendered` is `true` only for the ad displayed as a visible card, so you can count real impressions instead of the array length. `visibility` exposes OpenAI's serving status (`allowed`, or `hidden` when an ad was filtered), and `adsResponseIndex` gives the ad's served slot position. The fields ride the existing `include.ads` flag, so there is no new parameter and no extra credit cost. See the [ChatGPT ads schema](https://cloro.dev/docs/api-reference/endpoint/chatgpt/ads.md#served-vs-shown).

**10th July 2026**

**ChatGPT: new `mapSearchQueries` field**

The [ChatGPT endpoint](https://cloro.dev/docs/api-reference/endpoint/monitor-chatgpt.md) now exposes a `mapSearchQueries` array on `result` when you set `include.searchQueries: true`. When ChatGPT renders a map block for a local-intent prompt (e.g. "best coffee shops in San Francisco", "plumbers near me"), it fires a separate query at its maps tool to gather the businesses behind `result.map`. That query previously lived only in the raw stream. It now has a structured home, distinct from `result.searchQueries` (the web-search fan-out), which the two can diverge on for the same prompt. The field rides the existing `include.searchQueries` flag, so there is no new parameter and no extra credit cost. It is additive and omitted when no map appears in the response. See the [ChatGPT response schema](https://cloro.dev/docs/api-reference/endpoint/monitor-chatgpt.md#response-schema).

**30th June 2026**

**Czech Republic (CZ) targeting disabled in ChatGPT**

We've removed `country: "CZ"` support for the ChatGPT endpoint. ChatGPT no longer allows anonymous access from Czech IPs — every request is met with a login wall, which scrapers cannot pass through. Requests with `country: "CZ"` to `/v1/chatgpt` will now return an unsupported-country error instead of silently failing.

> [!WARNING]
>
> If you target CZ on other scrapers, double-check the results you're getting back. Some providers fall back to proxies in neighboring countries when CZ-resident proxies are unavailable, which can skew localized answers.

**24th June 2026**

**State-level geo-targeting for AI endpoints**

You can now target a specific US state when querying ChatGPT, Copilot, Perplexity, Gemini, or Grok. Pass the USPS two-letter code as the `state` parameter alongside `country: "US"` and cloro routes the request through a proxy in that state — giving you localized results at the sub-country level.

```json theme={null}
{
  "prompt": "best electricians near me",
  "country": "US",
  "state": "TX"
}
```

State targeting costs **+2 credits** on top of the base cost and any other add-ons. Use [`GET /v1/states?country=US`](https://cloro.dev/docs/api-reference/endpoint/states) to retrieve the full list of supported state codes. Google Search and AI Mode are not affected — those endpoints continue to use `location` / `uule` for sub-country targeting.

**25th April 2026**

**Inline products now return offers correctly for ChatGPT**

We fixed a bug where ChatGPT inline products were missing pricing and merchant data. Inline products now include the full offer payload (current price, multi-merchant offers from retailers like Amazon and John Lewis, product images, and aggregated ratings) fetched from ChatGPT's product update API.

Alongside this fix, shopping cards and inline products move to an opt-in model on the ChatGPT endpoint. Set `include.shopping: true` to include them in your response:

* **Pricing and offers**: Current price and multi-merchant offers with availability
* **Product images**: Image URLs for product display
* **Ratings**: Aggregated rating scores and review counts

> [!NOTE]
>
> **Opt-in with additional credit cost**
>
> Shopping cards and inline products are disabled by default. Set `include.shopping: true` to enable them. Enabling `shopping`, `rawResponse`, `searchQueries`, or `ads` (or any combination) adds +2 credits to the base cost.
>
> The credit surcharge reflects increased extraction complexity. OpenAI now serves product pricing, offers, and merchant data through a separate endpoint, so cloro performs additional fetches per product to enrich the response.

> [!WARNING]
>
> **Migration deadline: 8th May 2026**
>
> During the migration window, ChatGPT responses still return `shoppingCards` and `inlineProducts` by default. **Starting 8th May 2026**, requests without `include.shopping: true` will no longer receive these fields. Update your integrations before that date to avoid silent data loss.

> [!NOTE]
>
> **Breaking change**: Shopping cards and inline products were previously included automatically in ChatGPT responses. They now require `include.shopping: true` in your request. The `details` object on inline products (rationale and themed reviews) is no longer returned.

Learn more in our [ChatGPT shopping cards documentation](https://cloro.dev/docs/api-reference/endpoint/chatgpt/shopping-cards.md) and [inline products documentation](https://cloro.dev/docs/api-reference/endpoint/chatgpt/inline-products.md).

**7th April 2026**

**More business data in ChatGPT map entries**

ChatGPT map entries now return mapped business data from providers (Yelp, Google Business) with 47 structured fields, replacing the previous 10-field structure.

What changed:

* **Mapped data**: Map entries now include all available business fields from ChatGPT's providers (Yelp, Google Business, Yelp-feed)
* **47 mapped fields**: Access to detailed location data, operating hours, attributes, reviews, images, and provider-specific metadata
* **Structured schema**: Properly typed fields with consistent camelCase naming conventions
* **Field name updates**: `phone_number` → `phone`, `country` → `countryCode`, `review_count` → `reviewCount`
* **Null-safe**: All fields except `name` and `position` are optional

Key improvements:

* **More location data**: Full address breakdown with coordinates (`latitude`/`longitude`), distance from user (`distanceMeters`), and human-readable location strings
* **Hours**: Weekly schedule with next opening times (`nextOpenHour`) and special hours (`specialHours`)
* **Attributes**: Provider-specific details like parking options, WiFi availability, accepted payment methods, and accessibility features
* **Images**: Multiple image URLs (`imageUrls`) with provider-hosted images (`providerImages`)
* **Metadata**: Business claimed status (`isClaimed`), opening/closing dates (`dateOpened`/`dateClosed`), popularity scores (`popularityScore`), and cache indicators (`fromCache`)

> [!NOTE]
>
> **Breaking change**: Field names have changed to camelCase. Examples: `review_count` → `reviewCount`, `country_code` → `countryCode`, `is_open` → `isOpen`. All fields except `name` and `position` are now optional.

Learn more in our [ChatGPT map documentation](https://cloro.dev/docs/api-reference/endpoint/chatgpt/map.md).

**6th April 2026**

**Ad extraction for ChatGPT**

ChatGPT responses now support structured ad extraction when advertising content is displayed. This opt-in feature lets you monitor ads shown in ChatGPT responses.

> [!NOTE]
>
> **Opt-in feature with additional cost**
>
> Ad extraction is disabled by default. Set `include.ads: true` to extract ads from ChatGPT responses. Enabling `ads`, `rawResponse`, or `searchQueries` (or any combination) adds +2 credits to the base cost.

**Features**:

* **Brand information**: Advertiser brand name, URL, and favicon
* **Carousel cards**: Multiple promotional cards with titles, descriptions, images, and destination URLs
* **Attribution tracking**: All URLs include ChatGPT attribution parameters
* **Structured data**: JSON structure

Learn more in our [ChatGPT documentation](https://cloro.dev/docs/api-reference/endpoint/chatgpt/ads.md).

**30th March 2026**

**Inline products for ChatGPT**

ChatGPT responses now include inline products: individual product references that appear embedded in the response text, separate from shopping cards. This feature supports OpenAI's new [product discovery capabilities](https://openai.com/index/powering-product-discovery-in-chatgpt/) announced in ChatGPT.

> [!NOTE]
>
> **Model availability**: Inline products currently appear when ChatGPT uses the `gpt-5-3` model. ChatGPT automatically selects which model to use for each request.

What's new:

* Inline product extraction: Individual products referenced in comparison tables, featured recommendations, or inline mentions
* Rendering hints: Display guidance with `render_as` field ("inline", "hero", or "block")
* Cite references: Each product includes a unique cite ID for cross-referencing with text

Learn more in our [ChatGPT inline products documentation](https://cloro.dev/docs/api-reference/endpoint/chatgpt/inline-products.md).

**19th February 2026**

**Improved ChatGPT source metadata**

ChatGPT sources now include enhanced metadata for better source attribution:

* **`datePublished`**: Publication date of the source article (e.g., "May 22, 2025")
* **`label`**: Now contains the article title instead of the domain name
* **`description`**: Now contains a content snippet instead of the combined date and title

Learn more in our [ChatGPT documentation](https://cloro.dev/docs/api-reference/endpoint/chatgpt/sources.md).

**10th February 2026**

**ChatGPT geographical expansion**

ChatGPT is now available in 200 countries worldwide.

The [countries endpoint](https://cloro.dev/docs/api-reference/endpoint/countries.md) remains the authoritative source for current country availability. Always query with `model=chatgpt` to verify supported locations before deploying.

**6th February 2026**

**Isolation of ChatGPT citation data**

We've improved how source information is structured and exposed in ChatGPT responses:

**Citation pills**: Inline citations that appear within ChatGPT responses where specific sources are referenced. Each citation pill includes:

* **URL**: Direct link to the cited source
* **Label**: Title or label of the citation
* **Description**: Summary of the cited content
* **Domain**: Source domain (e.g., "example.com")
* **Date published**: ISO 8601 date string when the source was published
* **Citation pill ID**: Unique identifier for the citation

**Sources footnote field**: The `sources` array now includes a `footnote` boolean field that indicates whether a source appears in the main window footnote (i.e., the sources pill), to distinguish between primary and secondary sources.

Previously, the citation and source pill data was only accessible by parsing the markdown response. Now you can access it directly through structured JSON objects without needing to parse markdown links.

No additional parameters required. Citation pills and the footnote field are automatically included when available in ChatGPT responses.

Learn more in our [ChatGPT documentation](https://cloro.dev/docs/api-reference/endpoint/chatgpt/citation-pills.md).

**3rd February 2026**

**Map entries for ChatGPT**

ChatGPT responses now automatically include structured map entries when business or place information is detected. Use cases:

* **Local business monitoring**: Track restaurants, stores, and service providers
* **Location intelligence**: Extract ratings, reviews, and contact details
* **Competitive analysis**: Monitor local businesses across different regions
* **Directory building**: Create structured business listings

Map entries include business details:

* **Business information**: Name, category, description
* **Social proof**: Rating score, review count
* **Contact details**: Website URL, phone number
* **Location data**: Position/ranking in results
* **Navigation**: Directions URL (when available)

No additional parameters are required. Map entries are automatically detected and included when ChatGPT returns local business or place information.

Learn more in our [ChatGPT documentation](https://cloro.dev/docs/api-reference/endpoint/chatgpt/map.md).

**6th November 2025**

**Entity extraction for ChatGPT**

ChatGPT responses now include automatic entity extraction when specific items, products, brands, or concepts are identified. Use cases:

* **Product recognition**: Identify and extract product mentions
* **Brand tracking**: Monitor brand references across ChatGPT responses
* **Concept analysis**: Extract named entities for semantic analysis
* **Content classification**: Categorize response content based on extracted entities

Each entity includes:

* **Type**: Entity type identifier (e.g., "product", "software")
* **Name**: Entity name or title (e.g., "adidas Grand Court Lo", "Nike Dunk Low Retro SE")

Entity extraction works alongside shopping cards. No additional parameters are required. Entities are automatically detected and included when available.

Learn more in our [ChatGPT documentation](https://cloro.dev/docs/api-reference/endpoint/chatgpt/entities.md).

**1st November 2025**

**Shopping cards for ChatGPT**

ChatGPT responses now automatically include structured shopping cards when product information is detected. Use cases:

* **Product monitoring**: Track prices, ratings, and availability over time
* **Price tracking**: Monitor price changes across different regions
* **Competitive intelligence**: Extract structured product data for analysis
* **Commerce integration**: Build price comparison and recommendation systems

Shopping cards include product details:

* **Product information**: Name, brand, description, specifications
* **Pricing data**: Current price, original price, discount information
* **Commercial details**: Multiple merchant offers, availability, checkout options
* **Media assets**: Product images, checkout-specific images
* **Ratings**: Ratings, review counts, rating citations with sources
* **Offer details**: Merchant-specific pricing, promotional tags, shipping costs

The shopping cards feature supports:

* **Multi-offer products**: Compare different merchants for the same product
* **Price breakdown**: Pricing including base, shipping, tax, and total
* **Promotional content**: Tags, tooltips, and special offers
* **Media**: Multiple product images and checkout assets
* **Availability tracking**: Real-time stock and checkout status

No additional parameters are required. Shopping cards are automatically detected and included when available.

Learn more in our [ChatGPT documentation](https://cloro.dev/docs/api-reference/endpoint/chatgpt/shopping-cards.md).

**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`)

**17th October 2025**

**Added `include.rawResponse` parameter**

You can now access the underlying AI provider payload in monitoring responses (ChatGPT-only). Enable it with `"include.rawResponse": true` to receive the full provider response alongside cloro's structured output.

```json theme={null}
{
  "prompt": "What do you know about Acme Corp?",
  "model": "CHATGPT",
  "include": {
    "markdown": true,
    "rawResponse": true
  }
}
```

Learn more in our [API Reference](https://cloro.dev/docs/api-reference/endpoint/monitor-chatgpt.md).


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