Ghulam Qadir
Engineering2 min read

Call the small model on purpose

Haiku 5.5, Gemini 4 Argon, and GPT-6.1 Sol showed up within weeks of each other. The useful question is which call in your app is allowed to be cheap.

Call the small model on purpose

Through late September and early October 2026, three efficient models landed close together: OpenAI’s GPT-6.1 Sol on 22 September, Google’s Gemini 4 Argon on 30 September, and Anthropic’s Claude Haiku 5.5 on 7 October. A clear comparison is in this rundown of the three releases. None of them is the model the keynote wants you to remember. They are the ones a product can afford to call all day.

Most of an app is not a hard problem

A support inbox, a classifier on uploaded PDFs, a router that decides which specialist runs next, a pass that pulls the right chunks before a larger model answers. Those calls dominate the bill. They also dominate latency, because they sit on the path before the user sees anything.

Anthropic positions Haiku 5.5 for that path: classification, routing, retrieval, and sub-agent work, not the longest reasoning trace. Google’s Argon is aimed at heavier engineering workflows and a much larger output budget, and it was still limited to trusted testers in the first days after the announcement. OpenAI’s Sol line sits under the Astra tier and above Luna. The names collide on purpose. If you do not read the model card, you will wire the wrong one.

How I would route it

  1. Cheap model first for intent, language, and whether the request is in scope.
  2. Retrieval with an embedding model, not with the generator.
  3. A stronger model only when the cheap one marks the task as ambiguous, high impact, or a poor retrieval.

Write that down as code, not as a vibe. Log the route. If Sol, Haiku, or Argon is wrong on a class of tickets, you want to see the class, not a blended average that looks fine.

What efficient does not mean

A smaller model will still invent a confident answer when the context is thin. Routing does not replace a schema. For anything I store, I still want JSON that fails validation, a tool call with typed arguments, and a human on the actions that cannot be undone.

The October pile-up is good news if you ship software for a company. You can stop sending every token to the most expensive model you have access to. You cannot stop deciding which step is allowed to be wrong.