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

# Platform changelog

> All cloro changelog entries for Platform, newest first.

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

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

**29th September 2026**

**Send requests from the dashboard Playground**

The [Playground](https://dashboard.cloro.dev/playground) now sends requests to every monitoring endpoint, with no API key. Pick an endpoint, fill in its parameters, and see the response in three tabs:

* **JSON**: the full response.
* **HTML**: the page that the endpoint returned, rendered.
* **Code**: the same request in cURL, Python and Node.js, ready to copy.

Requests use your organization's credits and show in [Logs](https://dashboard.cloro.dev/logs). The page URL keeps the parameters, so you can share a request with your team.

**17th August 2026**

**Scheduled maintenance: 19 August 2026, 18:00 UTC**

We will do routine infrastructure upgrades on **Wednesday 19 August 2026 from 18:00 UTC**. They will take approximately 1 to 2 hours.

Scraping and the API stay fully operational for the full window. Dashboard analytics and log views can be unavailable for short periods, which leaves a short gap in the dashboard data for that window. No action is necessary.

**14th August 2026**

**Request latency is now returned in responses**

Every API response carries an [`X-Latency-Ms`](https://cloro.dev/docs/guides/concurrency#latency-header) header with the milliseconds the API spent on that request. It excludes network transit.

Async task processing time is reported separately as [`task.latencyMs`](https://cloro.dev/docs/guides/making-requests/async#step-2-receive-the-results), measured from first pickup to the final outcome and excluding the initial queue wait. It is returned by [`GET /v1/async/task/{taskId}`](https://cloro.dev/docs/api-reference/endpoint/get-task-status), in the [webhook payload](https://cloro.dev/docs/guides/webhooks.md#receiving-deliveries), and in create responses, where it is `null` until the task finishes.

Both additions are additive — no existing field or header changed.

**11th August 2026**

**Incident: `result.html` unavailable between 12:00 and 12:47 UTC**

A DNS misconfiguration meant the URLs returned in `result.html` did not resolve between **12:00 and 12:47 UTC on 11 August 2026**. Requests completed and were charged as normal, and every other `result` field was unaffected. DNS has been corrected.

The HTML from that window cannot be recovered. Contact support with the number of affected credits and we will reimburse them.

**7th August 2026**

**MCP server**

cloro now ships a hosted [MCP server](https://cloro.dev/docs/integrations/mcp.md) that exposes the monitor endpoints as agent tools for any MCP client — Claude, Claude Code, Cursor, or your own agent. Connect over Streamable HTTP at `https://mcp.cloro.dev/YOUR_CLORO_API_KEY/mcp` and ask your agent how AI assistants answer a prompt, whether a brand appears in Google's AI Overview, or what Google News is saying — no HTTP calls to hand-write. The server forwards your own API key to the API, so billing, rate limits, and concurrency work exactly as they do for direct requests.

See the [MCP server guide](https://cloro.dev/docs/integrations/mcp.md) for client configuration and the full tool list.

**30th July 2026**

**New endpoint: read your credit balance with `GET /v1/credits`**

The new [`GET /v1/credits`](https://cloro.dev/docs/api-reference/endpoint/get-credits) endpoint returns your current balance (`remaining`), credits per cycle (`perCycle`), and the cycle reset date (`cycleResetsAt`). Async-only workloads can now read their balance and reset date programmatically — for low-balance alerts or a submission breaker — without making a billable sync `/v1/monitor/*` call just to inspect the `X-Credits-Remaining` header.

**18th July 2026**

**New `DELETE /v1/async/queue` endpoint to clear your async queue**

You can now clear your organization's pending async queue in a single call with the new [Clear queue endpoint](https://cloro.dev/docs/api-reference/endpoint/clear-async-queue.md). It deletes every task still in the `QUEUED` state and returns the number removed (`{ "success": true, "cleared": <count> }`), giving you a self-serve way to drain a backlog instead of waiting for it to process. Tasks already `PROCESSING` are in-flight and left running, and `COMPLETED`/`FAILED` tasks are untouched. Queued tasks aren't charged until they're processed, so clearing them has no effect on your credit balance, and the call is idempotent — an empty queue simply returns `cleared: 0`. Check how many tasks are queued first with the [async status endpoint](https://cloro.dev/docs/api-reference/endpoint/get-async-status.md).

**2nd July 2026**

**OpenClaw integration**

cloro now ships a plugin for [OpenClaw](https://openclaw.ai) that exposes the monitor endpoints as native agent tools — `cloro_chatgpt`, `cloro_perplexity`, `cloro_gemini`, `cloro_copilot`, `cloro_aimode`, `cloro_google`, and `cloro_google_news`. Ask your OpenClaw agent how AI assistants answer a prompt, whether a brand appears in Google's AI Overview, or what Google News says — no HTTP calls to hand-write.

See the [OpenClaw integration guide](https://cloro.dev/docs/integrations/openclaw.md) for installation and configuration, including an MCP-server alternative.

**22nd June 2026**

**Rate limits are now per endpoint**

The API rate limit of 1,000 requests per second now applies independently to each endpoint (`/v1/*`) per API key. Previously, all endpoints shared a single bucket, meaning a burst on one endpoint could exhaust the limit for others. Each endpoint now has its own independent bucket, so high-traffic calls to one endpoint no longer affect the rate limit for any other.

No action required — existing integrations are unaffected. The `X-RateLimit-Limit` and `X-RateLimit-Remaining` response headers continue to reflect the limit and remaining requests for the specific endpoint called.

**17th June 2026**

**Ask the docs — AI assistant now available**

You can now ask questions about cloro directly from the docs. The assistant is trained on all published documentation and answers in natural language, with citations linking back to the relevant pages.

Look for the **Ask Assistant** button in the navigation bar or the search bar. It works across all pages — API reference, guides, and the changelog.

**1st June 2026**

**Webhook signing — verify deliveries came from cloro**

Enable webhook signing from the [dashboard](https://dashboard.cloro.dev/webhooks) and every async-task delivery will carry an `X-Cloro-Signature` header (HMAC-SHA256 over `<timestamp>.<raw_body>`) plus `X-Cloro-Timestamp` and `X-Cloro-Webhook-Id`. Your endpoint can confirm the payload's origin and integrity, and reject anything signed more than a few minutes ago to protect against replay.

The new [Webhooks guide](https://cloro.dev/docs/guides/webhooks.md) is the single home for everything that happens at your endpoint — payload shape, retry behavior, signature verification (with copy-pasteable Node.js, Python, and Go examples), and troubleshooting. Opt-in per organization.

**23rd April 2026**

**Sync request surcharge**

All sync monitor requests (`/v1/monitor/*`) now include a **+2 credit surcharge** on top of the base cost and any feature add-ons. This reflects the higher operational cost of real-time synchronous requests.

Async and batch requests (`/v1/async/*`) are **not** affected by this surcharge.

Existing customers who used sync endpoints in the 30 days before this change have been granted a grace period. If you have questions about your account, contact [info@cloro.dev](mailto:info@cloro.dev).

Learn more in our [provider pricing documentation](https://cloro.dev/docs/guides/providers.md#sync-request-surcharge).

**9th April 2026**

**Batch task creation**

You can now submit up to 500 async tasks in a single API request using the new batch endpoint. This reduces HTTP overhead for high-volume workloads and simplifies bulk monitoring workflows.

**Features**:

* **Up to 500 tasks per request**: Submit tasks to any combination of providers in one call
* **Partial success**: Each task is validated independently. One invalid task doesn't block the rest
* **Per-task error reporting**: Failed tasks include detailed error codes (`VALIDATION_ERROR`, `RESOURCE_ALREADY_EXISTS`, `INSUFFICIENT_CREDITS`) with field-level details
* **Per-task credits**: Each task's result includes its own credit information
* **Full feature support**: Each task in a batch supports priority, idempotency keys, and webhooks

Learn more in the [batch task creation documentation](https://cloro.dev/docs/api-reference/endpoint/create-batch-tasks.md).

**9th April 2026**

**Priority support for async tasks**

You can now assign a priority to async tasks so that time-sensitive work is processed first. Set the `priority` field (1-10) when creating a task. Higher numbers mean higher urgency.

**Features**:

* **Priority range**: Integer from 1 (lowest, default) to 10 (highest)
* **Smart ordering**: Higher-priority tasks are processed before lower-priority ones within your queue. Same-priority tasks are processed in FIFO order
* **Priority breakdown**: The [async status endpoint](https://cloro.dev/docs/api-reference/endpoint/get-async-status.md) now shows queued task counts per priority level
* **Backward compatible**: Tasks without a priority default to 1, so existing integrations are unaffected

Learn more in our [async requests documentation](https://cloro.dev/docs/guides/making-requests/async.md#request-prioritization).

**24th March 2026**

**Async queue monitoring and visibility**

New [`GET /v1/async/status`](https://cloro.dev/docs/api-reference/endpoint/get-async-status) endpoint provides real-time visibility into your async queue health, including queued tasks, processing tasks, and concurrency usage.

**Use cases**:

* Monitor queue health and processing capacity
* Decide on plan upgrades based on actual concurrency usage
* Debug task delays by identifying queue bottlenecks
* Throttle task submission based on current queue size

Learn more in our [async status documentation](https://cloro.dev/docs/api-reference/endpoint/get-async-status.md).

**14th March 2026**

**Global coverage milestone: 250 countries supported**

cloro now supports **250 countries worldwide** across all endpoints.

Our geographical infrastructure spans from major markets to remote territories, so you can monitor AI responses and search results from almost anywhere in the world. This includes territories like Antarctica (AQ), remote islands like Bouvet Island (BV), and regions like the British Indian Ocean Territory (IO).

**Total coverage**:

* **250 countries**: Complete ISO 3166-1 alpha-2 country code coverage
* **All endpoints supported**: Geographical availability across ChatGPT, Perplexity, Grok, Gemini, Copilot, AI Mode, AI Overview, and Google Search
* **Model-specific availability**: Each model has its own country support based on provider restrictions

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

**31st January 2026**

**Added 16 new countries**

We've expanded our geographical coverage with 16 new countries available for monitoring across all non-Google endpoints:

```text theme={null}
BG - Bulgaria
BY - Belarus
CY - Cyprus
EE - Estonia
GE - Georgia
KE - Kenya
KG - Kyrgyzstan
LT - Lithuania
LU - Luxembourg
LV - Latvia
MA - Morocco
MT - Malta
PE - Peru
TJ - Tajikistan
UZ - Uzbekistan
```

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

**18th December 2025**

**Added 11 new countries**

Expanded our geographical coverage with 11 new countries available for monitoring:

```text theme={null}
BD - Bangladesh
CO - Colombia
EG - Egypt
FI - Finland
HK - Hong Kong
KZ - Kazakhstan
NG - Nigeria
PH - Philippines
PK - Pakistan
VE - Venezuela
VN - Vietnam
```

Most new locations start with low capacity, which will be increased based on demand. 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.

**17th December 2025**

**Defined async task retention policy**

`COMPLETED` and `FAILED` async tasks are stored for **24 hours** after you create the task.

HTML URLs also expire after 24 hours from generation (aligned with task retention).

**12th December 2025**

Since location availability depends on the model, we have enhanced the `/v1/countries` endpoint with model filtering:

* **Model-specific filtering** - Get countries available for specific AI providers using the `model` query parameter
* **Supported models** - Filter by: `aimode`, `aioverview`, `chatgpt`, `copilot`, `gemini`, `google`, or `perplexity`

**Usage examples**:

```bash theme={null}
# Get all countries
curl "https://api.cloro.dev/v1/countries"

# Get countries available for ChatGPT
curl "https://api.cloro.dev/v1/countries?model=chatgpt"

# Get countries available for Perplexity
curl "https://api.cloro.dev/v1/countries?model=perplexity"
```

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

**18th November 2025**

The HTML code is now stored externally to avoid crowding the response payload.

**Changes**:

* HTML URLs now expire after 24 hours from generation
* Storage URLs updated to use `https://storage.cloro.dev/results/` format

**Important note**: If you need to preserve HTML content longer than 24 hours, download it promptly after receiving the response.

**Example response**:

```json theme={null}
{
  "result": {
    "html": "https://storage.cloro.dev/results/c45a5081-808d-4ed3-9c86-e4baf16c8ab8/page-1.html"
  }
}
```

Learn more in our [output formats documentation](https://cloro.dev/docs/guides/output-formats.md).

**15th November 2025**

**Enhanced retry logic for synchronous requests**

We have the following changes in our internal retry mechanism:

* Increased retry attempts from 5 to 10 for synchronous requests
* Added 5-minute maximum duration timeout to prevent indefinite waiting
* Requests canceled by clients are charged for resources consumed (same behavior as before)

This automatic retry handling **removes the need for client-side timeout logic**. More details in the [Error handling](https://cloro.dev/docs/guides/error-handling.md) section.

**14th November 2025**

**Configurable HTML response for all parsers**

HTML content in parser responses is now optional and configurable across all monitoring endpoints.

**Changes**:

* Added `include.html` parameter to all parser endpoints (ChatGPT, Perplexity, Copilot, AI Mode, AI Overview)
* A URL to the HTML content is now only included when explicitly requested with `"include.html": true`
* Responses are smaller and faster when HTML is not needed
* Markdown conversion continues to work regardless of HTML inclusion

**Usage example**:

```json theme={null}
{
  "prompt": "Your query here",
  "include": {
    "html": true,
    "markdown": true
  }
}
```

This reduces response size and improves performance when your application doesn't need the full HTML content.

**11th November 2025**

**Asynchronous requests and webhooks**

You can now make asynchronous requests for async tasks. When you make an async request, you'll receive a `taskId`, the task will then be processed in the background.

You can retrieve the results in two ways:

* **Webhooks**: Provide a `webhook.url` in your request, and we'll send the results to your endpoint as soon as they're ready.
* **Polling**: Use the new [`GET /v1/async/task/{taskId}`](https://cloro.dev/docs/api-reference/endpoint/get-task-status) endpoint to check the status of your task and retrieve the results when it's complete.

This works for serverless environments or applications that can't wait for a task to complete.

Learn more in our [async requests documentation](https://cloro.dev/docs/guides/making-requests/async.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`)

**14th October 2025**

**Added `searchQueries` field to responses**

All AI monitoring responses now include a `searchQueries` field that shows the search terms used to generate the AI response.

```json theme={null}
{
  "success": true,
  "result": {
    "text": "The name \"Acme Corporation\" is used in various contexts...",
    "searchQueries": [
      "What is Acme Corporation?",
      "Acme Corp company overview",
      "Acme Corporation products and services"
    ]
  }
}
```

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

**11th October 2025**

**Added `include.markdown` parameter**

You can now receive markdown-formatted content in AI monitoring responses. Perfect for documentation workflows and content management systems.

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

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

**9th October 2025**

**cloro API launch**

The cloro AI monitoring API is live. Extract structured data from ChatGPT, Perplexity, Microsoft Copilot, Google AI Mode and other AI models about your brand or any topic across different regions.

Key features:

* AI response monitoring across different countries
* Structured data extraction with sources and citations
* Support for text and HTML formats
* Real-time AI model tracking

Get started with our [welcome guide](https://cloro.dev/docs/index.md) or explore the [API reference](https://cloro.dev/docs/api-reference/introduction.md).


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