My AI Stack In September 2026: Who Builds, Who Digs, Who Decides
AIThis post was created with the assistance of artificial intelligence (AI).

🔍 Read the full analysis: My AI Stack In September 2026: Who Builds, Who Digs, Who Decides on ThorstenMeyerAI.com

Prime Big Deal Days · Oct 6–7Offer from Amazon

Get the latest gadgets delivered free — and shop member deals

  • Fast, free delivery on millions of items
  • Access to Prime Big Deal Days deals on October 6–7
  • Prime Video, Amazon Music and more included
Start your free Prime trial Free trial for eligible customers · Cancel anytime
As an affiliate, we earn on qualifying purchases.

TL;DR

Thorsten Meyer says he uses Claude Opus 5.5 for building and GPT-6.1 Sol for detailed reviews, following Sol’s release on Sept. 29. His comparison of Artificial Analysis Intelligence Index v4.3.x scores finds a wide gap in estimated task costs, but the index does not establish which model performs best on a particular team’s work.

Thorsten Meyer says he has made Claude Opus 5.5 his main model for building software and GPT-6.1 Sol his model for detailed investigation and review, following Sol’s release on Sept. 29. His updated stack reflects a comparison in which several models score within about 20 points on the Artificial Analysis Intelligence Index, while estimated costs per task vary widely.

Meyer’s comparison uses the Artificial Analysis Intelligence Index v4.3.x, which he describes as a measure of general capability rather than a verdict on any particular workload. In the listed top settings, Opus 5.5 scores 58 at an estimated $5.98 per task; GPT-6.1 Sol at xhigh scores 51 at $0.39. The figures are estimates from the index, not reported costs for Meyer’s own completed tasks.

The other models in his comparison fill narrower roles. Sonnet 5.5 scores 56 at max effort and costs an estimated $7.60 per task; Fable 5.1 scores 53 at $7.63; and GPT-6 Astra scores 53 at $3.26. GPT-6 Luna scores 37 at $0.07, which Meyer assigns to classification, extraction and routing. He says Astra and Fable are options for cases where his own tests favor them.

Effort settings also change the estimates. For Opus 5.5, the index lists a score of 54 for $1.82 per task at high and 56 for $3.46 at xhigh. Meyer uses those settings for development and harder problems, respectively. At max, the score rises to 58 while estimated cost reaches $5.98. For Sonnet 5.5, the listed max setting costs $7.60 for a score of 56; Meyer favors its high setting, listed at 47 for $1.08.

At a glance
updateWhen: Published Sept. 29, 2026; GPT-6.1 Sol w…
The developmentThorsten Meyer published a Sept. 29 update assigning Opus 5.5 to building and newly released GPT-6.1 Sol to detail work and review, based on model scores and estimated task costs.

Opus builds. Sol reviews. Jev decides.

The September 2026 AI stack in one page: six frontier models on one price curve, and a decision model for the high-volume judgements that do not need a sentence.
Scores: Artificial Analysis Intelligence Index v4.3.x. Data as of 29 September 2026.
BuildsClaude Opus 5.5 at high or xhigh effort
Digs and reviewsGPT-6.1 Sol at high or xhigh effort
DecidesJev on high-volume yes/no and routing calls

One price tape, six models

Put every model on the same cost-per-task ruler and capability looks compressed. The bill does not.
Price tape: cost per task of six models on a log scale, from GPT-6 Luna at $0.07 to Fable 5.1 at $7.63$0.05$0.10$0.50$1$5$10cost per task, log scale: each tick is a different order of magnitudeGPT-6 Lunaindex 37 · $0.07GPT-6.1 Solindex 51 · $0.39 (xhigh)GPT-6 Astraindex 53 · $3.26Opus 5.5index 58 · $5.98Sonnet 5.5 · index 56 · $7.60Fable 5.1 · index 53 · $7.63about 100× from the cheapest to the priciest, but only 21 index points between them

Score against cost, at every effort setting

Each dot is an effort level. Opus 5.5 at high already matches Astra and Fable at max on this index, for less money.
Intelligence Index score against cost per task for each effort setting of six models$0.01$0.10$1$102030405060cost per Intelligence Index task, log scaleindexOpus high / xhigh: my defaultOpus 5.5Sonnet 5.5Fable 5.1GPT-6 AstraGPT-6.1 Sol (new)GPT-6 Sol (Sep 22), dashedGPT-6 Lunaup and to the left is better
Astra and Fable are shown at their top published setting. Luna starts at $0.0045 per task. GPT-6.1 Sol has no low or max setting published yet.

The effort dial moves the bill more than the model

Going from medium to max on Opus costs 4.46× more for 7 points. That is why I run high or xhigh.

Claude Opus 5.5

$0.55
42
$1.34
51
$1.82
54
$3.46
56
$5.98
58
low
medium
high
xhigh
max
Solid bars are where I run it. Max adds 2 points over xhigh for 73% more cost.

Claude Sonnet 5.5

$0.41
36
$0.59
41
$1.08
47
$2.74
52
$7.60
56
low
medium
high
xhigh
max
Best value is high. At max it writes about 193k output tokens per task, the most measured.

GPT-6.1 Sol: near-Astra scores at a fraction of the price

Launched 29 September at $2 in and $10 out per 1M tokens. It sits 1 to 2 points under Astra and Fable, and Opus xhigh still leads it by 5.

Three published settings

SettingIndexCost per taskOutput tokensFirst token
medium48$0.2115M5.3 s
high50$0.3225M57 s
xhigh51$0.3936M69 s
Median for comparable models is 82M output tokens. High and xhigh are not interactive: plan for a wait before the first token.

Same score band, very different bill

GPT-6.1 Sol xhigh
$0.39index 51
Opus 5.5 high
$1.82index 54
GPT-6 Astra max
$3.26index 53
Opus 5.5 xhigh
$3.46index 56
Fable 5.1 max
$7.63index 53
Cost per Intelligence Index task. A one-point gap is inside the noise.

My stack: who builds, who reviews

Opus does the work. A second model family reviews it, because a different reviewer catches what the author cannot see.
Stack diagram: Opus 5.5 builds at high effort, escalates to xhigh, and sends every change to GPT-6.1 Sol for review; Astra or Fable give a second opinionOpus 5.5 · xhighhard problems: architecture,migrations, trust boundariesOpus 5.5 · highMAIN BUILDERfeatures, APIs, multi-filework, refactorsescalate when it gets hardGPT-6.1 Solhigh or xhighdigs into details andreviews every change$0.32–0.39 per taskdifffindingsAstra or Fablesecond opinion, 8 to 20×the cost per taskif they disagreeSonnet 5.5 · Lunaside work: scopedsubtasks, bulk checksand routingFailed review? Hand Opus the failing case and the evidence.Never just “try harder”: effort cannot supply a missing requirement.
Effort is not capability. Turning the dial up does not make a model smarter.
Effort cannot fill gaps. A missing requirement stays missing at any setting.
Different model, same spec. That is not independent review if both read the same flawed brief.
Green tests are not approval. Passing tests only prove what the tests cover.

Cheaper tokens are not cheaper work

Illustrative, not measured: $1 of model time plus 4 minutes of review at $45 an hour. Halving the model price saves 12.5% of the total. One extra minute of review erases it.
$4.00
review $3.00
model $1.00
Baseline
$3.50
review $3.00
model $0.50
Model price cut 50%
$4.25
review $3.75
model $0.50
Cheaper model plus 1 extra minute of review
Track cost per accepted result: model, tools, review and rework, divided by the results someone actually uses.

Read the numbers with four warnings

The index movesFable scored 66 on an earlier version and 53 on v4.3. Compare within one version only.
Fallback is includedFlagged cyber and biology tasks route to older Anthropic models, now on Sonnet 5.5 too.
Max is not productionReal deployments run medium or high, where gaps narrow and costs fall.
Your work decidesShadow-test on your own tasks. Budget cost per task, not per token.

Part 2: Jev, the model that decides instead of writing

Jev cannot write, summarise or extract. It answers narrow typed questions with a probability and an honest confidence, in under a second, for about $0.04 per million input tokens.

One call in, typed answers out

Your code, not Jev, decides what to do with each answer, usually by confidence band.
Jev flow: state and typed questions go into one Jev call; typed answers with confidence come out; code acts alone, escalates the gray zone, or logsStatea ticket, a story,a site profile,a log line …+ typed questions,many per callJevone call0.3 to 0.9 s$0.042 / M tokens inAnswersnoul: 0.03choice: billing p 0.91, conf 0.86score: 2.7 of 3 conf 0.64code branches on thisAct aloneconf ≥ 0.8Escalategray zone toLLM or humanLogmeasure first

Three question types

noul
A yes/no question. Returns the probability of yes, 0 to 1.
gates, flags, filters
choice
Pick one option. Returns the choice, a probability per option, and a confidence.
routing, classification, taxonomy
score
Rate on your ordered levels. Returns a position (it can fall between levels) plus a confidence.
quality, fit, severity, priority

Confidence is the superpower

In my own measurement on a 31-topic classification, Jev agreed with a frontier LLM almost every time it was sure, and rarely when it was not. So: decide the clear cases, route the gray zone.
confidence 0.8 or higher
97–99%
all answers
89%
confidence below 0.5
42%
Agreement with a frontier LLM, my production data, September 2026, rounded.

Three uses running in my publishing operation

About 90,000 decisions so far. Checks I could only afford on a sample now cover everything.
$2.01
Language check
78,889 articles scanned overnight. 1,576 in the wrong language found, 1,553 fixed in place.
22%
Relevance gate
About 10,000 story-to-site pairings judged in 3 days. Only 22% were clearly on-topic.
89%
Classifier fallback
Agreement with the primary LLM across 31 topics, used when that LLM errors.

The fit test, then the shadow test

Use Jev only when all four hold. Then prove it on past decisions before it acts on anything.
High volumeThousands of small calls, not a handful of big ones.
Narrow questionNo multi-step reasoning needed.
Cheap errorsOr unsure cases go to something smarter.
Heuristic failsVisibly, and measured, not assumed.
  1. Replay 300 to 500 past decisions
  2. Compare overall and per confidence band
  3. Read 20 disagreements, decide who was right
  4. High band at 95% or better?
  5. Own flag, off by default
  6. Canary on 5 to 10 units
  7. Roll out in the confident band only

24 use cases, sorted by how well they fit

Start from the strong fits. The amber ones need a measurement before you trust them, and the red ones fail one of the four conditions.
in productionstrong fitmeasure firstpoor fit

Proven in production

  • 1Relevance gate
  • 2Language check
  • 3Classifier fallback

Publishing and content

  • 4Thin-source detector
  • 5Same-event dedupe
  • 6Product fits roundup
  • 7Disclosure present
  • 8Headline quality
  • 9Comment moderation

Commerce and support

  • 10Support-ticket routing
  • 11Return-reason coding
  • 12Review to feature complaints
  • 13Catalogue taxonomy
  • 14Order-fraud pre-triage

Software and AI systems

  • 15LLM guardrail
  • 16RAG passage filter
  • 17Citation check
  • 18Tool and intent routing
  • 19Log-line triage
  • 20PR risk triage

Business ops and home

  • 21Inbox triage
  • 22Expense categorisation
  • 23Lead qualification
  • 24Smart-home intent

Limits, cost and one hard rule

No writing, summarising or extractionPair it with an LLM for the write step.
No world knowledgePut a snippet in the state; a bare name means nothing.
Reads your wording literallyA rewording moved my results about 2 points. Freeze it, re-measure after changes.
Weaker on non-English, maths, datesKeep those checks on an LLM. Early access, hosted API only.
100,000 decisions ≈ $2.50
About 60M input tokens at $0.042 per million, output free, roughly 600 tokens per three-question call. Latency 0.3 to 0.9 seconds.
Never the sole decision-maker for consequences about people. Hiring, credit, medical and legal outcomes stay with a human. Jev can sort and flag. A person decides.
Sources. Model scores, cost per task and speeds: Artificial Analysis, Intelligence Index v4.3.x, including the GPT-6.1 Sol medium, high and xhigh pages, checked 29 September 2026. Astra and Fable scores from the Artificial Analysis v4.3 announcement. Jev figures are my own production measurements, September 2026, rounded. The review-bill example is illustrative. Read the full article on thorstenmeyerai.com.

Why the Review Seat Matters

Meyer’s central decision is to use a model from another family to review work produced by his main builder. He says GPT-6.1 Sol’s estimated cost of $0.32 to $0.39 per task makes routine review practical for him. That is his operating choice, not evidence that every Sol review will catch errors or that the same economics apply to other users.

The split also shows why a benchmark score alone may not settle model selection. The index’s general scores sit relatively close for several listed models, but their estimated task costs and response characteristics differ. Meyer says teams should shadow-test models on their own work before switching. He also cautions that more effort cannot supply missing requirements, and that a second model can share a flawed specification with the first.

His review rules distinguish evidence from approval: a passing test does not by itself mean work should ship. When a review finds a failure, Meyer says he sends the failing case and evidence back for correction rather than simply asking the builder to try harder.

How the Model Roles Took Shape

The stack follows releases and index entries listed across September. Meyer says Opus 5.5 was released on Sept. 22, Luna on Sept. 22, Sonnet 5.5 on Sept. 28 and GPT-6.1 Sol on Sept. 29. Fable 5.1 is listed with a Sept. 1 release, while Astra is listed with a Sept. 3 release.

Sol’s launch price, according to Meyer, is $2 per million input tokens and $10 per million output tokens, the same as the prior GPT-6 Sol. He reports three available effort settings in the index: medium, high and xhigh. At medium, Sol scores 48 at an estimated $0.21 per task; at high, 50 at $0.32; and at xhigh, 51 at $0.39. The index lists output-token totals of 15 million, 25 million and 36 million for those settings.

Meyer reports that high and xhigh take 57 and 69 seconds, respectively, to produce a first token in the index. He says this makes them a poor fit for interactive use. He also notes that the index had not yet published low or max settings for GPT-6.1 Sol when he wrote his update.

““The practical reading: Sol is not the model I ask to build. It is the model I can afford to run on everything.””

— Thorsten Meyer

What the Index Cannot Settle

The index measures general capability, and Meyer says its results are not a verdict on an individual workload. His article does not report a controlled head-to-head test across his own projects, so the listed scores and estimated costs do not establish which model will be most effective for another team.

Meyer also cautions that a one-point score difference may fall within measurement noise. The index had not published GPT-6.1 Sol’s low or max results at the time of his update. The figures do not settle how model performance may change as new measurements appear, or whether the reported task costs match usage in a particular workflow.

One cost discussion in the source text is incomplete: it begins an illustrative example about model prices and human review time but ends mid-sentence. No conclusion from that example can be reported from the supplied material.

Test Before Changing Defaults

Meyer’s next step for teams considering a similar setup is to shadow-test models against their own tasks before changing defaults. The supplied update does not announce a later test date or a planned change to his chosen roles. Its immediate recommendation is to compare model quality and cost on the work that needs to be done, then use the results to set defaults.

Further comparisons may be possible as the index adds settings that were not yet listed for GPT-6.1 Sol. Until then, Meyer’s reported setup is Opus 5.5 at high or xhigh for building, Sol at high or xhigh for details and review, and other models for selected tasks. Whether he changes that arrangement will depend on his tests and later index data.

Key Questions

Which models does Meyer use for building and review?

Meyer says he uses Opus 5.5 as his main builder and GPT-6.1 Sol for detailed investigation and review.

What does GPT-6.1 Sol cost in the index comparison?

The index lists Sol at an estimated $0.32 per task at high and $0.39 at xhigh. These are index estimates, not guaranteed costs for an individual workload.

Does the comparison prove Sol is better value for every team?

No. Meyer says the index measures general capability and recommends shadow-testing models on a team’s own tasks before switching.

Why does Meyer avoid Opus 5.5 at max effort for routine work?

In the index figures he cites, max scores 58 at an estimated $5.98 per task, compared with high at 54 for $1.82. Meyer uses high for development and xhigh for harder work, reserving max as rarely worthwhile.

Source: ThorstenMeyerAI.com

FALL

Fall Picks

As an affiliate, we earn on qualifying purchases.

You May Also Like

Kimi K3: The Gap Closed Six Months Early — And China Stopped Competing On Price

Moonshot’s Kimi K3, with 2.8 trillion parameters, is now the most capable Chinese AI model, priced at Western mid-tier levels, signaling a shift in global AI competition.

The Co-Founder’s Black Hole — A Structural Read on Jack Clark’s Automated AI R&D Essay

Anthropic co-founder Jack Clark predicts over 60% chance of fully automated AI research by 2028, raising concerns about institutional capacity and future risks.

SteamdDB Joins Nexus Mods

SteamDB has integrated into Nexus Mods, expanding modding access for Steam users. Details are confirmed, but the full scope remains to be seen.

Understanding Talent Density

Explores how AI-driven talent density transforms organizational performance, productivity metrics, and business scale in 2026.