Google: Gemini 2.5 Flash
google/gemini-2.5-flash
Use this Gemini 2.5 variant as a separate candidate when testing summaries or text analysis. Pin its model ID to isolate its behavior before adding any routing policy.
Provider-supported parameters
These are upstream capabilities. Jevrouter supports the subset described in the API contract; chat input is currently text only.
Capabilities are imported from OpenRouter’s catalog. This does not mean every model has been independently tested by Jevrouter.
Catalog updated: 2026-09-22T08:51:50.371Z · Price version: cmubxr2mm07wcjn0z66ha0vhv:3
Provider pricing fields · USD per indicated unit
{
"prompt": "0.0000003",
"completion": "0.0000025",
"audio": "0.000001",
"image": "0.0000003",
"web_search": "0.014",
"input_cache_read": "0.00000003",
"input_audio_cache": "0.0000001",
"input_cache_write": "0.0000000833333333333333",
"internal_reasoning": "0.0000025"
}JEVROUTER INTEGRATION NOTES · REVIEWED 2026-09-22
What to check in your application
- Measure billable output, including any reasoning tokens reported by the provider.
- The upstream model has multimodal capabilities, but Jevrouter's chat endpoint currently accepts text only.
Start with the example below, then test representative inputs against your own acceptance criteria.
Make a request
curl --no-buffer https://api.jevrouter.io/v1/chat/completions \
-H "Authorization: Bearer $JEVROUTER_API_KEY" \
-H "Content-Type: application/json" \
-d @- <<'JSON'
{
"model": "google/gemini-2.5-flash",
"messages": [
{
"role": "user",
"content": "Summarize this support ticket in one sentence: The invoice arrived twice, but my card was charged once. I need a corrected receipt."
}
],
"max_tokens": 1024
}
JSONPlan your integration
Related models to evaluate
Use identical inputs and scoring rules. No ranking is implied by this selection.
Source: OpenRouter model catalog. Imported descriptions and capabilities are provider declarations, not independent benchmark results. Jevrouter currently uses OpenRouter as its managed upstream.