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

Inkling-Small vs ThinkingCap (Qwen3.8 27B)

Inkling-Small scores 66.5 (B) on agent readiness against ThinkingCap (Qwen3.8 27B)'s 61 (C), and leads in 3 of 4 scored categories. ThinkingCap (Qwen3.8 27B) 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 45
  • Agent interface, 85 against 70
  • Documentation and upkeep, 82 against 53

Also in its favour

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

Watch for

The smallest build Thinking Machines publishes needs about 205 GB

ThinkingCap (Qwen3.8 27B) C

Best for Small teams and individuals running Qwen3.8-27B for agent or reasoning work who want shorter thinking traces on one 24 GB GPU or Mac.

Ahead on

  • Reach, 75 against 55

Watch for

PolyForm Small Business licence, free commercially only below 100 people and 1,000,000 USD (2019) revenue

Score by category

CategoryWeight this runInkling-SmallThinkingCap (Qwen3.8 27B)Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255575ThinkingCap (Qwen3.8 27B) +20
Risk20%207045Inkling-Small +25
Agent interface10%108570Inkling-Small +15
Documentation and upkeep10%108253Inkling-Small +29
Negative events≤1500
TotalB 66.5/100C 61/100

Facts side by side

FactInkling-SmallThinkingCap (Qwen3.8 27B)
KindOpen-weight modelOpen-weight model
VendorThinking Machines LabBottleCap AI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0PolyForm-Small-Business-1.0.0
Read-only variant documentednono
llms.txtnono
Last release2026-07-312026-10-06
Terms last updatedno document linkedno document linked
Privacy policy last updatedno 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)2.5/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.

ThinkingCap (Qwen3.8 27B)

A Qwen3.8-27B with shorter reasoning, for agent work where thinking tokens cost time, and BottleCap's 4-bit GGUF runs in about 19 GB. The main limits are the licence, which needs a paid licence above 100 people or 1,000,000 USD revenue, a gated main repository, and no safety results or training-data description.

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

ThinkingCap (Qwen3.8 27B)

  1. Check the licence first, an organisation with 100 or more people or 1,000,000 USD (2019) revenue needs a commercial licence from BottleCap
  2. For files without the gate use llama-server -hf bottlecapai/ThinkingCap-Qwen3.8-27B-GGUF:Q4_K_M --jinja, about 17.4 GB
  3. On vLLM use --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_xml, and on SGLang --tool-call-parser qwen3_coder
  4. Set reasoning_effort (xhigh, medium or low) in chat_template_kwargs, any other value makes the template raise an error
  5. Keep the base's sampling (temperature 1.0, top_p 0.95, top_k 20), the GGUF card says greedy decoding can loop
  6. The GGUFs carry an MTP head, and llama.cpp builds without MTP support for this architecture may refuse to load them with a missing blk.64 tensor

Questions

Which is better for AI agents, Inkling-Small or ThinkingCap (Qwen3.8 27B)?

Inkling-Small scores 66.5 (B) on agent readiness against ThinkingCap (Qwen3.8 27B)'s 61 (C), and leads in 3 of 4 scored categories. ThinkingCap (Qwen3.8 27B) leads on reach.

Other comparisons with Inkling-Small or ThinkingCap (Qwen3.8 27B)

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.