Skip to main content
cloro API monitoring endpoints share a mostly consistent request and response structure. See Making requests for an overview of both request modes.

Request structure

Each provider has its own endpoint (/v1/monitor/chatgpt, /v1/monitor/google, and so on; see Providers). There is no single /v1/monitor path and no model field in the body.

Common parameters

Most monitoring endpoints share these core parameters:
Google Search endpoint exceptionThe Google Search endpoint uses query instead of prompt as the required parameter, since it’s designed for search queries rather than AI prompts. See the Google Search endpoint documentation for details.

Response structure

All successful responses follow this base structure:

Common response fields

Response headers

Every response includes an X-Request-ID header. Store it — our support team uses it to locate your request.
For rate limit, concurrency, and credit headers, see Rate & concurrency limits.

Sources array structure

Some endpoints include additional source fields. See individual endpoint documentation for endpoint-specific source fields.

Request examples