Google: Gemma 4 31B (batch) vs Recursive: Flint (free)

Neither wins outright: Google: Gemma 4 31B (batch) is the pick when you need image input, Recursive: Flint (free) when cost matters at scale.

Key numbers

SpecGoogle: Gemma 4 31B (batch)Recursive: Flint (free)
ProviderGoogleRecursive
Input price (per 1M tokens)$0.39$0
Output price (per 1M tokens)$0.97$0
Blended price (3:1 input/output)$0.53$0
Cheaper than … of all models we track51%90%
Context window262K tokens (~393 pages)262K tokens (~393 pages)
Larger context than … of all models47%47%
Max output per response236K tokens (~176,900 words)236K tokens (~176,900 words)
Input typesimage, text, videotext
Output typestexttext
Free variantNoYes
Listed since2026-04-022026-10-21
Advertisement

What it costs for real workloads

Monthly cost at list price for five common workloads. Token counts per unit are stated so you can scale them to your own traffic. A workload that does not fit a model's context window is marked rather than priced.

Workload (per month)Google: Gemma 4 31B (batch)Recursive: Flint (free)Difference
Customer-support chatbot
50,000 conversations — each a 6-turn conversation (1,500 in / 400 out tokens)
$48.65$0Recursive: Flint (free) saves $48.65
RAG search over documents
20,000 questions — each a question answered from ~8 retrieved passages (6,000 in / 500 out tokens)
$56.50$0Recursive: Flint (free) saves $56.50
Coding / tool-using agent
2,000 tasks — each a multi-step task with tool calls and file context (60,000 in / 6,000 out tokens)
$58.44$0Recursive: Flint (free) saves $58.44
Batch summarisation
10,000 documents — each a 6,000-word report summarised to a page (8,000 in / 600 out tokens)
$37.02$0Recursive: Flint (free) saves $37.02
Long-document analysis
500 documents — each a 150-page contract or codebase read in one pass (100,000 in / 2,000 out tokens)
$20.47$0Recursive: Flint (free) saves $20.47

Capabilities side by side

CapabilityGoogle: Gemma 4 31B (batch)Recursive: Flint (free)What it lets you do
Tool / function calling✓ Yes✓ Yescall your APIs and run agent loops
Structured output (JSON schema)✓ Yes✓ Yesreturn JSON that validates against your schema
Reasoning / thinking mode✓ Yes✓ Yesspend extra tokens thinking before answering hard problems
Image input✓ Yes—read screenshots, charts and scanned pages
Audio input——take speech or audio directly
File / PDF input——accept documents without your own parsing step
Image output——generate images, not just text
Built-in web search——answer from live web results
Seed (reproducible sampling)—✓ Yesrepeat a generation for tests and evals
Log-probabilities—✓ Yesread token confidence for classification and scoring

From each model's published parameters and input/output types. “—” means not advertised, not proven absent.

Price history

Which should you choose?

Choose Google: Gemma 4 31B (batch) if…

  • you need image input — to read screenshots, charts and scanned pages; Recursive: Flint (free) does not advertise it

Choose Recursive: Flint (free) if…

  • cost matters at scale — it is 100% cheaper on a typical 3:1 input/output mix ($0 vs $48.65 a month for 50,000 support chats)
  • you need seed (reproducible sampling) — to repeat a generation for tests and evals; Google: Gemma 4 31B (batch) does not advertise it
  • you need log-probabilities — to read token confidence for classification and scoring; Google: Gemma 4 31B (batch) does not advertise it
  • you want to prototype at zero cost — a free variant is listed
  • you want the newer model — released 2026-10-21, 7 months after the other

Frequently asked questions

Is Google: Gemma 4 31B (batch) better than Recursive: Flint (free)?

Neither wins outright: Google: Gemma 4 31B (batch) is the pick when you need image input, Recursive: Flint (free) when cost matters at scale. In short: Google: Gemma 4 31B (batch) when you need image input; Recursive: Flint (free) when cost matters at scale, you need seed (reproducible sampling), you need log-probabilities, you want to prototype at zero cost, you want the newer model.

Which is cheaper, Google: Gemma 4 31B (batch) or Recursive: Flint (free)?

Recursive: Flint (free) is cheaper: $0 vs $0.53 per 1M tokens at a typical 3:1 input/output mix, 100% less. For 50,000 support conversations a month that is $0 against $48.65.

How much do Google: Gemma 4 31B (batch) and Recursive: Flint (free) cost per million tokens?

Google: Gemma 4 31B (batch) costs $0.39 per 1M input tokens and $0.97 per 1M output tokens; Recursive: Flint (free) costs $0 input and $0 output. Output tokens are billed separately, so long answers shift the gap.

Which has the bigger context window, Google: Gemma 4 31B (batch) or Recursive: Flint (free)?

Both take 262K tokens per request — roughly 393 pages of text.

Do Google: Gemma 4 31B (batch) and Recursive: Flint (free) support function calling and JSON output?

Tool calling — Google: Gemma 4 31B (batch): yes, Recursive: Flint (free): yes. JSON-schema structured output — Google: Gemma 4 31B (batch): yes, Recursive: Flint (free): yes.

Can Google: Gemma 4 31B (batch) or Recursive: Flint (free) read images?

Only Google: Gemma 4 31B (batch) accepts image input; Recursive: Flint (free) is text-only for input.

Is Google: Gemma 4 31B (batch) or Recursive: Flint (free) free to use?

Recursive: Flint (free) has a free variant (recursive/flint-v1.0:free). Free variants usually carry tighter rate limits.

What is the maximum output length of Google: Gemma 4 31B (batch) and Recursive: Flint (free)?

Google: Gemma 4 31B (batch) can write up to 236K tokens (about 176,900 words) per response; Recursive: Flint (free) up to 236K (about 176,900 words).

When were Google: Gemma 4 31B (batch) and Recursive: Flint (free) released?

Google: Gemma 4 31B (batch) was listed on 2026-04-02; Recursive: Flint (free) on 2026-10-21.

About the two models

Compare Google: Gemma 4 31B (batch) with other models

Compare Recursive: Flint (free) with other models

Advertisement