Skip to main content
See every entry.
Async: the idempotency 409 returns the existing task IDWhen you reuse an idempotencyKey, the 409 RESOURCE_ALREADY_EXISTS from POST /v1/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 returns it too, except for a key repeated inside the same batch.Google: the AI Overview is expanded in the HTMLWhen a Google Search 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.
Send requests from the dashboard PlaygroundThe 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. The page URL keeps the parameters, so you can share a request with your team.
Scheduled maintenance: 19 August 2026, 18:00 UTCWe 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.
Request latency is now returned in responsesEvery API response carries an X-Latency-Ms header with the milliseconds the API spent on that request. It excludes network transit.Async task processing time is reported separately as task.latencyMs, measured from first pickup to the final outcome and excluding the initial queue wait. It is returned by GET /v1/async/task/{taskId}, in the webhook payload, and in create responses, where it is null until the task finishes.Both additions are additive — no existing field or header changed.
Incident: result.html unavailable between 12:00 and 12:47 UTCA 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.
MCP servercloro now ships a hosted MCP server 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 for client configuration and the full tool list.
New endpoint: read your credit balance with GET /v1/creditsThe new GET /v1/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.
New DELETE /v1/async/queue endpoint to clear your async queueYou can now clear your organization’s pending async queue in a single call with the new Clear queue endpoint. 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.
OpenClaw integrationcloro now ships a plugin for OpenClaw 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 for installation and configuration, including an MCP-server alternative.
Rate limits are now per endpointThe 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.
Ask the docs — AI assistant now availableYou 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.
Webhook signing — verify deliveries came from cloroEnable webhook signing from the dashboard 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 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.
Sync request surchargeAll 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.Learn more in our provider pricing documentation.
Batch task creationYou 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.
Priority support for async tasksYou 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 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.
Async queue monitoring and visibilityNew GET /v1/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.
Global coverage milestone: 250 countries supportedcloro 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 remains the authoritative source for current country availability. Always query with your target model to verify supported locations.
Added 16 new countriesWe’ve expanded our geographical coverage with 16 new countries available for monitoring across all non-Google endpoints:
Remember to always check the model-specific country list before deploying to ensure availability for your target endpoint, as some models have country-specific restrictions.
Added 11 new countriesExpanded our geographical coverage with 11 new countries available for monitoring:
Most new locations start with low capacity, which will be increased based on demand. Remember to check the model-specific country list before deploying to ensure availability for your target endpoint.
Defined async task retention policyCOMPLETED 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).
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:
Learn more in our countries endpoint documentation.
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:
Learn more in our output formats documentation.
Enhanced retry logic for synchronous requestsWe 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 section.
Configurable HTML response for all parsersHTML 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:
This reduces response size and improves performance when your application doesn’t need the full HTML content.
Asynchronous requests and webhooksYou 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} 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.
New dedicated endpointsEach AI model now has its own dedicated endpoint for better performance and clearer documentation:
Added searchQueries field to responsesAll AI monitoring responses now include a searchQueries field that shows the search terms used to generate the AI response.
Learn more in our API Reference.
Added include.markdown parameterYou can now receive markdown-formatted content in AI monitoring responses. Perfect for documentation workflows and content management systems.
Learn more in our API Reference.
cloro API launchThe 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 or explore the API reference.