Why Kael Is Slower, On Purpose
By Response Mosese, Owner, Quancis · Updated
Kael takes longer to answer than most models. That is not a limitation we are working around. It is the trade we chose: accuracy over speed.
Every Kael answer is drafted, checked against your request and refined before you see it, and that takes work. If you want the background, Introducing Kael describes the design. This post is about what the design costs you in time, and how to decide how much of that time to spend.
What slow means in numbers
With thinking on, at any level, Kael spends about 2.2 times as long thinking as an average AI model does. Once it starts writing, though, the answer streams quickly, at roughly 220 to 340 tokens per second. So the wait is at the front. The text itself arrives at a good clip.
With thinking off, the first word usually arrives within 0.7 to 3 seconds, and the output runs at roughly 90 to 140 tokens per second. That is the quickest Kael gets.
We do not have published worst-case latency numbers for long prompts yet, and we would rather say that than imply otherwise.
Choosing how much Kael thinks
You choose how much thinking a request gets, and the setting does more than a simple on-off switch. It changes how the system works on the request. Three levels are available today, plus off.
| Level | Status | Input | Cached input | Output |
|---|---|---|---|---|
| Off | Available | — | — | — |
| Low (default) | Available | $2 | $0.40 | $6 |
| High | Available | $2 | $0.40 | $6 |
| Max | Available | $2 | $0.40 | $6 |
| Auto | Not available yet | — | — | — |
| z-low, z-high | Not released, no date | $6 | Not announced | $15 |
Two notes on that table. First, the z levels are not out. They are the highest levels of thinking and send requests through a different internal route that costs more; we will say more when there is a date. An Auto level, where Kael decides how much to think, is also not available yet. Second, the billing rule is simple and worth repeating: you pay for your own input tokens and the final output tokens only. The extra calls Kael makes inside the system, which can run to about twenty on a hard task, are never billed to you. The console has the exact numbers for your account.
Rules of thumb
- Start at Low. It is the default for a reason. Most requests do not need more.
- Move up to High or Max when being right matters more than being quick: a security review, a large refactor, a bug that touches several files. The research on spending extra compute points the same way: how much extra effort pays off depends on how hard the problem is.
- Turn thinking off when the question is simple and you want the fastest reply Kael can give.
When Kael is the wrong tool
None of this makes Kael right for every job. If you need the fastest response available, if your work is mostly creative writing, if you need PDFs, video or a language other than English today, or if you need downloadable or self-hosted weights, there are better fits. If you need the answer to be correct, and a few extra seconds are a fair price for that, that is what Kael is for.
Keep reading
- Introducing KaelKael is a composite intelligence: a system of models that drafts, checks and refines every answer, behind an API that works with the SDKs you already use. It is in public beta today.
- AI-Written Code Has a Security Problem. Here’s How to Review It.Four studies on the security of AI-written code, two bugs worth spotting on sight, and a review checklist that fits how machine-written code actually fails.