Google Search grounding

by GoogleWeb search

Grounding with Google Search connects Gemini to live Google Search results. Gemini decides when to search, writes its own queries and returns metadata that ties each part of its answer to a source, and Google's terms require showing its Search Suggestions with a grounded answer. On Opper, opper:web_search on auto uses it when you call Gemini on the generateContent endpoint, and Opper's own engine everywhere else. Pin "engine": "native" to require it, or pin Jina or SearchBase to keep searches in the EU instead. It runs on 34 routes in the catalogue today.

UseGoogle Search groundingwithin

Add Google Search grounding on Opper

Set up with agents

Paste this into your coding agent (Claude Code, Cursor, Codex, and more) and it will set up and build with Opper for you.

Get your API key

Key info

Endpoint

generateContent

Region

Provider

Pin it with

"engine": "native"

Index

Google Search

Native routes

In your code

1curl "https://api.opper.ai/v3/compat/v1beta/models/gemini/gemini-4-argon:generateContent" \
2  -H "Authorization: Bearer $OPPER_API_KEY" \
3  -H "Content-Type: application/json" \
4  -d '{"contents": [{"role": "user", "parts": [{"text": "What changed in the news today?"}]}],
5       "tools": [{"type": "opper:web_search", "engine": "native"}]}'

Use Google Search grounding with these models

Step-by-step setup for Google Search grounding on each of these models through Opper.

Gemini 4 Argon Gemini 3.8 Flash Gemini 3.7 Flash Gemini 3.6 Flash Gemini 3.5 Flash-Lite Gemini 3.5 Flash Gemini 3.1 Pro Preview Gemini 2.5 Pro See all 700+ models

More tools on Opper

Jina search

Opper's default search engine for models without their own. Search processing stays in the EU.

Search"engine": "jina"

SearchBase

The Swedish open-source search API, on Europe's own Staan index and hosted in the EU.

Search"engine": "searchbase"

Exa search

Exa's search engine built for AI, on any tool-calling model through one tool entry. US-based.

Search"engine": "exa"