Routeless Radar calls the Gemini API with Google Search grounding to measure brand visibility in current, source-backed answers. It records the response, grounding sources, returned search queries when available, usage, timing, and failure state. For local checks, the requested market is written into the prompt because this integration does not send a separate provider location field.
Evidence verified 2026-09-28 · Vendor facts reviewed 2026-09-28
Radar contains a direct Gemini provider with Google Search grounding, grounding-source and search-query parsing, usage records, timing, estimated cost, and explicit failure handling. Gemini belongs to the base provider set.
The evidence supports Radar's API-based Gemini measurement. It does not claim consumer-app equivalence, exact device or location simulation, Google partnership, or fixed provider behavior.
Radar sends a buyer-style question to the Gemini API with Google Search grounding enabled, then stores the answer and grounding sources as one provider observation.
Evidence: Radar contains a direct Gemini provider and public methodology for grounded AI visibility checks.
Radar identifies the market attached to the check, states it in the question sent to Gemini, and records that requested market with the returned answer.
Evidence: The provider implementation carries location through the prompt rather than a separate Gemini location field.
The response parser reads Gemini grounding metadata and normalizes returned sources and search queries. Usage and timing stay attached to the same provider run.
Evidence: Verified in Radar's Gemini response parser and provider tests.
The Gemini API credential stays in the server-side provider environment and is never exposed to the browser or included in public observation data.
Google AI credentials remain in the server-side provider environment. Public observations can include answer text, sources, returned search queries, timing, and usage totals, but not API keys, private prompt controls, internal request identifiers, or exact cost rates.
Radar separates successful observations from authentication, quota, timeout, malformed-response, and provider failures. A failed Gemini call is recorded for operations and does not become a successful visibility result.
Product context for Gemini and other grounded AI visibility checks.
How Routeless treats answers, citations, locations, and repeated observations.
Yes. Radar contains a direct Gemini API provider with Google Search grounding, source parsing, returned search-query records, usage accounting, timing, and error handling.
Yes. Radar enables Google Search for grounded Gemini requests and stores the sources returned in grounding metadata.
Radar includes the target market in the question sent to Gemini. This implementation does not claim to set a separate provider location or simulate a specific device.
Gemini is part of Radar's base provider coverage, together with OpenAI and Perplexity.
Not necessarily. Radar identifies its API-based method and does not claim to reproduce every consumer interface, account, or personalization condition.
Google Gemini official site. The Google Gemini name and logo belong to their owner. Inclusion documents Routeless implementation experience and does not imply partnership, certification, or endorsement.
Share the account access, records, expected events, and the workflow that must recover when delivery fails.