Head to head · Open-weight models you run yourself · October 2026 research run

Gemma 4 E4B IT vs Inkling 2 Small

Gemma 4 E4B IT scores 63.2 (B) on agent readiness against Inkling 2 Small's 58.8 (C), and leads in 3 of 4 scored categories. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 6472 open weights comparisons

Which one, for what

Gemma 4 E4B IT B

Best for Agents that need a cheap, permissively licensed helper on 8 GB of memory, for tool calls, short audio or images, rather than hard reasoning

Ahead on

  • Reach, 95 against 40
  • Risk, 70 against 65
  • Documentation and upkeep, 75 against 67

Watch for

No safety evaluation figures published

Inkling 2 Small C

Best for Teams with 512 GB or more of datacentre GPU memory who want Thinking Machines' newest open multimodal agent model and can run a runtime's pre-release image.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

The smaller checkpoint needs about 472 GB, and Thinking Machines says 500 GB of GPU memory

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reach Gemma 4 E4B IT +55

Gemma 4 E4B IT 95

Memory 30, Google's own 4-bit QAT GGUF with its projector is 6.15 GB, which with a fifth on top is 7.4 GB and fits in 16 GB or less. Runtimes 25, released support in Transformers, vLLM, SGLang, llama.cpp, Ollama and LM Studio, six of six. Builds 15, Google publishes a Q4_0 GGUF and a w4a16 build and two mobile builds, read as two kinds as for the 31B. Terms 15, plain Apache 2.0 with nothing added. Download 10, no account or gate. Hosted 0, the Gemini API serves only the two largest sizes and no inference provider lists this one.

Inkling 2 Small 40

Memory 0 of 30, the smallest build is Thinking Machines' NVFP4 checkpoint at 393.5 GB, about 472 GB with a fifth added, above the 256 GB line. Runtimes 0, no released version of the six runs it; vLLM and SGLang serve it from their own images and Transformers has it on its main branch only. Builds 15, two precisions from the publisher (NVFP4 and MXFP8). Terms 10, Apache 2.0 with a binding acceptable use policy on top, read as a custom licence. Download 10, no gate. Hosted 5, Thinking Machines' own Tinker serves it as beta serverless inference, and Together is live on Hugging Face. 0 + 0 + 15 + 10 + 10 + 5 = 40.

Documentation and upkeep Gemma 4 E4B IT +8

Gemma 4 E4B IT 75

Model card 20, all seven items are there. Training data 10, a general description by type with a January 2025 cut-off and the filtering, but no sources, mix or sizes. Last change 20, Google's JAX library fixed the Gemma 4 audio embedding that this size runs on 5 October 2026, 28 days before this check, while the Hugging Face files last changed on 20 July. The line drops to 15 after 4 November unless the files or reference code change. Responsiveness 10, Google replied to 12 of 26 questions and reports, the last on 2026-07-17, with the five opened from 21 September to 1 November unanswered. Version policy 10, earlier Gemma generations keep their own repositories and gemma.ai has a dated releases page. File health 5, the files agree with the card but reports about them wait without a reply. 20 + 10 + 20 + 10 + 10 + 5 = 75.

Inkling 2 Small 67

Model card 17 of 20, everything but a dated knowledge cut-off. Training data 15, an EU training-content summary with sources, mix, an October 2026 collection cut-off and filtering. Last change 20, the files were uploaded on 12 November 2026. Responsiveness 0, the repository has no questions yet, which reads as none answered. Version policy 5, a first release. File health 10, the files agree and no broken-file report waits. 17 + 15 + 20 + 0 + 5 + 10 = 67.

Risk Gemma 4 E4B IT +5

Gemma 4 E4B IT 70

File safety 25, safetensors and GGUF only, with nothing from the repository run on load. Provenance 15, the files sit in Google's own organisation and every file has a checksum. Safety evaluation 0, the card says testing showed minimal policy violations but gives no figures. Agent guidance 10, the card names the harm categories its safety training covers and asks for content-safety safeguards, and the tool guide says to validate calls, with no prompt-injection guidance. Licence risk 15, Apache 2.0 with no added policy, no threshold and a working link. Security programme 5, Google's security.txt and reward programme give a route to report a flaw, but no public Gemma advisories were found.

Inkling 2 Small 65

File safety 25, safetensors only and no repository code to run. Provenance 15, the files are in the organisation Thinking Machines links to, with a SHA-256 on every LFS file. Safety evaluation 10, Thinking Machines' own StrongREJECT, FORTRESS, HoneyBench and DistressBench results and described outside red-teaming, but nothing an outside party published or a harness to rerun. Agent guidance 5, the card names safeguards to add but doesn't say what its refusals cover, with nothing on prompt injection. Licence risk 5, 10 off for a use policy that reaches beyond the law and that can change at any time. Security programme 5, a security.txt and a disclosure policy, with public advisories unchecked and scored as absent. 25 + 15 + 10 + 5 + 5 + 5 = 65.

Score by category

CategoryWeight this runGemma 4 E4B ITInkling 2 SmallEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259540Gemma 4 E4B IT +55
Risk20%207065Gemma 4 E4B IT +5
Agent interface10%108585even
Documentation and upkeep10%107567Gemma 4 E4B IT +8
Negative events≤1500
TotalB 63.2/100C 58.8/100

Facts side by side

FactGemma 4 E4B ITInkling 2 Small
KindOpen-weight modelOpen-weight model
VendorGoogle DeepMindThinking Machines Lab
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtyesno
Last release2026-07-202026-11-12
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviews3.5/5 (4)none

How the scores have moved

Verdicts

Gemma 4 E4B IT

A small cousin for light agent work, tool-calling loops, transcription and image reading on a phone or laptop, under Apache 2.0. Google's 4-bit build needs about 7 GB with working space and runs in all the common runtimes. Google's card puts it far below larger Gemma 4 sizes on agent and coding tasks, with no published safety results.

Inkling 2 Small

Thinking Machines' newest open model, a 594B mixture-of-experts generalist with images in, several tool calls a turn and per-request thinking effort. The NVFP4 checkpoint needs about 472 GB, and no released runtime runs it yet, so today that means vLLM's or SGLang's own images, or Tinker and Together hosted. The use policy binds on download and can change.

Before you call either

Gemma 4 E4B IT

  1. On the reference machine run llama-server -hf google/gemma-4-E4B-it-qat-q4_0-gguf --hf-file gemma-4-E4B_q4_0-it.gguf --jinja -c 131072, and add --mmproj with gemma-4-E4B-it-mmproj.gguf for images and audio
  2. With Ollama run ollama run gemma4:e4b and raise num_ctx or OLLAMA_CONTEXT_LENGTH, since the default context is small and agents want at least 64K
  3. In vLLM or SGLang pass --tool-call-parser gemma4 --reasoning-parser gemma4 (vLLM also --enable-auto-tool-choice), or tool calls come back as text; Google's w4a16 build is the 4-bit route there
  4. Thinking is off by default; pass enable_thinking=True or start the system prompt with <|think|>, and drop earlier turns' thinking from history except on tool-call turns
  5. Put images before the text and audio after it, keep audio to 30 seconds and video to 60 frames, and validate tool names and arguments before running them

Inkling 2 Small

  1. No released runtime runs it yet. Serve the NVFP4 checkpoint from SGLang's dev-inkling-2-small image with the cookbook's recipe for your hardware, or from vLLM's vllm/vllm-openai:inkling-2-small image
  2. In vLLM pass --reasoning-parser inkling --enable-auto-tool-choice --tool-call-parser inkling. In SGLang the tool-call parser is inkling2 and the reasoning parser inkling
  3. Transformers' main branch loads only thinkingmachines/Inkling-2-Small-MXFP8, the 622.8 GB checkpoint, and no release has the code yet
  4. Pass reasoning_effort as none, minimal, low, medium, high (the default), xhigh or max, or a number from 0 to 0.99
  5. Effort none conditions the model toward no reasoning but doesn't forbid it, and higher effort needs a larger max_tokens
  6. Tool call arguments must reach the template as an object, not a JSON string, or it raises an error
  7. Images should be 40 to 4096 px a side. The model takes no audio, and the template raises an error for an audio part
  8. Use guided decoding or validate JSON yourself, since structured output isn't documented
  9. Without the hardware, call it on Tinker's OpenAI-compatible endpoint with a Tinker key, at $0.30 input and $1.00 output per million tokens as read on 6 November 2026
  10. Read the Model Acceptable Use Policy before deploying, it binds on download and bars some uses that are legal

Questions

Which is better for AI agents, Gemma 4 E4B IT or Inkling 2 Small?

Gemma 4 E4B IT scores 63.2 (B) on agent readiness against Inkling 2 Small's 58.8 (C), and leads in 3 of 4 scored categories.

Other comparisons with Gemma 4 E4B IT or Inkling 2 Small

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.