The Release Desk

Posted on Oct 14 AI-assisted

Gemini 4 Argon is half price until November 30. Three of your settings already do nothing

#webdev #gemini #ai #javascript

Hint: nothing crashes. That's the problem.

Google opened Gemini 4 Argon, its new flagship model, to everyone on the paid Gemini API on October 13. The model ID is gemini-4-argon, and the Vercel AI SDK's Google provider added it the same day.

So the upgrade looks like a one-line change. Swap the model string, ship, done.

But Argon doesn't play by the old rules. Some settings you've been passing for months now get ignored. Your app doesn't throw, and it doesn't fail a test. It just quietly stops doing what you think it does.

And there's a deadline attached.

The deadline first

According to Google's pricing page, Argon costs $2 per million input tokens and $10 per million output tokens through November 30. From December 1, that becomes $4 and $20. Batch and Flex are half of those numbers, and they double on the same date.

Two details matter more than the headline price:

Thinking is billed as output. The pricing table says it outright: "output price (including thinking tokens)". The default thinking level is medium, so every call does some thinking, even for short answers.
There's no free tier. Google's pricing page says Argon is "not available on the Free tier or on the Google AI Pro plan."

Here's a rough example (illustrative numbers, not a benchmark). Say a feature makes 10,000 calls a month, each with 2,000 input tokens and 800 output tokens including thinking. That's $40 + $80 = $120 a month now, and $240 from December for the exact same traffic.

So if you're testing Argon this week, do your budget maths at the December price.

The three settings that went quiet

Google's developer guide has a short "Migrating from previous models" section. It's easy to skip. Don't.

1. temperature, top_p and top_k are ignored. In Google's words: "Custom sampling values are ignored by gemini-4-argon and return a deprecation warning." A warning, not an error. Your request succeeds, and your carefully tuned temperature: 0.2 is now a decoration.

2. thinking_budget is deprecated. Argon uses thinking_level instead, with three values: low, medium (the default) and high. Google suggests low for classification, routing and extraction, and high for multi-file debugging and architecture work.

3. Explicit context caching is gone. If your code creates a cache and passes cached_content, that's not supported on Argon. Caching is now implicit: it happens on its own, and cached input tokens are 95% off.

Think of it like a new car that ignores the cruise-control button. The car still drives. You just aren't controlling the speed anymore.

So, to recap:

Set temperature to 0? Ignored.
Set a thinking budget of 2,048? Deprecated.
Built a caching layer? Not supported anymore.

What that looks like in a Next.js or Node app

If you call Gemini through the Vercel AI SDK, a typical "before" looks like this:

import { generateText } from 'ai';
import { google } from '@ai-sdk/google';

const { text } = await generateText({
  model: google('gemini-2.5-pro'),
  temperature: 0.2,
  providerOptions: {
    google: { thinkingConfig: { thinkingBudget: 2048 } },
  },
  prompt,
});

And the Argon version:

const { text } = await generateText({
  model: google('gemini-4-argon'),
  providerOptions: {
    google: { thinkingConfig: { thinkingLevel: 'low' } },
  },
  prompt,
});

The thinkingLevel option and the gemini-4-argon model ID both exist in @ai-sdk/google 4.0.95 (released October 13). So update the package first. If you use cachedContent in providerOptions, remove it.

One small trap: the SDK's type also allows 'minimal', because older Gemini models accept it. Argon's docs only list low, medium and high, so stick to those.

The fourth thing: timeouts

This one isn't a setting, but it can break production.

Google's guide says hard reasoning prompts "can take several minutes". It recommends setting your HTTP client timeout to at least 15 to 20 minutes, or running the request in the background (background: true on its Interactions API).

A typical serverless request handler isn't built to wait 20 minutes. If you plan to use thinkingLevel: 'high' behind an API route, check your platform's maximum function duration first. Or move that work to a background job and poll for the result. The AI SDK's changelog says generateText now polls background calls until they finish when you use the Interactions API.

Should you switch?

Argon is a strong model, and Google reports big wins on its own codebase. Independent rankings disagree about whether it's the best, so the honest test is your own prompts, not a leaderboard.

What's not up for debate is the checklist. If you swap the model ID without it, your app keeps working, just not the way you think.

Desk verdict: Try Argon now while it's half price, but plan your budget at the December 1 rate. Before you swap the model ID, remove temperature/topP/topK, switch thinkingBudget to thinkingLevel, drop explicit caching, and raise your timeouts for high thinking.

Sources: Gemini 4 Argon developer guide (Google AI Studio) · Gemini API model page · Gemini API pricing · Google's developer announcement · @ai-sdk/google on npm (4.0.95) · VentureBeat on independent rankings

DEV Community