Kimi K3 vs Fable 5.1 vs GLM-5.3: The Open-Weight Frontier Has Arrived

Six weeks ago I would have written this article differently.

In July, Moonshot AI put 2.8 trillion parameters of frontier-class model on Hugging Face and let anyone download it. On 28 August, Z.ai finally released the GLM-5.3 weights it had been sitting on for two weeks — after finding that its own model could chain exploits together in ways nobody had asked it to. And on 1 September, Anthropic shipped Claude Fable 5.1 and made agentic work up to 45% cheaper without touching the headline price.

Three models. Three completely different answers to the question of what an AI lab owes the public. And for the first time since this whole thing started, the open-weight options are not the compromise choice.

That is the actual story of late 2026, and it is worth about eight thousand words, because the details are where all the money and all the mistakes live.

I have pulled the architecture papers, the model cards, the licence texts — properly, line by line, because two of the three are not what people are casually calling them — the vendor benchmarks, the neutral aggregator scores, the real per-token rates, and Ollama’s brand-new pricing sheet. Then I ran the cost maths on a normal working month instead of a launch-day scenario.

Here is what came out.

---

TL;DR — The 60-Second Verdict

GLM-5.3 is the best value in AI right now, and it is not close. Artificial Analysis scores it within half a point of Kimi K3 and about three and a half points behind Claude Opus 5, at $1.40 in and $4.40 out per million tokens. On the same agentic task, it costs roughly one sixth of what Fable 5.1 costs. The weights are downloadable. If you want one model to point your agent at and you are not running a $10-billion-revenue business, this is it.

Kimi K3 is the most capable thing you can legally download. 2.8 trillion parameters, 104 billion active, a genuine 1M context, native vision, the best agentic browsing score anyone has published (BrowseComp 91.2), and — the number that should end the “open models are behind” argument — 88.3 on Terminal-Bench 2.1, against Claude Fable 5’s 88.0 and GPT-5.6 Sol’s 88.8 on the same version. It also costs $3/$15 — more than double GLM-5.3 — and its 1.5 TB of weights need a rack, not a workstation. It is the model you use when the task is hard and long, and the model you cite when someone tells you open weights are a generation behind.

Claude Fable 5.1 is still the model you reach for when being wrong is expensive. It leads the field on sustained, multi-hour agentic work and on the messy debugging that never shows up cleanly on a leaderboard. Anthropic cut cache reads by 75% on 1 September, which makes long agent sessions dramatically cheaper than they were. It is also six times the price of GLM-5.3 per task, closed, and now carries anti-distillation restrictions that break some existing integrations.

The honest one-liner: the open-weight models have closed the capability gap to something like three to five months, and they have obliterated the price gap. What you are actually buying from Anthropic in September 2026 is reliability on the hardest 10% of work — and the right to not think about any of this.

And the twist nobody wants to say out loud: neither Kimi K3 nor GLM-5.3 ships under an open-source licence any more. Both moved to bespoke, revenue-gated terms this summer. Open weights, yes. Open source, no. Read the section on licences before your legal team does.

---

Quick Comparison Table

	Kimi K3	GLM-5.3	Claude Fable 5.1
Maker	Moonshot AI	Z.ai (Zhipu AI)	Anthropic
Released	16 July 2026 (API) · 27 July (weights)	14 August 2026 (API) · 28 August (weights)	1 September 2026
Weights available	Yes	Yes	No
Licence	Kimi K3 License (custom, revenue-gated)	glm-5.3 License (custom, revenue-gated)	Proprietary
Total parameters	2.8T	753B	Undisclosed
Active per token	104B (16 of 896 experts)	~40B (estimated)	Undisclosed
Architecture	KDA + Attention Residuals, Stable LatentMoE, 69 KDA + 24 Gated MLA layers	MoE, same base as GLM-5.2, gains from post-training only	Undisclosed
Context window	1,048,576	1,000,000	1,000,000
Max output	131,072 default (up to 1,048,576)	128,000	128,000
Multimodal input	Text, image, video (MoonViT-V2)	Text only	Text, image
Thinking	Always on	Always on, reasoning_effort low/high/max	Always on, adaptive, per-message effort (beta)
Input price / 1M	$3.00	$1.40	$10.00
Cached input / 1M	$0.30	$0.26	$0.25
Output price / 1M	$15.00	$4.40	$50.00
AA Intelligence Index	59.7	59.5	Not yet scored (Fable 5: 62.1)
Cost per AA eval task	$0.84	$0.68	— (Opus 5: $2.34)
Self-host footprint	~1.5 TB (native MXFP4)	~1.5 TB BF16 / ~750 GB FP8	N/A
On Ollama	kimi-k3:cloud	glm-5.3:cloud	Via Claude Code / Claude Desktop as a client

All pricing is first-party list pricing. Artificial Analysis figures are from the September 2026 index snapshot; Fable 5.1 launched on 1 September and had not been independently scored at the time of writing.

---

Why This Three-Way Is The Comparison That Matters

For two years the open-versus-closed conversation had a comfortable shape: closed models were better, open models were cheaper, and you picked your spot on that trade-off. Everyone knew where they stood.

That shape broke this summer.

Nathan Lambert, who tracks this more carefully than almost anyone, puts the current capability gap between frontier open-weight and frontier closed models at three to five months — down from the six to nine months people were quoting a year ago. At the time he wrote, Kimi K3 sat at #2 on the Vals AI index and near the top of Artificial Analysis’s, beaten only by Claude Fable and GPT-5.6 Sol Max. The September index snapshot I use later in this article has it fourth, behind Grok 4.6. Either way: that is not “good for an open model.” That is a podium finish.

Meanwhile the usage data has gone somewhere genuinely surprising. Chinese-origin models captured roughly 61% of all tokens routed through OpenRouter by May 2026. The US share of that traffic collapsed from about 70% to about 30% over twelve months. Meta’s Llama — the model that started the open-weight wave — fell below 1% of routed volume. Google’s share went from roughly 37% to 13%. OpenRouter’s own 100-trillion-token study with a16z found open-weight models accounting for about a third of all token volume on the platform.

You can argue about what OpenRouter traffic represents. It over-indexes on developers, hobbyists and cost-sensitive workloads, and it under-counts enterprise contracts that never touch a router. Fine. But it is the largest public dataset we have on what people actually choose when they can choose freely, and the direction is unambiguous.

So the question in September 2026 is no longer “are open models good enough yet.” It is much sharper:

Given three models that all clear the bar, which one do you point your agent at — and what does being wrong actually cost you?

That is a question about benchmarks, prices, licences and infrastructure, in roughly that order of how much people think about them and exactly the reverse order of how much they matter.

---

What Kimi K3 Actually Is

Moonshot AI announced Kimi K3 on 16 July 2026 and released the full weights on 27 July. It is, by parameter count, the largest open-weight model anyone has ever published — 2.8 trillion total parameters, roughly 75% larger than DeepSeek V4 Pro.

That number is less impressive than it sounds and more impressive than it sounds, in that order.

The architecture, in plain language

Kimi K3 is a mixture-of-experts model that activates 104 billion parameters per token, selecting 16 experts from a pool of 896. So while the total is 2.8T, any given forward pass touches under 4% of the weights. That is where the economics come from: enormous stored knowledge, moderate inference cost.

The interesting engineering is in the attention stack. K3 uses 93 layers built from 69 KDA (Kimi Delta Attention) layers and 24 Gated MLA layers — a hybrid linear-to-full attention design at roughly a 3:1 interleave ratio. KDA is a linear-attention variant that runs in linear time relative to sequence length rather than quadratic, which is what makes the 1M context economically viable instead of merely advertised. Moonshot reports up to a 75% KV-cache reduction and up to 6× decode throughput at 1M context as a result.

Layered on top is Attention Residuals (AttnRes), which Moonshot describes as a drop-in replacement for standard residual connections, and a Stable LatentMoE framework for routing. The combination is claimed to deliver roughly a 2.5× improvement in overall scaling efficiency versus Kimi K2.

Vision comes from MoonViT-V2, a 401M-parameter encoder, and it is native rather than bolted on — K3 handles text, images and video in one model.

One more detail that matters for anyone thinking about self-hosting: K3 was trained with native MXFP4 quantisation-aware training, with experts in MXFP4 and activations in MXFP8. This is not a post-hoc quantisation. The published checkpoint is the quantised model, which is why 2.8 trillion parameters land at roughly 1.5 TB on disk rather than the ~5.6 TB a BF16 checkpoint of that size would need.

The benchmark story

Moonshot’s published numbers are strong across the board, and unusually, several have held up under independent evaluation:

• Terminal-Bench 2.1: 88.3 — the highest published score on that version of the benchmark
• FrontierSWE: 81.2
• DeepSWE: 67.5
• BrowseComp: 91.2 — state of the art for agentic web research
• GPQA Diamond: 93.5
• MMMU-Pro: 81.6 / 83.4 (vision)
• SWE Marathon: 91.0
• OfficeQA Pro: 81.3
• AutomationBench: 30.8
• LMArena Frontend Code Arena: 1,679 Elo — first place, ahead of Claude Fable 5 (1,631) and GPT-5.6 Sol (1,618), winning six of seven frontend domains

That last one deserves a pause. An open-weight model you can download for free took first place on a human-preference frontend coding arena, ahead of the flagship closed models from the two best-funded labs in the world. Whatever you think about arena benchmarks as a methodology, that is a headline that would have been unthinkable in 2025.

On the aggregate indexes it lands slightly lower: 59.7 on the Artificial Analysis Intelligence Index, third overall, behind Claude Opus 5 (63.0) and Claude Fable 5 (62.1). Moonshot’s own showcase numbers — GDPval-AA v2 at 1,687 and AA-Briefcase at 1,527 — put it third and second respectively in those knowledge-work evaluations. On the Vals Index v2 it lands at 57.8%, against Claude Opus 5’s 67.2%, Claude Fable 5’s 66.0% and GPT-5.6 Sol’s 63.7% — the widest open-versus-closed gap in any index I found, and worth holding in mind against the coding numbers.

The demos, and how to read them

Moonshot published two long-horizon autonomy demonstrations that got a lot of attention: a 48-hour autonomous run completing a full chip design pipeline (a 4mm design closing timing at 100 MHz, simulating at 8,700+ tokens/second), and a reproduction of the astrophysics I-Love-Q relation in about two hours, against the one-to-two weeks a senior researcher would typically need.

These are genuinely impressive and I would not build a purchasing decision on them. Vendor-run, vendor-scaffolded, vendor-selected demonstrations tell you what a model can do on a good day with expert supervision, not what it does in your repository on a Tuesday. Treat them as an existence proof for long-horizon capability, not as a spec.

---

Show Image Two published architectures and one black box. The open models tell you exactly how they work; the closed one tells you what it scores.

What GLM-5.3 Actually Is

GLM-5.3 has the strangest release story of the three, and it is the one worth telling properly, because it is the first time a major lab has visibly hesitated over publishing weights for reasons other than commercial ones.

Z.ai announced GLM-5.3 on 14 August 2026 with the tagline “Built to Code. Ready for Cyber Defense.” The model is a 753-billion-parameter mixture of experts, with roughly 40 billion active per token according to community estimates derived from the GLM-5.2 configuration. It carries a 1M-token context window and a 128K max output, and — unlike GLM-5.3-Flash, which is a completely different model — it is text-only.

“Scaling post-training is all we did”

The most interesting technical fact about GLM-5.3 is that there is no new base model. It reuses the same pretrained foundation as GLM-5.2. Every gain came from dramatically extended post-training, which Z.ai summarised as: “Scaling post-training is all we did for GLM-5.3.”

The deltas are not small:

Benchmark	GLM-5.2	GLM-5.3
Terminal-Bench 3.0	4.6	28.3
DeepSWE v1.1	46.2	66.9
CyberGym	77.2%	84.5%

A six-fold improvement on Terminal-Bench and a twenty-point jump on DeepSWE, from the same base weights, is a genuinely important result. It says the frontier still has a lot of headroom in post-training, which is by far the cheaper half of the training bill. That is precisely why Chinese labs operating with, as Lambert puts it, “orders of magnitude less capital” than American ones are keeping pace.

The two weeks Z.ai spent not shipping

Z.ai said at launch that the weights would follow “in stages following rigorous safety evaluations,” with a target of roughly two weeks. Its Hugging Face repository listed 28 August. That date came, went by a matter of hours, and then the weights appeared alongside a technical writeup explaining the delay.

The reason was cyber capability. During evaluation, Z.ai reported that GLM-5.3 identified 2,436 vulnerabilities across 269 open-source projects, of which 1,097 were rated critical or high severity. More to the point, the model demonstrated multi-stage exploit-chain reasoning — autonomously chaining exploitation steps together — which Z.ai characterised as behaviour that was “not fully intended” and that “continued compounding as training scaled.”

I want to be careful here, because this is easy to read as either marketing or alarmism and it is probably neither. A model that is good at finding vulnerabilities is good at finding vulnerabilities; the defensive and offensive uses are the same capability pointed in different directions. Z.ai’s benchmark spread reflects that honestly: CyberGym 84.5% (vulnerability discovery, where it leads) against ExploitBench 54.4% (exploitation, where Claude Fable 5 scores 78.0%). The lab deliberately optimised for the defensive half and it shows.

What is genuinely notable is that a lab took a two-week hold on a flagship release and published its reasoning. Whether you find the reasoning convincing, the precedent is new.

Where GLM-5.3 actually lands

Z.ai’s published comparison chart does not claim a clean sweep, which is refreshing:

Benchmark	GLM-5.3	Best comparator
AutomationBench	48.2%	GLM-5.3 leads
CyberGym	84.5%	GLM-5.3 leads
GDPval-AA v2	1,769	GLM-5.3 leads
Terminal-Bench 3.0	28.3%	GPT-5.6 Sol: 34.6%
DeepSWE v1.1	66.9%	GPT-5.6 Sol: 72.7%
ExploitBench	54.4%	Claude Fable 5: 78.0%
Code Bench (50K tokens)	31.4%	—

Independently, Artificial Analysis puts it at 59.5 on the Intelligence Index — statistically indistinguishable from Kimi K3’s 59.7, from a model with roughly a quarter of the parameters.

One caveat from that same evaluation that nobody in the marketing mentions: GLM-5.3 generated 170 million output tokens across the Artificial Analysis suite against a 72 million median for its class. It is verbose. reasoning_effort defaults to max and thinking cannot be disabled, so you are paying for a lot of deliberation whether the task earns it or not. Even so, the total cost to run the full evaluation came to $0.68 per task, against $0.84 for Kimi K3 and $2.34 for Claude Opus 5 — so the verbosity does not erase the price advantage. It just narrows it.

---

What Claude Fable 5.1 Actually Is

Anthropic released Claude Fable 5.1 on 1 September 2026, alongside Claude Mythos 5.1 — the same model with different safeguard configuration, available only through trusted-access programmes for cybersecurity and life-sciences work.

The positioning is specific and, I think, correct: this is “a model built for work that does not finish in one prompt.” Anthropic is not claiming a general intelligence leap. It is claiming that sustained, multi-hour agentic sessions go better.

The numbers

Benchmark	Fable 5	Fable 5.1	Mythos 5.1
Terminal-Bench 4.0	42.0%	55.8%	60.9%
Terminal-Bench-Science 0.1	24.7%	52.6%	—
AutomationBench	17.1%	31.4%	—
CursorBench 3.2.0	70.5%	73.4%	—
OSWorld 2.0 (partial)	72.9%	77.9%	—
Humanity’s Last Exam (with tools)	63.8%	65.0%	—
GDPval-AA v2	—	1,853	—

For external context on the same ruler: GPT-5.6 Sol scores 52.3% on Terminal-Bench 4.0, so Fable 5.1’s 55.8% takes the lead and Mythos 5.1’s 60.9% extends it.

The Terminal-Bench-Science jump — 24.7% to 52.6%, a clean doubling — is the one I would weight most heavily if your work involves scientific computing or data pipelines. And on Browserbase’s hardest computer-use benchmark, Fable 5.1 completed 82% of tasks against Claude Opus 5’s 74%.

Anthropic also reports roughly a 60% reduction in cyber-safety false positives — the model refusing legitimate security work because it pattern-matched to something dangerous. If you have ever had a coding assistant decline to help you write a rate limiter, you will understand why that matters.

The pricing change is the actual news

Headline rates did not move: $10 per million input tokens, $50 per million output. What changed is the cache read multiplier, and it changed a lot.

	Fable 5	Fable 5.1
Input	$10.00	$10.00
Output	$50.00	$50.00
Cache write (5 min)	$12.50	$12.50
Cache write (1 hour)	$20.00	$20.00
Cache read	$1.00	$0.25

That is a 75% cut, achieved by moving the cache-read multiplier from the standard 0.1× of base input to 0.025×. Anthropic quotes roughly 25% cheaper for typical workloads and up to 45% cheaper for highly agentic work — and that second number is real, because agentic loops are overwhelmingly cache reads. A 60-turn agent session re-reads the same accumulated context dozens of times. The Batch API halves input and output on top of that, landing at $5/$25.

This is a smart, targeted price cut. It makes the specific thing Fable 5.1 is best at — long sessions — meaningfully cheaper without devaluing the model generally.

Three breaking changes, one regression

Before you upgrade a production integration, read these properly.

1. Forced tool use is gone. Requests using tool_choice: "any" or tool_choice: "tool" now return a 400 error. Thinking is always on and cannot be bypassed, and forcing a tool call would skip it. You must use tool_choice: "auto".

2. Thinking blocks are one-directional. Fable 5.1 can read thinking blocks produced by earlier Claude models, but earlier models cannot read Fable 5.1’s. Only Mythos 5.1 can. If your architecture switches models mid-conversation to save money, that fallback now forces a re-plan.

3. Editing history invalidates thinking blocks. For accounts created after 31 August 2026, editing prior turns, the system prompt, or the tool array invalidates all subsequent thinking blocks — errors or silent drops. This is an explicit anti-distillation measure and it breaks a common pattern where agent frameworks rewrite context between turns.

And one regression worth knowing: parallel tool calling is reportedly more variable in 5.1, sometimes issuing a single call per turn where 5 would batch several. On a long agent loop that costs wall-clock time.

There is also a tokenizer detail that catches people out on cost comparisons: Fable 5.1 uses the same tokenizer as Claude Opus 4.7, which produces roughly 30% more tokens than the tokenizer in older Claude models for the same text. If you are benchmarking cost against a 2025 baseline, adjust for that before concluding anything.

---

The Benchmark Problem: Three Models, Three Different Rulers

Here is the part most comparison articles get wrong, and it is worth being blunt about.

You cannot line these three models up on Terminal-Bench. Look:

• Kimi K3: 88.3 on Terminal-Bench 2.1
• GLM-5.3: 28.3 on Terminal-Bench 3.0
• Fable 5.1: 55.8 on Terminal-Bench 4.0

Those are three different benchmarks that share a name. Each version got substantially harder than the last — that is the entire point of releasing a new version. Reading those three numbers as a ranking would tell you Kimi K3 is three times better than GLM-5.3 at terminal work, which is nonsense.

The same problem applies to AutomationBench, where version numbers are inconsistently reported, and to the SWE-bench family, where the Verified, Pro and Marathon variants measure genuinely different things. Labs are not doing this to deceive anyone — they run the evaluation that was current when they trained, and evaluations turn over every few months now. But the effect on a casual reader is the same as deception, so it is worth flagging loudly.

What you can legitimately compare, within a version:

On Terminal-Bench 2.1: Kimi K3 (88.3), GPT-5.6 Sol (88.8), Claude Fable 5 (88.0) and GLM-5.3-Flash (84.3). Four models, one ruler. This is the comparison that actually matters and I have given it its own table in the next section.

On Terminal-Bench 4.0: Fable 5.1 (55.8) against GPT-5.6 Sol (52.3). Fable wins.

Beyond that, be sceptical of anyone showing you a single bar chart with all three of this article’s headline models on a Terminal-Bench axis. It cannot be done honestly.

---

Where They Actually Meet: The Cross-Comparable Numbers

Strip out the benchmark-version mismatches and three comparisons survive.

1. Artificial Analysis Intelligence Index (September 2026)

Independently run, same methodology across every model, no vendor involvement in selection.

Rank	Model	Score	Open weights
1	Claude Opus 5	63.0	No
2	Claude Fable 5	62.1	No
3	Grok 4.6	60.9	No
4	Kimi K3	59.7	Yes
5	GLM-5.3	59.5	Yes
6	GPT-5.6 Sol	58.9	No
7	Qwen3.8 Max Preview	58.1	Weights pending
8	GLM-5.3-Flash	57.5	Yes (MIT)
31	MiniMax M3	45.4	Yes

Fable 5.1 had not been independently scored at the time of writing — it launched the day before. Given 5.1’s benchmark deltas over Fable 5, expect it to land at or above 62.1 when it is.

A note on precision: different snapshots of this index round differently — one September pull has Kimi K3 and GLM-5.3 both at 60 and GPT-5.6 Sol at 61. The ordering at the top is stable; the sub-point gaps are not. Do not build an argument on half a point.

Read that table carefully. The best open-weight model is 3.3 points behind the best closed model on the broadest neutral index available. A year ago that gap was double digits.

2. Terminal-Bench 2.1 — the one version where three of them meet

This is the single most useful table in the article, and I nearly missed it. Kimi K3, Claude Fable 5 and GPT-5.6 Sol were all scored on the same version of Terminal-Bench:

Model	Terminal-Bench 2.1	Open weights
GPT-5.6 Sol	88.8	No
Kimi K3	88.3	Yes
Claude Fable 5	88.0	No
GLM-5.3-Flash	84.3	Yes (MIT)

Half a point separates a model you can download from the best closed model on the same benchmark, on the same version, on terminal-native agentic work.

That is the number to remember. Not the index aggregate, not the vendor chart — this one. On the specific task shape that agentic coding actually is, the gap is inside the noise.

One caveat, stated by the source and worth repeating: all of Kimi K3’s published figures are max-effort runs, at reasoning_effort maximum and temperature 1.0. Different labs use different evaluation harnesses and different effort settings, so even same-version comparisons carry more uncertainty than a clean table suggests.

3. Cost to run the same evaluation suite

If the table above is the best capability comparison, this is the best value comparison — because it is the only figure that bundles capability, verbosity, reasoning overhead and price into a single number:

Model	Cost per Intelligence Index task
GLM-5.3	$0.68
Kimi K3	$0.84
Claude Opus 5	$2.34

Same tasks, same scoring, actual invoices. GLM-5.3 delivers 94% of Opus 5’s index score for 29% of the cost.

4. GDPval-AA v2 (knowledge work)

Model	Score
Claude Fable 5.1	1,853
Claude Fable 5 Max	1,815
GLM-5.3	1,769
GPT-5.6 Sol Max	1,747.8
Kimi K3	1,687

This one is worth caveating: it is assembled from vendor-published charts rather than a single independent run, and the “Max” suffixes indicate different effort settings. But the ordering is broadly consistent across sources, and it says something real — on general knowledge work, as opposed to coding, the closed models still hold a clearer lead than the coding benchmarks suggest.

That is the pattern across all three comparisons. The open models have essentially caught up on coding and agentic tasks. They are still a step behind on broad knowledge work. If your workload is the former, the case for paying closed-model prices is weak. If it is the latter, it is still defensible.

---

Show Image Three and a bit points separate the best closed model from the best downloadable one. That gap was double digits twelve months ago.

The Cost Maths, With Real Numbers

Benchmarks are abstract. Invoices are not.

The scenario

One medium feature, done agentically: roughly 60 tool-calling turns, averaging 45,000 input tokens per turn as context accumulates, and 2,000 output tokens per turn.

• Total input: 2.7M tokens
• Total output: 120K tokens
• Assumed prompt cache hit rate: 80% (2.16M cached, 540K fresh)

Claude Fable 5.1

Component	Tokens	Rate	Cost
Fresh input	540K	$10.00/M	$5.40
Cached input	2.16M	$0.25/M	$0.54
Output	120K	$50.00/M	$6.00
Total			≈ $11.94

Kimi K3

Component	Tokens	Rate	Cost
Fresh input	540K	$3.00/M	$1.62
Cached input	2.16M	$0.30/M	$0.65
Output	120K	$15.00/M	$1.80
Total			≈ $4.07

GLM-5.3

Component	Tokens	Rate	Cost
Fresh input	540K	$1.40/M	$0.76
Cached input	2.16M	$0.26/M	$0.56
Output	120K	$4.40/M	$0.53
Total			≈ $1.85

And for reference — GLM-5.3-Flash

Component	Tokens	Rate	Cost
Fresh input	540K	$0.15/M	$0.08
Cached input	2.16M	$0.03/M	$0.06
Output	120K	$0.50/M	$0.06
Total			≈ $0.21

The ratios

• GLM-5.3 is 6.5× cheaper than Fable 5.1 for identical work
• Kimi K3 is 2.9× cheaper than Fable 5.1
• GLM-5.3 is 2.2× cheaper than Kimi K3
• GLM-5.3-Flash is 58× cheaper than Fable 5.1, at 57.5 on the intelligence index against Fable 5’s 62.1

Scaling to a working month

Four such tasks a day, twenty working days — 80 agentic runs:

Model	Monthly token cost
Claude Fable 5.1	≈ $955
Kimi K3	≈ $326
GLM-5.3	≈ $148
GLM-5.3-Flash	≈ $17

Three honest caveats on these figures

Cache writes are excluded. Fable 5.1 charges $12.50/M for 5-minute cache writes, and a long session writes cache repeatedly. Including writes moves Fable’s real number up, not down. The 80% hit rate is also optimistic for short sessions.

Reasoning tokens are billed output tokens. All three models have always-on thinking. GLM-5.3 in particular is documented as verbose — 170M output tokens against a 72M class median across the AA suite — so its real-world output volume runs above what a naive turn count suggests. The $0.68-per-task figure already accounts for this, which is why I trust it more than my own model above.

Fable 5.1’s tokenizer produces ~30% more tokens than older Claude models for the same text. If you are comparing against a historical Claude bill, adjust.

Even after all three corrections, the ordering does not change and the magnitude barely does. Closed-frontier work costs roughly six times what the best open-weight model costs, per completed task.

---

Show Image The same 60-turn agentic task at each vendor’s list pricing. The vertical axis is the entire argument for open weights.

Licences: What “Open” Actually Buys You In 2026

This is the section I would most like people to read, because the vocabulary has drifted badly and it is going to cost somebody a lot of money.

Neither Kimi K3 nor GLM-5.3 is open source. Both publish downloadable weights under bespoke licences with revenue-triggered conditions. That is a meaningfully different thing from MIT or Apache 2.0, and the difference lands squarely on the kind of business that would most benefit from self-hosting.

The Kimi K3 License

You will see “Modified MIT” repeated all over the internet for K3. It is wrong — that described K2. K3 ships under a custom document with two distinct gates:

The Model-as-a-Service gate. If you provide third parties with access to model inference or fine-tuning — where those third parties control inputs, parameters or training data — and “the aggregate revenue of the Licensee and its affiliates exceeds 20 million US dollars” over any consecutive 12 months, you must negotiate a separate commercial agreement with Moonshot. Note aggregate revenue, across all affiliates, not revenue attributable to K3. A €25M-turnover consultancy that resells inference is over the line even if the AI business is a rounding error.

The attribution gate. Products exceeding 100 million monthly active users or $20 million monthly revenue must display “Kimi K3” prominently in the product interface.

The exemption that matters most: purely internal use is unrestricted. Running K3 to support your own developers, researchers, legal team or general employee productivity does not trigger either gate. For the overwhelming majority of businesses — including essentially all of mine — that is the relevant clause, and the answer is that you are fine.

The clause that is new relative to K2 is the $20M MaaS gate. K2 only required attribution above its thresholds. K3 adds a much lower revenue gate aimed specifically at commercial inference resellers. Moonshot is not trying to stop you using the model; it is trying to stop cloud providers building a business on it for free.

The glm-5.3 License

Z.ai’s flagship went a different direction, and it is a bigger break with precedent than most coverage acknowledged.

GLM-5.2 shipped under MIT. GLM-5.3-Flash shipped under MIT. GLM-5.3 did not.

The custom licence permits individuals and ordinary businesses to run, deploy and fine-tune the model with no additional restrictions. The single gate is aimed at hyperscalers: an entity whose “aggregate revenue of the Licensee and its affiliates exceeds 10 billion US dollars (or the equivalent in other currencies) in total over any consecutive 12 months” must pass Z.AI’s security review before using the model or its derivatives for any commercial purpose.

That is a $10 billion threshold. It excludes almost everyone. But two details in the fine print deserve attention:

First, the licence explicitly carves out app developers embedding the model in features, and resellers merely routing requests to other hosts. The target is narrow and clearly labelled: companies that want to host GLM-5.3 commercially at scale.

Second — and this is the genuinely awkward part — the licence publishes no criteria, timeline or appeal process for that security review. It states only that its “scope and method… shall be reasonably determined by Z.AI.” If you are a large enterprise, that is an unbounded dependency on a foreign vendor’s discretion, and your procurement team will say so.

Also worth noting: despite the two-week cyber-capability hold that preceded release, the licence contains no acceptable-use restrictions, no cyber carve-outs and no output-ownership claims. The safety concern shaped the release timing, not the release terms.

So what is actually still MIT?

GLM-5.3-Flash. 320B parameters, 18B active, natively multimodal, MIT-licensed, 57.5 on the intelligence index, and $0.15/$0.50 per million tokens — currently half that under a promotional discount running to 9 September 2026. If your requirement is genuine unrestricted permissive licensing rather than merely downloadable weights, that is where the frontier currently sits, and it is remarkably high.

The practical summary

	Kimi K3	GLM-5.3	GLM-5.3-Flash	Fable 5.1
Weights downloadable	Yes	Yes	Yes	No
OSI-style open source	No	No	Yes (MIT)	No
Restriction trigger	$20M revenue (MaaS)	$10B revenue (MaaS)	None	N/A
Attribution required	Above 100M MAU / $20M-month	Copyright notice only	Copyright notice only	N/A
Internal use restricted	No	No	No	N/A
Fine-tuning permitted	Yes	Yes	Yes	No
Acceptable-use policy	Standard	None in licence text	None	Anthropic AUP applies

For a typical German Mittelstand business, an agency, or a consultancy running models internally or embedding them in a product: all three open options are usable without negotiating anything. The gates exist to catch AWS, not you. But “read the licence” has gone from pedantic advice to actual advice, and if you are above about €20M turnover and reselling inference in any form, get it in front of counsel before you deploy.

---

The Real Case For Open Models

I want to make this argument properly rather than as a slogan, because “open models are great” is not an argument and the actual reasons are more interesting than the cheerleading.

1. The price collapse is not a subsidy, it is structural

The instinctive objection to cheap Chinese models is that the pricing is loss-leading and will normalise upward. Some of it certainly is. But the structural point stands independently: when weights are public, inference becomes a commodity market. Twenty hosting providers compete to serve the same model, and none of them can charge a capability premium because none of them has a capability moat. That is why GLM-5.3 runs at $1.40/$4.40 and Fable 5.1 runs at $10/$50 for scores three points apart.

Closed-model pricing includes the R&D amortisation, the margin, and the fact that there is exactly one seller. Open-weight pricing includes electricity, hardware amortisation and a thin margin. Those are different businesses, and the gap will not close by open models getting more expensive.

The evidence that this is real rather than temporary: DeepSeek captured roughly 17% of token usage on Vercel by May 2026 while holding about 1% of revenue share. That is not a pricing anomaly. That is what commoditisation looks like on a chart.

2. Exit rights change your negotiating position even if you never exercise them

Most teams reading this will not self-host. The hardware section below explains why — Kimi K3 needs a rack. But the option has value regardless.

If Anthropic raises prices, deprecates the model you built on, changes its acceptable-use policy in a way that breaks your product, or has a bad quarter, your recourse with a closed model is a migration project. With an open-weight model your recourse is downloading a file you could have downloaded any time. You may never do it. The fact that you could is what makes the vendor relationship a commercial one rather than a dependency.

This is not theoretical. Fable 5.1 shipped with three breaking changes on 1 September, one of which invalidates thinking blocks when you edit conversation history for accounts created after 31 August. If that pattern is load-bearing in your architecture, you are re-engineering on Anthropic’s schedule, not yours.

3. Data residency stops being a project

For anyone operating under GDPR, this is the argument that actually closes deals.

With a closed API, every prompt leaves your infrastructure. You need a processor agreement, a transfer impact assessment if the processor is outside the EEA, a data-flow map, and an answer for your DPO about what happens to the data at rest. All of that is doable. It is also weeks of work per vendor, repeated whenever the vendor changes anything.

With open weights on infrastructure you control — your own hardware, or a German or EU GPU host — the cross-border transfer question does not arise, because there is no transfer. The model runs where your data already lives. Legal review goes from a transfer assessment to a licence read.

For German and EU clients this is frequently the deciding factor, and it is worth being precise about the caveat: using GLM-5.3 through Z.ai’s API does not give you this. You get it from running the weights yourself, or from a provider hosting them in your jurisdiction. The licence makes that legal; it does not make it automatic.

4. Inspectability is real, if underused

Open weights mean you can examine the architecture, run your own evaluations on the actual model rather than an endpoint that might be silently updated, quantise it to fit your hardware, fine-tune it on your domain, and — importantly — pin a version forever.

That last one is underrated. Closed APIs get updated behind stable model IDs. Behaviour drifts. Prompts that worked stop working, and you cannot diff the change because you cannot see it. A local checkpoint is byte-identical in a year’s time.

5. The competitive pressure benefits everyone, including closed-model users

Look at what happened this summer. Kimi K3 lands in July at $3/$15 with frontier-adjacent scores. GLM-5.3 lands in August at $1.40/$4.40 within half a point of it. And on 1 September, Anthropic cut cache reads by 75%.

I am not claiming direct causation — Anthropic does not publish its pricing rationale and cache-read cuts are a natural optimisation. But a market with credible cheap substitutes prices differently from one without them, and the substitutes got credible this year. If you use closed models exclusively, the open-weight ecosystem is still quietly making your bills smaller.

6. Post-training is where the gains are, and it is cheap

GLM-5.3’s headline result — a six-fold Terminal-Bench improvement from the same base weights — is the most strategically important number in this entire article, and it is not about GLM.

It says the expensive part of building a frontier model (pretraining) is increasingly a solved, commoditised input, and the differentiating part (post-training, RL environments, long-horizon task design) is comparatively affordable. That is why four Chinese labs with a combined valuation of about $159 billion are keeping pace with American labs valued at multiples of that. Lambert’s assessment is that Chinese labs are running with “orders of magnitude less capital.”

For anyone downstream, the implication is straightforward: the number of credible model vendors is going up, not down. Plan your architecture accordingly.

7. The ecosystem effects compound

Qwen passed one billion cumulative downloads on Hugging Face, overtaking Llama, and now anchors over 200,000 tagged models and 113,000+ derivatives — roughly 40% of all new LLM derivatives on the platform are Qwen-based. That is a tooling, quantisation, fine-tuning and deployment ecosystem that exists only because the weights are public.

You benefit from that ecosystem whether or not you contribute to it. GGUF conversions, vLLM kernels, LoRA adapters, quantisation recipes, evaluation harnesses — all of it exists because thousands of people could get their hands on the actual weights.

8. It is where the developers already went

Chinese-origin models at ~61% of OpenRouter tokens. US model share down from ~70% to ~30% in a year. Four of the five most-used models on the router are Chinese-origin. Xiaomi’s MiMo models alone account for roughly 21% of routed tokens and about 22% of all coding traffic.

Developer behaviour is a leading indicator. It was a leading indicator for Docker, for Postgres, for Linux. Betting against it has a poor historical record.

---

…And The Honest Case Against

If I only wrote the section above, this would be an advert.

Open weights are not open source, and the vocabulary drift is a real problem. Two of the three models here ship under bespoke revenue-gated licences with no OSI approval. GLM-5.3’s security-review clause has no published criteria or appeal process. If your compliance framework requires OSI-approved licensing, the honest answer is that your options are GLM-5.3-Flash, DeepSeek’s MIT-licensed flagships, and a shrinking list of others.

Vendor benchmarks remain vendor benchmarks. Every headline number Moonshot and Z.ai published is self-reported and self-selected. Where neutral aggregators have measured, the numbers broadly hold up — which is genuinely to both labs’ credit — but “broadly hold up” is doing work in that sentence.

Self-hosting is a fantasy for most teams. Kimi K3 is 1.5 TB and Moonshot recommends 64+ accelerators. GLM-5.3 needs 8×H200 at FP8 as a bare minimum. The exit right is real; the exercise cost is a data centre.

Support is what you make it. When Fable 5.1 breaks, there is a company with an SLA. When your self-hosted GLM-5.3 deployment produces garbage at 300K context on a Friday night, there is a GitHub issue and your own competence.

Geopolitics is a real procurement input. All three open-weight options discussed here come from Chinese labs. For some clients — public sector, defence-adjacent, certain regulated industries — that is a hard blocker regardless of licence terms or where the weights run. It is not my job to tell you whether that concern is well-founded. It is my job to tell you it will come up in the meeting.

The closed models still lead on general knowledge work. GDPval-AA v2 has Fable 5.1 at 1,853 against GLM-5.3’s 1,769 and Kimi K3’s 1,687. On coding the gap is gone. On broad professional knowledge work it is not.

---

Show Image Downloadable weights, three different sets of strings. Only GLM-5.3-Flash is still MIT.

Ollama In 2026: The Pricing Change That Actually Matters

Ollama has quietly become the most important piece of infrastructure in this conversation, and on 31 August 2026 it changed how it charges in a way that is worth understanding properly.

What changed

Ollama moved its Pro, Max and Team plans from GPU-time billing to industry-standard per-token pricing, with a pool of usage credits included in every plan. The company’s stated reason is refreshingly concrete: models like Kimi K3 made GPU-time metrics impossible to predict. When one model activates 104B parameters and another activates 3B, “an hour of GPU” stops meaning anything to the person paying.

The new plans

Plan	Price	Included monthly usage	Concurrency
Free	$0	Small monthly credit, starter models	1 request
Pro	$20/mo (or $200/yr)	$60 of usage	3 requests
Max	$100/mo	$300 of usage	10 requests
Team	$500/mo	$1,000 shared, unlimited users	10 requests
Enterprise	Custom	Custom	Custom

Read the Pro row again. $20 buys $60 of tokens. That is a 3× multiplier on included usage, and when the pool runs out you continue at exactly the same published per-token rate — no penalty tier, no service fee.

What was removed

This is the part developers actually noticed: no 5-hour resets and no weekly caps. Anyone who has hit a rolling usage window mid-refactor will understand why that mattered more than the price. The monthly pool refreshes on your subscription date and, importantly, does not roll over — so size your plan to your normal month, not your busiest one.

The terms that matter for EU work

Three commitments in the announcement are directly relevant if you are handling client data:

• Zero data retention. Prompts and responses are never logged and never trained on.
• Hosting in the US and Europe, plus Singapore for a limited set of Qwen models.
• Per-request cost visibility in your account — you can see exactly what each call cost.

For a German consultancy that is a materially better compliance story than most gateway providers offer, though “hosted in Europe” is a routing statement rather than a contractual data-residency guarantee. If residency is a hard requirement rather than a preference, ask Ollama for it in writing before you assume it.

The actual per-token rates

This is where it gets interesting. Ollama publishes rates per model, and they track first-party pricing closely:

Model on Ollama	Input / 1M	Cached / 1M	Output / 1M
kimi-k3	$3.00	$0.30	$15.00
glm-5.3	$1.40	$0.26	$4.40
mistral-large-3	$0.50	$0.50	$1.50
gemma4	$0.14	$0.05	$0.40
nemotron-3-super	$0.015	$0.015	$0.60

Run the monthly maths from earlier through this. Eighty agentic runs a month on GLM-5.3 costs about $148 in tokens. A Max plan at $100/month covers $300 of usage — so the same workload that would cost roughly $955/month on Fable 5.1 fits comfortably inside a $100 Ollama subscription with headroom to spare.

That is the entire open-model economic argument compressed into one line on an invoice.

Show Image Eighty agentic runs a month on GLM-5.3 fit inside a $100 Ollama Max plan with change. The same work on Fable 5.1 is a $955 invoice.

What else Ollama shipped in 2026

The pricing change did not happen in isolation. The last few months have been busy:

• 25 August — Claude Desktop support. Ollama now works as a third-party gateway provider for Claude Desktop, so you can drive open models through Anthropic’s own client.
• 26 August — v0.33.0. The Claude Desktop gateway integration landed, prefill recovery was restored to the cache, and Ollama disabled Claude Code’s token-countdown system message, which was invalidating the KV cache on every turn. That last one is a quiet but significant performance fix.
• 26 August — v0.33.1. MLX support for Qwen3.8 Flash Next, structured output, and a fix for GPU timeouts when loading models from slower storage.
• 28 August — v0.33.2. Dark mode restored, macOS handoff fixed, and Claude Desktop proxy requests kept alive during model catalogue updates.
• 20 August — v0.32.15. New desktop onboarding, and metadata caching between requests that cut time-to-first-token by roughly half.
• 11 August — NVIDIA Nemotron 3.5 Lightning, a 30B model tuned for agentic workflows with tool calling on personal hardware.
• 10 August — Meta’s Muse Glimmer, a 30B multimodal model under Apache 2.0, accelerated by Ollama’s MLX engine. Worth noting given Llama’s collapse in routed usage — Meta is still shipping genuinely permissive weights.
• 9 July — $88M funding round, with Ollama reporting 8.9 million developers.
• 29 June — Gemma 4 on MLX up to 90% faster via multi-token prediction, which disproportionately benefits coding agents on Apple Silicon.
• 5 June — v0.30 added GGUF compatibility through llama.cpp, broadening hardware support well beyond Apple Silicon.

The through-line is that Ollama has stopped being “the easy way to run a small model on your laptop” and become a general-purpose gateway that happens to also run models locally. The cloud catalogue now includes kimi-k3:cloud, glm-5.3:cloud, glm-5.3-flash, deepseek-v4-pro, deepseek-v4-flash, minimax-m3, qwen3.5 across seven sizes, gpt-oss at 20b and 120b, gemma4, the Nemotron 3 family and mistral-large-3.

---

Setting It All Up: Copy-Paste Configs

Ollama + Claude Code (the fastest path)

Ollama ships a one-command launcher that handles the environment wiring for you:

bash

ollama launch claude

If you would rather do it manually — which you should if you are scripting it — install Claude Code first:

bash

# macOS / Linux
curl -fsSL https://claude.ai/install.sh | bash

# Windows (PowerShell)
irm https://claude.ai/install.ps1 | iex

Then point it at Ollama:

bash

export ANTHROPIC_AUTH_TOKEN=ollama
export ANTHROPIC_API_KEY=""
export ANTHROPIC_BASE_URL=http://localhost:11434

And run against whichever model you want:

bash

# A local model
claude --model qwen3.5

# A cloud model — note the :cloud suffix
claude --model kimi-k3:cloud

Or inline, without exporting anything globally:

bash

ANTHROPIC_AUTH_TOKEN=ollama \
ANTHROPIC_API_KEY="" \
ANTHROPIC_BASE_URL=http://localhost:11434 \
claude --model glm-5.3:cloud

Two things that will bite you.

First, do not export ANTHROPIC_BASE_URL permanently in your shell profile. It is a global variable and it will silently redirect every Anthropic-speaking tool on your machine to Ollama, including the one you wanted talking to Anthropic. Scope it per-project or per-invocation.

Second, set your context length to 64k or higher for anything working on a real repository. Ollama’s default is smaller, and a coding agent that quietly runs out of window will just start forgetting things rather than erroring.

For CI, Docker or scripted runs, --yes skips the interactive prompts:

bash

ollama launch claude --model glm-5.3:cloud --yes -- -p "how does this repository work?"

GLM-5.3 direct from Z.ai

If you want first-party routing rather than going through Ollama, Z.ai exposes three protocol endpoints:

Protocol	Base URL
Anthropic Messages	https://api.z.ai/api/anthropic
OpenAI Chat Completions	https://api.z.ai/api/coding/paas/v4
OpenAI Responses	https://api.z.ai/api/v1

An OpenCode provider block for GLM-5.3:

json

{
  "$schema": "https://opencode.ai/config.json",
  "provider": {
    "zai": {
      "npm": "@ai-sdk/openai-compatible",
      "name": "Z.AI",
      "options": {
        "baseURL": "https://api.z.ai/api/coding/paas/v4",
        "apiKey": "{env:ZAI_API_KEY}"
      },
      "models": {
        "glm-5.3": {
          "name": "GLM-5.3",
          "limit": { "context": 1000000, "output": 128000 },
          "options": { "reasoning_effort": "high", "temperature": 1 }
        }
      }
    }
  },
  "model": "zai/glm-5.3"
}

Important upgrade note: GLM-5.3 requires reasoning to be enabled. If your existing configuration sets thinking.type: "disabled", that will now fail. Change it to "enabled" and set reasoning_effort: "low" if you want the old latency profile back.

reasoning_effort is your main quality-versus-cost dial: low for latency-sensitive calls, high for substantial work, max (the default) for problems that have genuinely defeated high. Given the documented verbosity, I would run high as an everyday setting rather than leaving max on and wondering where the output tokens went.

The routing setup I would actually recommend

None of this is a “pick one” decision. The correct answer for most teams is a three-tier routing table, and every serious agent harness supports per-agent models.

json

{
  "$schema": "https://opencode.ai/config.json",
  "model": "zai/glm-5.3",
  "small_model": "ollama/gemma4",
  "agent": {
    "plan": {
      "description": "Architecture, root-cause analysis, anything expensive to get wrong",
      "model": "anthropic/claude-fable-5-1"
    },
    "build": {
      "description": "The bulk of implementation work",
      "model": "zai/glm-5.3",
      "options": { "reasoning_effort": "high" }
    },
    "research": {
      "description": "Long-context reading, web research, multi-source synthesis",
      "model": "ollama/kimi-k3:cloud"
    },
    "grunt": {
      "description": "Renames, docstrings, test scaffolding, lint fixes",
      "model": "ollama/glm-5.3-flash"
    }
  }
}

The reasoning behind each line:

• Planning gets Fable 5.1. Planning is where a bad decision costs you the most downstream tokens, and long-horizon coherence is precisely what 5.1 was built for. It is also where you spend the fewest tokens, so the price premium applies to the smallest slice of your bill.
• Building gets GLM-5.3. Best capability-per-euro on the market, and the bulk of your token spend lands here.
• Research gets Kimi K3. BrowseComp 91.2 and a genuine 1M context make it the best available option for reading a lot of things and synthesising them.
• Mechanical work gets GLM-5.3-Flash. At $0.15/$0.50 it is effectively free, and renaming a symbol across 40 files does not need frontier reasoning.
• small_model gets something tiny for the harness’s own housekeeping — title generation, summarisation, internal utility calls.

You are not choosing a winner. You are building a gearbox. And write the model IDs so that swapping one is a one-line change, because in this market you will be making that change again within the quarter.

---

What You Can Actually Run Locally (The Hardware Reality)

Let me kill an assumption before it costs somebody money.

You cannot run Kimi K3 or GLM-5.3 on a workstation. Not with a 5090. Not with two.

Kimi K3

• ~1.5 TB of weights in native MXFP4 — and remember, that is the quantised checkpoint, not a starting point for further compression
• Moonshot recommends a minimum of 64 accelerators for competitive serving
• Realistic self-hosting starts at multi-node clusters; reference deployments use GB300 NVL72 racks
• There is no official Ollama library entry for local Kimi K3 and no consumer GGUF conversion worth pointing you at
• Reports of it running on clusters of consumer RTX 5090s exist, but “a cluster of 5090s” is not a laptop and the throughput is not comparable

GLM-5.3

• ~1.5 TB in BF16, roughly 750 GB at FP8
• Minimum viable single node: 8× H200 (1,128 GB of GPU memory) at FP8, leaving around 375 GB for KV cache
• BF16 needs two 8×H200 nodes, or a single 8×B300 node (2,304 GB)
• A single 8×H200 node in BF16 is too small for the weights plus cache

Show Image The frontier open models need a rack. The 24 GB tier is where “runs on my machine” actually lives — and it has got very good.

So what does “local AI” actually mean in September 2026?

It means a different tier of model, and that tier has got genuinely good:

Model	VRAM	What it is for
Qwen3.8-27B	24 GB at Q4	Best all-rounder on consumer hardware — 61.7% SWE-bench
gpt-oss:20b	16 GB	Best small model, adjustable reasoning effort
Gemma 4 E4B	~6 GB	Vision plus tool calling on a modern laptop
Mistral 7B	8 GB	Fastest general-purpose option, 40–60 tok/sec
DeepSeek-R1 7B	5 GB	Chain-of-thought reasoning on a laptop GPU
Llama 4 Scout	~55 GB at Q4	10M context, multimodal — workstation territory

A Qwen3.8-27B scoring 61.7% on SWE-bench, running entirely on a 24 GB consumer GPU with no network connection, is a remarkable thing that would have sounded like science fiction eighteen months ago. It is not GLM-5.3 and it is not pretending to be.

The honest framing: open weights at the frontier buy you sovereignty and price, not local execution. Open weights in the 7B–30B range buy you genuine local execution, at a real but acceptable capability cost, and that is the tier where “runs on my machine, sees no network” is an achievable requirement.

The architecture that works for most of my clients is exactly that split: a small local model for anything touching genuinely sensitive data, and a hosted open-weight frontier model for everything else — with the weights available as insurance rather than as a deployment plan.

---

Where Each Model Actually Breaks

No hype. Here are the honest weaknesses.

Kimi K3 weaknesses

It is expensive for an open model. $3/$15 is 2.1× GLM-5.3’s input rate and 3.4× its output rate for essentially the same intelligence index score. If you are choosing K3 over GLM-5.3, be clear about what you are buying with that premium — usually it is the vision stack or the browsing performance.

The licence has the lower gate. A $20M aggregate-revenue MaaS threshold catches far more organisations than GLM-5.3’s $10B. If inference resale is anywhere in your business model, K3 is the more constrained of the two.

Self-hosting is out of reach for almost everybody. 1.5 TB and 64+ accelerators is a serious infrastructure commitment. The exit right is more theoretical here than with any other model in this comparison.

Broad knowledge work trails. GDPval-AA v2 at 1,687 puts it behind GLM-5.3, both Claude Fables and GPT-5.6 Sol Max. It is a coding and agentic specialist that happens to be enormous.

GLM-5.3 weaknesses

Text only. No image input, no video. If your workflow includes screenshot debugging, design-to-code or document vision, GLM-5.3 simply cannot do it and you need GLM-5.3-Flash, Kimi K3 or Fable 5.1 instead. This is the single most common configuration mistake I expect people to make, because the model IDs look related and are not.

It is verbose, and verbosity is billed. 170M output tokens against a 72M class median across the AA suite. reasoning_effort defaults to max, and thinking cannot be turned off. Budget for more output tokens than your turn count implies.

The licence is no longer MIT, and the security-review clause is unbounded. For most readers the $10B threshold makes this academic. For anyone near it, “scope and method shall be reasonably determined by Z.AI” is not a clause your legal team will enjoy.

Terminal-Bench 3.0 at 28.3 trails GPT-5.6 Sol’s 34.6. On the specific benchmark closest to terminal-native agentic coding, it is behind the closed competition on the same ruler.

It is new to open weights. Released 28 August. The community has had days, not months. Long-tail deployment bugs have not surfaced yet.

Claude Fable 5.1 weaknesses

The price. Roughly 6.5× GLM-5.3 per completed agentic task, even after the 75% cache-read cut. For most work that gap is not defensible on capability grounds any more.

Three breaking changes. Forced tool use returns 400. Thinking blocks do not travel backwards to older models. Editing conversation history invalidates thinking blocks on accounts created after 31 August 2026. Any of these can break a working integration on upgrade.

Parallel tool calling regressed. Reports of one call per turn where Fable 5 batched several. On a long agent loop that is wall-clock time you are paying for twice.

Zero exit optionality. No weights, no self-hosting, no version pinning beyond what Anthropic offers, no inspection. When it changes, you adapt.

The tokenizer inflates comparisons. ~30% more tokens than older Claude models for the same text, which makes historical cost comparisons misleading in Anthropic’s favour if you are not careful.

---

The Decision Framework: Six Scenarios

Show Image Six scenarios, six answers. Find the row that sounds like your week.

1. “I want one model. Set it, forget it, keep the bill sane.”

GLM-5.3. Within half a point of Kimi K3 and roughly three points of the best closed model on the neutral index, at $1.40/$4.40. Run it through Ollama on a Pro or Max plan, set reasoning_effort: high, and get on with your work. The only thing that should push you off this answer is needing image input.

2. “My work is visual — UI, design-to-code, screenshot debugging, documents.”

Kimi K3 or GLM-5.3-Flash, not GLM-5.3. K3’s MoonViT-V2 handles text, images and video natively and scores 81.6/83.4 on MMMU-Pro. GLM-5.3-Flash is the budget option with native multimodality and an MIT licence. GLM-5.3 is text-only and will simply refuse the input.

3. “Long autonomous sessions where being wrong is expensive.”

Claude Fable 5.1. This is what it was built for and the benchmarks back it: Terminal-Bench-Science doubled, 82% on Browserbase’s hardest computer-use tasks against Opus 5’s 74%, and the largest published gains on multi-hour agentic work. The 75% cache-read cut makes exactly this workload up to 45% cheaper than it was. Pay the premium where a mistake costs more than the tokens.

4. “EU data residency is a hard requirement.”

GLM-5.3-Flash if you need MIT, GLM-5.3 if you need capability. Self-host on your own hardware or an EU GPU provider and the cross-border transfer question stops existing. Budget 8×H200 for GLM-5.3 at FP8; Flash is far more tractable at 320B/18B. If self-hosting is out of budget, Ollama’s Europe hosting with zero data retention is the pragmatic middle ground — but get the residency commitment in writing rather than inferring it from a marketing page.

5. “Small team, tight budget, coding all day.”

GLM-5.3-Flash as default, GLM-5.3 for hard problems, Ollama Pro at $20. Flash costs $0.15/$0.50 — currently half that until 9 September — and scores 57.5 on the intelligence index. Twenty dollars buys sixty dollars of tokens with no weekly caps. For a two-to-four person team this is close to unbeatable. The GLM Coding Plan at $18/month (Lite) is the alternative if you prefer a fixed quota to a credit pool.

6. “I need to justify this to a procurement or legal team.”

GLM-5.3-Flash. It is the only model in this comparison under a standard OSI-approved licence (MIT), it is natively multimodal, it scores 57.5 on the neutral index, and the weights are on Hugging Face with no revenue gates, no attribution mandates and no security-review clause. When the question is “what can we defend in a contract review,” permissive licensing beats three points of benchmark every time.

---

What I Would Watch Over The Next Quarter

Whether Fable 5.1 lands above 62.1 on the Artificial Analysis index. It launched the day before this article and has not been independently scored. Its benchmark deltas over Fable 5 suggest it should, but “should” is not “did,” and the gap to Kimi K3’s 59.7 is the number the whole open-versus-closed argument turns on.

Whether the licence drift continues. In eight weeks we went from GLM-5.2 under MIT to GLM-5.3 under a bespoke licence with a discretionary security review, and from Kimi K2’s modified-MIT to K3’s revenue-gated terms. If GLM-6 and K4 tighten further, “open weights” becomes a marketing term rather than a meaningful category. GLM-5.3-Flash staying MIT is the counter-signal worth tracking.

Whether other labs adopt Z.ai’s staged-release pattern. A two-week hold with a published safety rationale is a new norm. If it holds, it is a good one. If it becomes a reason weights ship later and later, it is a soft path to not shipping them at all.

Independent replication of the cyber capability claims. 2,436 vulnerabilities across 269 projects is an extraordinary number and it is entirely self-reported. Somebody neutral needs to check it, because if it is accurate it reframes the entire open-weights safety conversation, and if it is not, it was effective marketing.

Ollama’s per-token rates six months from now. $20 for $60 of usage is an aggressive introductory posture from a company that raised $88M in July. Whether those multipliers survive contact with real unit economics is the single biggest variable in the “cheap open models” thesis for small teams.

Whether local models close on the 30B tier. Qwen3.8-27B at 61.7% SWE-bench on 24 GB is the most under-discussed result of the year. The frontier gets the headlines; the 24 GB tier is what changes what an ordinary business can do without an API key.

---

Frequently Asked Questions

Is Kimi K3 really open source? No. Kimi K3’s weights are freely downloadable from Hugging Face, but under a custom “Kimi K3 License,” not an OSI-approved open-source licence. Model-as-a-Service operators whose aggregate revenue exceeds $20 million over any consecutive 12 months must negotiate a separate commercial agreement with Moonshot, and products above 100 million monthly active users or $20 million monthly revenue must display “Kimi K3” in their interface. Purely internal use is unrestricted.

Is GLM-5.3 better than Kimi K3? They are effectively tied on the neutral aggregate index — 59.5 against 59.7 on Artificial Analysis. GLM-5.3 is 2.2× cheaper per agentic task and scores higher on knowledge work (GDPval-AA v2: 1,769 vs 1,687). Kimi K3 is natively multimodal, leads on agentic browsing (BrowseComp 91.2) and took first place on Arena.AI’s frontend code arena. Choose GLM-5.3 for cost and text-based coding; Kimi K3 for vision, browsing and long-horizon research.

How much cheaper are open models than Claude Fable 5.1? On a modelled 60-turn agentic task, GLM-5.3 costs about $1.85 against Fable 5.1’s $11.94 — roughly 6.5× cheaper. Kimi K3 costs about $4.07, roughly 2.9× cheaper. GLM-5.3-Flash costs about $0.21, roughly 58× cheaper. Over 80 runs a month that is $148 versus $955.

Can I run Kimi K3 or GLM-5.3 locally? Not on consumer hardware. Kimi K3 is roughly 1.5 TB even in its native MXFP4 format and Moonshot recommends 64+ accelerators. GLM-5.3 needs a minimum of 8×H200 (1,128 GB) at FP8. For genuine local execution, look at Qwen3.8-27B (24 GB at Q4), gpt-oss:20b (16 GB) or Gemma 4 E4B (~6 GB).

What changed in Claude Fable 5.1? Released 1 September 2026. Cache reads dropped 75% from $1.00 to $0.25 per million tokens, making typical workloads about 25% cheaper and agentic workloads up to 45% cheaper; input and output stayed at $10/$50. Terminal-Bench 4.0 rose from 42.0% to 55.8%, Terminal-Bench-Science from 24.7% to 52.6%, AutomationBench from 17.1% to 31.4%. Three breaking changes affect forced tool use, thinking-block portability and history editing.

What is Ollama’s new pricing? From 31 August 2026, Pro, Max and Team plans use per-token pricing with included credits: Pro $20/month for $60 of usage, Max $100 for $300, Team $500 for $1,000 shared across unlimited users. The 5-hour and weekly caps were removed entirely, there are no service fees, credits do not roll over, and all plans carry zero data retention with hosting in the US and Europe.

Which of these models is genuinely MIT-licensed? Only GLM-5.3-Flash — a separate 320B/18B natively multimodal model released 26 August 2026, scoring 57.5 on the Artificial Analysis index at $0.15/$0.50 per million tokens. GLM-5.3 and Kimi K3 both use bespoke revenue-gated licences; Claude Fable 5.1 is fully proprietary.

Why can’t I compare these models on Terminal-Bench? Because they were each evaluated on a different version. Kimi K3’s 88.3 is on Terminal-Bench 2.1, GLM-5.3’s 28.3 is on 3.0, and Fable 5.1’s 55.8 is on 4.0. Each version is substantially harder than the last, so the numbers are not on the same scale. Compare within a version only. On Terminal-Bench 2.1, for example, Kimi K3 scores 88.3 against Claude Fable 5’s 88.0, GPT-5.6 Sol’s 88.8 and GLM-5.3-Flash’s 84.3 — that comparison is valid, and it is the one worth quoting.

Should I use Ollama or go direct to the vendor? Ollama if you want one billing relationship, one API surface, easy model switching and EU/US hosting with zero data retention — its per-token rates track first-party pricing closely. Direct if you need first-party features like Z.ai’s reasoning_effort controls at full fidelity, vendor SLAs, or subscription plans such as the GLM Coding Plan. Many teams run both and route by workload.

Does GLM-5.3 support images? No. GLM-5.3 is text-only. GLM-5.3-Flash — a completely different model despite the similar name — is natively multimodal and handles text, image, video and file input. Sending images to the wrong model ID is the most common early mistake with the GLM family.

---

The Bottom Line

Twelve months ago the open-weight question was whether these models were usable. Six months ago it was whether they were competitive. In September 2026 it is genuinely: what are you still paying a closed-model premium for?

There is a real answer to that question, and it is narrower than it used to be. Claude Fable 5.1 leads on the hardest sustained agentic work, on general knowledge work, and on the class of debugging where a model needs to hold a messy problem in its head for hours without drifting. Anthropic’s 75% cache-read cut targets exactly that workload. If your failure cost exceeds your token cost, that premium is rational.

For everything else, the maths has moved. GLM-5.3 delivers 94% of Claude Opus 5’s index score at 29% of the cost. Kimi K3 scores 88.3 on Terminal-Bench 2.1 against Claude Fable 5’s 88.0 on the same version, and took first place on LMArena’s Frontend Code Arena ahead of both flagship closed models. Ollama will sell you $60 of tokens for $20 and remove the usage caps while doing it. That combination did not exist in the spring.

But do not let the enthusiasm skip the fine print, because there are two of them and both matter.

The first is licensing. “Open weights” and “open source” have quietly stopped meaning the same thing. Kimi K3 and GLM-5.3 both ship under bespoke, revenue-gated licences. The gates are high enough that most readers are unaffected — but “most readers are unaffected” is not the same as “unrestricted,” and GLM-5.3’s undefined security-review clause is a genuine procurement risk for large enterprises. GLM-5.3-Flash under MIT is the last fully permissive frontier-adjacent option, which is precisely why it deserves more attention than it gets.

The second is that self-hosting is mostly aspirational. 1.5 TB of weights and 64 accelerators is not an exit plan for a mid-sized business. What open weights buy you at this tier is a competitive inference market, price transparency, version pinning, jurisdiction choice, and a negotiating position. Those are worth a great deal. They are not the same as running the thing in your basement.

The setup I would actually build: GLM-5.3 as the default, Fable 5.1 on planning and the genuinely hard problems, Kimi K3 for vision and long-horizon research, GLM-5.3-Flash for the grunt work, and a 27B local model for anything that must never leave the building. Route by workload, not by loyalty. Write your configuration so the model IDs are a one-line change.

Because the only prediction I am confident about is that this article will need updating before Christmas.

---

Are you running any of these three in production? I am particularly interested in whether GLM-5.3’s verbosity shows up as a real cost problem at scale, and whether anyone has actually put the Kimi K3 licence in front of counsel and got a clear read on the MaaS definition. Get in touch — corrections and counter-evidence welcome, and this article gets updated when the picture changes.

Last updated: 2 September 2026.