17 October 2026. Five sources side by side, a capability ranking, and what $100 of API spend actually buys from each model. Coverage decides which models can be ranked at all, so every chart states how many sources measured the model.
Three always-on agents landed in the last four weeks; all three now sit on the agents directory and the news feed:
Also new on the model board: Gemini 4 Carbon — an Artificial Analysis v5 score of 59, the highest independent figure on record; no DeepSWE run yet.
Left: models covered by three or more of the five sources, so a composite can be computed. Right: the rest — one or two sources only — shown at their raw DeepSWE score. Two measures on one 0–100 scale, so the panels are divided and styled apart; the amber qualifying bar applies to the left panel only.
Solid bars: composite percentile. Amber line = qualifying bar, 53.2.
Hollow bars: raw DeepSWE score, not a composite. These are not ranked against the panel on the left.
Quality-weighted tokens = tokens × (composite ÷ 53) × coverage factor. The composite is the five-source percentile from the chart above; 53 is its median, so a model sitting at the median scores a coefficient of exactly 1.00. Coverage factor: 1 source ×0.50, 2 ×0.75, 3 ×1.00, 4 ×1.25, 5 ×1.50 — a stated prior, not a measurement: a figure reproduced by more independent runs is worth more, and a figure one lab reports is worth less. ‡ Targeted-training penalty: a headline number that survives only in the maker's own harness is halved before any of this is computed. DeepSeek V4.1 Flash is the first case: 74.2 under mini-SWE-agent but 65.6 under Codex, and 30.0 on Terminal-Bench 3.0 where Opus 5 posts 43.3 — a score tuned to the task shape the benchmark rewards. The dagger marks the model, the coefficient shows the halved composite, and the raw table number stays visible everywhere else. Columns: weighted tokens, raw tokens before any adjustment, the coefficient, and how many sources cover the model. Hollow bar = factor below neutral, so a row held down by thin evidence reads differently from one held down by price.
Models sold only as API — DeepSeek, GLM, Qwen, MiMo — have no subscription tier at all, so $100 of API spend is the only denominator that covers every vendor on the same terms.
Coverage reorders the board. Laguna S 2.1 buys the most tokens of anything here at 800M, but its composite is 9.1 and only one source measures it, so the factor cuts it to 69M and 8th place. The multiplier works the other way too: Claude Opus 5.5 is covered by all five sources and has the highest composite on the board, so its 12.5M raw tokens count as 33M.
4 models have a DeepSWE score but no public price, so they cannot be priced: Muse Wonder Full, Gemini 4 Argon, Gemini 3.6 Flash, Gemini 3.5 Flash. Qwen3.8-Flash-Next is not on this list because it is the same measurement as Qwen3.8 Flash — the weights release and the production API name of one model, double-listed upstream and counted once here. That includes the DeepSWE leader Muse Wonder Full, which Meta sells only inside Muse Code.
Tokens = $100 ÷ blended API list price per 1M tokens, at a 3:1 input:output ratio. Nothing on this tab is adjusted for capability — it answers only how much text $100 buys, which is the input the weighted tab needs. Sorted by tokens. The second column is the blended price, the last is how many of the five sources cover the model.
The same $100 buys 800M from Laguna S 2.1 and only 5M from Claude Fable 5 — a 160× spread. That gap is the whole reason the weighted tab reorders anything: a model can be far cheaper per token and still lose once capability is priced in.
5 (Muse Wonder Full, Gemini 4 Argon, Qwen3.8-Flash-Next, Gemini 3.6 Flash, Gemini 3.5 Flash) of the board publish no list price and cannot appear here: Muse Wonder Full, Gemini 4 Argon, Qwen3.8-Flash-Next, Gemini 3.6 Flash, Gemini 3.5 Flash.
Only four subscription tiers have a measured quota, which is why this pane is short. The bars are effective dollars per benchmark-sized coding task; the right-hand column names the model the plan's quota was spent on. Monthly figures use 4.33 weeks, not four — a month averages 4.33 weeks, and rounding to four understates every plan by 8%.
Where these quota figures come from. No vendor publishes a quota-to-token conversion rate — that is why the site's own membership table can price only four of its nine products. So a subscription cannot be priced from published data at all; it has to be measured. The figures below are a community measurement, not a vendor disclosure and not our own test: finopsllm.com logged their real weekly usage from 11 September to 15 October 2026 and valued it at API list prices. Sample: one team, five tiers. Read them as an order of magnitude, not an invoice.
The weeks are full caps, not partial ones. The source runs Claude Max to 100% of the weekly limit every week, so no uplift is applied — the $658–$873 range already is the whole cap. Anthropic's “50%” figure is a different thing: on Max, Fable may consume at most 50% of your weekly limits, which caps how much Fable work a week can hold, not how full the week is. Codex windows that ended at 98–99% were scaled to 100% by the source.
The Pro $200 tier changes on 30 October. Until 29 October it is 20× Plus, about 5,154 tasks a week, which makes it the cheapest per task on this chart at $0.0090. From 30 October it drops to 10×, about 1,377 tasks, and lands at $0.0335 — level with Pro $100 and 3.7× worse than it is today. Both rows are in the table; only the current one is plotted.
| Plan | Price | API value / wk | Tasks / wk | $ / task | API $ per $1 | Flagship | Status | Quota measured by |
|---|---|---|---|---|---|---|---|---|
| ChatGPT Plus | $20 | $67 | 258 | $0.0179 | 14.5 | GPT-6.1 Sol | current | community log, finopsllm.com |
| Claude Max 5x | $100 | $761 | 875 | $0.0264 | 33.0 | Claude Opus 5.5 | current | community log, finopsllm.com |
| ChatGPT Pro $100 | $100 | $179 | 688 | $0.0336 | 7.8 | GPT-6.1 Sol | current | community log, finopsllm.com |
| ChatGPT Pro $200 | $200 | $1340 | 5154 | $0.0090 | 29.0 | GPT-6.1 Sol | 20x, until 29 Oct | community log, finopsllm.com |
| ChatGPT Pro $200 | $200 | $358 | 1377 | $0.0335 | 7.8 | GPT-6.1 Sol | 10x, from 30 Oct | community log, finopsllm.com |
Qwen3.8-Flash-Next is 125B of weights with 6B active per token, so it computes like a small model and loads like a large one. Strata keeps the weights in system RAM and treats VRAM as a cache for hot experts. That inverts the usual advice: VRAM decides how fast it runs, system RAM decides whether it runs at all.
| GPU VRAM | System RAM | Quant | Decode | Context | What it actually means |
|---|---|---|---|---|---|
| 8 GB | 16 GB | none | — | — | Not viable. “8 GB runs 125B” is a video title; the thread that measured it settles on 12 GB + 64 GB as the floor. A 35B-A3B at Q4 is the honest pick for this card. |
| 10 GB | 64 GB | none | — | — | No measured report exists at this tier. Treat it as 12 GB with less headroom for the expert cache, which is what runs out first at long context. |
| 12 GB | 64 GB | Q2_0 | 93 tok/s | 32K | The official reference machine (RTX 5070). This is the headline number, and it is the most aggressively compressed tier — not what you want to code with. |
| 12 GB | 64 GB | IQ3_S | 53 tok/s | 32K | The quality tier: 93.26 against 93.12 for BF16 on the vendor's own three-part eval, at under a quarter of the size. |
| 12 GB | 96 GB | IQ3_S | ~1,400 prefill | ~60K | This site's own machine. One request at a time; the client's 60-second connect deadline caps practical prompts near 60K tokens well before the model's 80K. |
| 16 GB | 64 GB | IQ3_S | 40–60 tok/s | 256–262K | Where it gets comfortable. Two independent reports: a 5060 Ti at 40+ and a 5080 laptop at 45–60 with the full context window. Long context eats the VRAM that was caching experts — the 5080 was down to about 4 GB for that. |
| 48 GB (2 cards) | 128 GB | IQ3_S | 105.8 tok/s | — | Dual GPU is where speed comes from. The weights are 83.6 GB, so this is still mostly a memory-bandwidth story, not a compute one. |
| 32 GB | 32 GB | any | OOM | — | A 5090D with only 32 GB of system RAM ran out of memory. VRAM without RAM still fails. |
Two things the marketing rounds off. The 93 tok/s figure is the Q2_0 tier; the quality tier runs at 53. The tier below it (IQ3_XXS) is reported to loop and over-think, so it is not a shortcut to lower VRAM.
Where it actually falls short. Three limits matter more than the speed numbers, because they decide whether this replaces a subscription at all.
Power only looks like a wash at Chinese rates. At 53 tok/s and a ~400 W whole-system draw, one million generated tokens takes 5.2 hours and burns about 2.1 kWh. At ¥0.6/kWh that is ¥1.26 per million tokens, roughly level with Qwen3.8-Flash's blended API price of ¥1.28. In Australia it is not level. At AU$0.35/kWh — a mid-range residential rate — the same 2.1 kWh costs about AU$0.74, roughly ¥3.4, which is two to three times the API price before any hardware is counted. A 48 GB card draws more than a 12 GB one, so the gap widens further.
Add the card and the picture inverts. A 12 GB machine is roughly ¥12,000; over three years that is ¥11 a day. Run it at a million tokens a day — five hours of continuous generation, which nobody actually does — and hardware alone adds ¥11 per million tokens, about nine times the API price. The honest break-even is not a token count. It is a constraint: data that cannot leave the machine, an API that is rate-limited, or a need to work offline.
Put together, the commercial verdict holds even after the VRAM path is priced in: 12 GB serves one request at a time and cannot see a whole repository; 48 GB fixes both, but the card alone costs more than years of API calls and, in Australia, the power bill on top of it already exceeds the API price. It is a tool for a specific constraint — data that cannot leave the machine, an API that is rate-limited, offline work — not a cheaper way to do the same job.
Can it reach 1M context? No — and the 8K you may have seen is a
config default, not a model limit. The deployment tutorials ship with
context: 4096 or max_model_len: 8192 because those settings fit any
card. The model itself is rated to 128K, and the community has run 262K on two
24 GB cards with an int8 KV cache, passing needle-in-a-haystack at all depths.
1M is not a setting anyone forgot to change. It would need roughly four times the KV cache of that 262K run, and decode already drops from 105–160 tok/s at short context to 60–73 tok/s at 16–30K as the cache grows. Extrapolate that curve and a 1M run lands in single-digit tokens per second on hardware that does not exist in consumer form. The ceiling is architectural, not configuration.
Sources: the Strata reference machine figures, the vendor's GSQ-RCO eval, measured prefill/decode curves across 1K–30K context, and community reports collected 1–8 October 2026. The 12 GB / 96 GB row is measured here.
Long-horizon software engineering. The site's current primary ranking.
Ultra-long-horizon, 20-hour budget per task. Far from saturation, so it separates the top.
Scores model+harness pairs, so it partly measures the agent, not the model.
Rotating questions resist contamination, but the coding column is saturated: the top eight sit above 90.
The only blind, human-voted signal here, so it is the natural anti-gaming anchor. Caveat: the newest models carry the fewest votes (top entries ~1,800-2,600), so their Elo is still provisional.