Skip to main content
POST
Monitor Gemini Responses
Extract structured data from Google’s Gemini AI: the generated text response, citations and sources, with Markdown and HTML export formats.
Web search behaviorThis endpoint uses Gemini’s default interface. Gemini decides for itself whether a query needs current information, so web search and source citations may or may not appear.

Request parameters

Uses common parameters. Endpoint-specific options:
  • include.rawResponse (boolean): Include raw streaming response events. Defaults to false

Response objects

Response schema

Includes common response fields plus:

Example usage

Common questions

Some responses come back with no answer. How often, and what should I do?

Under 2% of successful Gemini responses contain no usable answer — Gemini returns a short canned message instead of content, with an empty sources array. See empty responses from AI providers for how to detect them and why matching on the message text does not work. The breakdown below comes from our own continuous Gemini monitoring. “Success on retry” is how often the same prompt returned a full answer on a later run: Retrying once resolves roughly 60% of them overall, which brings the effective rate to well under 1%. Age-restricted refusals are the exception — they follow the subject of the prompt, so retrying converts far fewer of them.
These figures move as Google changes Gemini’s models and safety policies. Use them to size a retry budget, not as a guarantee.

How does cloro retrieve Gemini responses?

cloro does not call the Gemini API. Each request runs through a real browser session against Gemini’s web interface, routed through a proxy in the country you specify. The result.* fields are extracted from that page; the raw streamed events are available via include.rawResponse: true. See How does cloro retrieve data from AI providers? for the implications (model routing, auth walls, geo behaviour).

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

Request parameters for monitoring Gemini responses

prompt
string
required

The prompt to send to Gemini

Required string length: 1 - 10000
Example:

"Explain quantum computing"

country
string
required

Country/region code for localized response

Example:

"US"

include
object

Optional flags for including additional response formats

Example:
state
string

State code for sub-country geo-targeting (e.g., "CA"). Only valid with country "US".

Required string length: 2
Pattern: ^[A-Z]{2}$
Example:

"CA"

Response

successful Gemini monitoring response

success
boolean
required
Example:

true

result
object
required

Gemini response data