Gemini 3.1 Pro Preview has its own web search on 2 of its 3 routes, and auto uses it when you call it on the generateContent endpoint. On every other route and endpoint Opper's engine runs the search.
Paste this into your coding agent (Claude Code, Cursor, Codex, and more) and it will set up and build with Opper for you.
curl "https://api.opper.ai/v3/compat/v1beta/models/gemini/gemini-3.1-pro-preview:generateContent" \-H "Authorization: Bearer $OPPER_API_KEY" \-H "Content-Type: application/json" \-d '{"contents": [{"role": "user", "parts": [{"text": "What changed in the news today?"}]}],"tools": [{"type": "opper:web_search", "engine": "native"}]}'
Gemini 3.1 Pro Preview runs Google Search grounding on the routes below. Some routes also sell flex and priority processing: the same model at another price, picked per request with service_tier. How service tiers work.
| Provider | Region | Zero data retention | Training | Input | Output | Cache read | ||
|---|---|---|---|---|---|---|---|---|
| US | No | $2.00 | $12.00 | $0.20$2.38 write | ||||
| Multi | No | $2.00 | $12.00 | $0.20$2.38 write |
Gemini 3.1 Pro Preview by Google, a frontier reasoning LLM with 1M context and strong agentic coding, scoring 77% on ARC-AGI-2 and 81% on SWE-Bench Verified.
Step-by-step setup for Google Search grounding on each of these models through Opper.
Opper's default search engine for models without their own. Search processing stays in the EU.
"engine": "jina"
The Swedish open-source search API, on Europe's own Staan index and hosted in the EU.
"engine": "searchbase"
Exa's search engine built for AI, on any tool-calling model through one tool entry. US-based.
"engine": "exa"