Inkling is Thinking Machines' open-weights model and the first in its family: a 975B-parameter mixture-of-experts (41B active) that reasons over text, images and audio with controllable thinking effort. Inkling Small is its smaller, cheaper sibling.
pick it if
you want Apache 2.0 open weights you can later fine-tune on Tinker
you send images with text and want to tune thinking effort
you run coding or agent harnesses, the work it was trained for
skip it if
cheaper Inkling Small, at half the input price, covers your workload
you need the strongest model; Thinking Machines says Inkling is not it
Inkling Small is Thinking Machines' 276B-total, 12B-active mixture-of-experts open-weights model, the smaller sibling of Inkling. the lab reports performance comparable to Inkling at a quarter of its size; on octomind it costs half Inkling's input rate and under a third of its output rate.
pick it if
want the Inkling family's lower-priced tier with image input
need adjustable thinking effort, from minimal to xhigh
want Apache 2.0 open weights you can fine-tune or self-host
skip it if
you lean on knowledge recall; the lab says Inkling keeps the factuality edge
faq
which is better, Inkling or Inkling Small?
on SWEBench Verified, as each maker reports it, Inkling scores 77.6% and Inkling Small 80.2%. these are each maker's own numbers, not a controlled head-to-head; the spec table lists every benchmark both publish.
which is cheaper, Inkling or Inkling Small?
Inkling Small lists lower input and output prices. on a coding-agent session (2M tokens in, 60,000 out) Inkling costs $2.24 and Inkling Small $1.07.
can i switch between Inkling and Inkling Small mid-task?
yes. in an octomind session, /model octohub:inkling and /model octohub:inkling-small switch models without losing the conversation, so you can draft on one and review on the other.
try either model
switch between models inside the same octomind session.