Skip to main content
This page covers Gemini through Google AI Studio API keys. For Gemini on Google Cloud’s Vertex AI, see the Google Vertex AI guide. By default, GoModel routes Gemini chat and Responses requests through Gemini’s native generateContent API. Switch to the OpenAI-compatible endpoint when you need compatibility behavior the native adapter does not implement yet (notably remote image_url values).

Configure

Or in config.yaml:
USE_GOOGLE_GEMINI_NATIVE_API is still honored as a legacy global toggle when per-provider GEMINI_API_MODE is unset. Prefer GEMINI_API_MODE.
Native AI Studio mode can also materialize GoModel’s post-routing prompt-cache plans as five-minute Gemini cached-content objects. Reuse is scoped to the API key selected for the session; sessionless traffic with rotating keys skips object creation so a resource is never reused under the wrong credential. Vertex currently receives the original request without cached-content objects.

Base URLs

GoModel keeps separate internal bases for native Gemini and the OpenAI-compatible API:
  • native chat/models: https://generativelanguage.googleapis.com/v1beta
  • OpenAI-compatible: https://generativelanguage.googleapis.com/v1beta/openai
GEMINI_BASE_URL overrides them. When the value ends in /openai, GoModel uses it for the OpenAI-compatible client and derives the native base by stripping /openai. Embeddings, files, and batches always use the OpenAI-compatible surface.

Image input

For URL-hosted images in native mode, Google’s own examples fetch the URL first and send the bytes to generateContent.

Not yet integrated

  • Automatic fetching of remote image_url values in native mode.
  • Uploading remote images through the Gemini Files API before a chat request.

References

Last modified on August 1, 2026