Skip to main content
Use one Gemini Generate Content-compatible integration for all seven Gemini models available through APIXO. Configure the APIXO base URL and API key once, then switch models by changing the model ID in the request URL or SDK call.
Google now recommends the newer Interactions API for new direct Gemini integrations and labels Generate Content as legacy. APIXO’s currently published Gemini gateway still uses the generateContent request format documented here. Do not send Interactions API payloads to this endpoint unless APIXO explicitly adds support.
This page includes the complete APIXO Gemini model and pricing snapshot verified on August 3, 2026. Model availability and pricing can change, so check the APIXO Gemini model page before making billing-sensitive decisions.
Choose your integration path: Use the Quickstart to integrate manually, or let an AI implement it by copying this page or using APIXO MCP.

Compare Gemini models and pricing

Choose the model that fits the workload, then use its exact model ID in any example on this page. Prices are in USD per 1 million tokens. means APIXO does not publish a separate cache-write price for that model. Prices verified: 2026-08-03. See the APIXO Gemini model page for the current rate card.
Start with Gemini 3.5 Flash for the latest general-purpose Flash option, Gemini 3.1 Pro Preview for more complex work, or Gemini 3.1 Flash-Lite Preview when preview access at a lower cost matters. Keep a Gemini 2.5 ID when your application intentionally targets that family.

What to change

Quickstart

The examples use gemini-3.5-flash. For REST, replace the model ID in the URL path. For the SDKs, change the model argument.

Let an AI implement it

Copy this page to an AI

Use the Copy page button in the page menu, paste the copied documentation into your AI coding tool, and add this prompt:
Replace gemini-3.5-flash in the prompt with any model ID from the comparison table.

Use APIXO MCP

APIXO MCP reads APIXO’s published machine-readable model catalog and schemas. The gemini schema includes the gateway endpoint, authentication header, supported model IDs, model guidance, and the pricing snapshot shown above. After installing APIXO MCP, ask your AI:
APIXO MCP helps your AI write the integration; it does not replace the API connection used by your application.

Streaming

The alt=sse query parameter requests Server-Sent Events so each response chunk can be processed as it arrives.

Supported Gemini models

Use one of these exact IDs in the REST URL path or SDK model argument.
  • gemini-3.5-flash
  • gemini-3.1-pro-preview
  • gemini-3.1-flash-lite-preview
  • gemini-3-flash-preview
  • gemini-2.5-pro
  • gemini-2.5-flash
  • gemini-2.5-flash-lite
To switch models, keep the same endpoint family, API key, and request format, then change only the model ID.

Troubleshooting

  • 401: missing or invalid API key
  • 400: invalid Gemini request body, endpoint, or unsupported model ID
  • 429: rate limit or temporary capacity limit
  • 502 / 504: upstream provider error or timeout
Retry 429, 502, and 504 with backoff. Fix 400 and 401 before retrying.

Open a model on APIXO

These links open the selected model on APIXO’s Gemini gateway page, where you can review its current pricing and copy model-specific code examples.