AIThis post was created with the assistance of artificial intelligence (AI).

🔍 Read the full analysis: My September 2026 AI Stack, From First Build To Final Decision on ThorstenMeyerAI.com

Buying for a business?Offer from Amazon

Get business pricing on monitors, keyboards and dev gear

  • Business-only prices and quantity discounts
  • Tax-exempt purchasing
  • Multiple users, one account, clear invoices
As an affiliate, we earn on qualifying purchases.

TL;DR

Thorsten Meyer’s September 29 AI stack assigns Claude Opus 5.5 to building and GPT-6.1 Sol to detailed review, with other models reserved for specific tasks. The source compares Artificial Analysis Intelligence Index v4.3.x scores and estimated task costs; those figures may not predict results on other workloads.

Thorsten Meyer’s September 29 comparison recommends Claude Opus 5.5 for software building and GPT-6.1 Sol for detail work and review, arguing that the cost of a task can matter more than small differences in benchmark scores. The report draws on the Artificial Analysis Intelligence Index v4.3.x and its task-cost estimates; those measurements are not a verdict on every team’s workload.

Meyer says six models fall within about 20 index points of one another, while the reported cost per task spans roughly 100 times. In his table, Opus 5.5 scores 58 at its top setting and costs $5.98 per task. GPT-6.1 Sol at xhigh scores 51 and costs $0.39. The report lists GPT-6 Luna at $0.07 per task, with a score of 37, and positions it for classification, extraction and routing.

The recommended division of work follows those comparisons. Meyer uses Opus 5.5 at high for features, APIs and refactors, and xhigh for more demanding architecture or migration work. He assigns Sol at high or xhigh to file-specific investigation and review, while Sonnet 5.5, Astra, Fable and Luna are alternatives for narrower tasks. He says Astra or Fable may be useful as a second opinion when Sol and Opus disagree.

The report also compares effort settings, which change both scores and costs. Opus at high scores 54 for a reported $1.82 per task; xhigh scores 56 at $3.46; max reaches 58 at $5.98. Meyer says Sonnet 5.5 at max costs $7.60 per task for a score of 56, and reports that it generated about 193,000 output tokens per task on the index. These are index-specific measurements, not a guarantee of equivalent costs in an individual deployment.

At a glance
reportWhen: Published September 29, 2026; GPT-6.1 S…
The developmentThorsten Meyer published a September 29, 2026, model comparison and workflow recommendation, including GPT-6.1 Sol, released the same day, as a low-cost review model.

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.

How the Cost Curve Changes Model Choice

The comparison shifts the practical question from picking the highest-scoring model to deciding which model meets a team’s quality threshold at a manageable cost. If the reported costs transfer to a particular workflow, using a lower-cost model for routine review could make additional checks affordable. Meyer argues that a different model family reviewing code can provide a useful second perspective, while acknowledging that review quality depends on the requirements and evidence supplied.

That distinction matters for buyers because the most capable model in a benchmark may not be the most economical choice for every task. The source also cautions that model-token prices alone do not determine the cost of completed work: extra waiting or human review can erase savings. Its example on that point is described as illustrative, rather than measured evidence.

Benchmark Scores Behind the Stack

The report uses the Artificial Analysis Intelligence Index v4.3.x, a general capability index, alongside task-cost and output-token figures. It lists Opus 5.5 as released September 22, Sonnet 5.5 on September 28, and GPT-6.1 Sol on September 29. Fable 5.1 and Astra are listed as September releases; Luna is dated September 22.

Meyer’s table puts Astra at 53 points at its top setting and $3.26 per task, and Fable 5.1 at 53 points and $7.63. Sol xhigh is listed at 51 points and $0.39. The report says Sol’s high setting took 57 seconds to produce its first token and xhigh took 69 seconds, making those settings slower to respond. Meyer advises readers to shadow-test models before switching a workflow.

“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, in the September 29 report

Limits of the Index and Cost Estimates

The report does not establish how the six models perform on a reader’s own codebase, documents or evaluation criteria. Meyer says the index measures general capability and recommends shadow testing before a switch. The source does not provide details here on the index’s full methodology, sample variation or how its per-task cost estimates map to each provider’s billing for a specific user.

It also says one index point is within the noise, and that Artificial Analysis had not yet published low or max effort results for GPT-6.1 Sol at the time of writing. The reported high and xhigh first-token delays may also limit Sol’s fit for interactive work. The figures therefore support Meyer’s stated workflow, but do not settle which model is best for other teams.

Test Models Against Your Workload

Meyer’s immediate recommendation is to shadow-test candidate models on the work a team actually performs before changing its defaults. Teams following his approach would compare output quality, latency and total review effort, not benchmark score or token price alone. The source does not give a date for further benchmark updates or specify a future release milestone.

For GPT-6.1 Sol, the next relevant evidence would include additional effort-level results and tests on real development and review tasks. Until then, Meyer’s stack remains a dated recommendation based on the index and cost figures available on September 29, 2026.

Key Questions

What is the main recommendation in Meyer’s September 2026 stack?

He uses Claude Opus 5.5 for building and GPT-6.1 Sol for detailed investigation and review, with other models assigned to narrower tasks.

Why does Meyer use GPT-6.1 Sol for review?

The report lists Sol at high or xhigh at $0.32 to $0.39 per task, far below the listed costs for several higher-scoring alternatives. Meyer says that makes routine review more affordable; the figures are index estimates and may not match every deployment.

Does the index show which model is best for every team?

No. Meyer describes the Artificial Analysis Intelligence Index as a map of general capability, not a verdict on a particular workload, and recommends testing models against a team’s own tasks.

What limits does the report identify for GPT-6.1 Sol?

At high and xhigh, the reported time to first token is 57 to 69 seconds. Sol xhigh also scores below Opus 5.5 at xhigh in the listed comparison, and the source says low and max results were not yet published.

Source: ThorstenMeyerAI.com

FALL

Fall Picks

As an affiliate, we earn on qualifying purchases.

You May Also Like

Best Code Review Tools For Developers Compared

Compare CodeRabbit and Graphite on review depth, workflow, integrations, pricing, and team fit to choose the right code review tool.

Why Has Shopify Dropped React Native?

Shopify has shifted back to native iOS and Android development, citing AI coding gains and React Native’s abstractions. What’s confirmed and what’s not.

Show HN: Reladraw – A Diagram Language Where You Decide Where To Place Things

Reladraw is a text-based diagram tool that combines relative placement instructions with a command-line renderer and a web component.