GPT-5.6 Terra has its own web search on 1 of its 6 routes, and auto uses it when you call it on the Responses 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/responses \-H "Authorization: Bearer $OPPER_API_KEY" \-H "Content-Type: application/json" \-d '{"model": "openai/gpt-5.6-terra","input": "What changed in the news today?","tools": [{"type": "opper:web_search", "engine": "native"}]}'
GPT-5.6 Terra runs OpenAI web search on the routes below. Its route also sells 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.50 write |
GPT-5.6 Terra is the balanced middle tier of OpenAI's GPT-5.6 family, pairing near-flagship quality with everyday speed and a 1M token context.
Step-by-step setup for OpenAI web search 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"