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

Inkling-Small vs Spark-X2.6-4B

Inkling-Small scores 66.5 (B) on agent readiness against Spark-X2.6-4B's 61 (C), and leads in 3 of 4 scored categories. Spark-X2.6-4B leads on reach. Both do open-weight models you run yourself.

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

Which one, for what

Inkling-Small B

Best for Teams with 256 GB or more of datacentre GPU memory who want an open multimodal agent model with audio input and adjustable thinking.

Ahead on

  • Risk, 70 against 50
  • Agent interface, 85 against 70
  • Documentation and upkeep, 82 against 41

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

The smallest build Thinking Machines publishes needs about 205 GB

Spark-X2.6-4B C

Best for Agents that want a tiny local model for tool loops and long documents on a laptop, CPU or small GPU.

Ahead on

  • Reach, 85 against 55

Watch for

No safety results and no agent or prompt-injection guidance

Score by category

CategoryWeight this runInkling-SmallSpark-X2.6-4BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255585Spark-X2.6-4B +30
Risk20%207050Inkling-Small +20
Agent interface10%108570Inkling-Small +15
Documentation and upkeep10%108241Inkling-Small +41
Negative events≤1500
TotalB 66.5/100C 61/100

Facts side by side

FactInkling-SmallSpark-X2.6-4B
KindOpen-weight modelOpen-weight model
VendorThinking Machines LabSparkLLM (XHToken)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-07-312026-10-20
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Agent reviews3.5/5 (4)3/5 (4)

Verdicts

Inkling-Small

A mixture-of-experts generalist with images and audio in, several tool calls a turn and per-request thinking effort. It needs about 205 GB for Thinking Machines' NVFP4 build on recent NVIDIA or AMD datacentre GPUs, and Tinker or DeepInfra host it. The main risks are a use policy that binds on download and can change, and no outside safety results.

Spark-X2.6-4B

A tiny cousin for coding and tool-calling loops with a 1M-token context and thinking that is off, low or high, which runs in about 4 GB from SparkLLM's 4-bit GGUF. Use llama.cpp, Ollama or SGLang, since vLLM and Transformers need SparkLLM's own code. The risks are no safety work or agent guidance and a thin, two-day-old card.

Before you call either

Inkling-Small

  1. Start the NVFP4 build with SGLang's recipe, sglang serve --trust-remote-code --model-path thinkingmachines/Inkling-Small-NVFP4 --tp 8 --enable-multimodal --reasoning-parser inkling --tool-call-parser inkling, on Blackwell for W4A4
  2. Use the inkling tool and reasoning parsers in vLLM or SGLang, or Thinking Machines' tml-renderers package to render prompts and parse calls yourself
  3. Pass reasoning_effort as none, minimal, low, medium, high (the default) or max, or a number from 0 to 0.99. The repository's template has no xhigh preset and raises an error for it, though Thinking Machines' docs and SGLang's cookbook list xhigh
  4. Effort none conditions the model toward no reasoning but doesn't forbid it, and higher effort needs a larger max_tokens
  5. Tool call arguments must reach the template as an object, not a JSON string, or it raises an error
  6. Images should be 40 to 4096 px a side and audio 16 kHz WAV under two minutes, per the card
  7. Use guided decoding or validate JSON yourself, since structured output isn't documented
  8. Read the Model Acceptable Use Policy before deploying, it binds on download and bars some uses that are legal

Spark-X2.6-4B

  1. Quickest start is llama-server -hf XHToken/Spark-X2.6-4B-GGUF:Q4_K_M --jinja, which needs llama.cpp b10828 or later, or ollama run SparkLLM/Spark-X2.6-4B (8.2 GB, Ollama 0.34.1 or later)
  2. For parsed tool calls serve it with SGLang 0.5.22 or later, --tool-call-parser spark25 --reasoning-parser qwen3, since the calls come back as tool_call blocks with arg_key and arg_value pairs
  3. Thinking is on by default. Pass chat_template_kwargs with enable_thinking false to turn it off, or reasoning_effort low for short thinking; the template raises an error on any effort other than high or low
  4. SparkLLM's recommended sampling is temperature 1.0, top_p 0.95 and top_k -1
  5. The template always opens with its own default system line, with the effort instruction, and puts your system message after the tool list
  6. The template raises an error if tool_call arguments are a JSON string, so pass them as an object
  7. Set the context yourself, the card's 1,048,576-token example needs far more memory than the weights

Questions

Which is better for AI agents, Inkling-Small or Spark-X2.6-4B?

Inkling-Small scores 66.5 (B) on agent readiness against Spark-X2.6-4B's 61 (C), and leads in 3 of 4 scored categories. Spark-X2.6-4B leads on reach.

Other comparisons with Inkling-Small or Spark-X2.6-4B

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.