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

🔍 Read the full analysis: The AI Tools I Use To Build, Dig, And Decide This September on ThorstenMeyerAI.com

Buying for a business?Offer from Amazon

Get business pricing on office and shipping supplies

  • 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 says he uses Claude Opus 5.5 for development and GPT-6.1 Sol for detailed review after Sol launched on Sept. 29. His comparison of six models, based on Artificial Analysis Intelligence Index v4.3.x, finds scores clustered within about 20 points while reported cost per task varies widely. The figures describe benchmark results and his workflow; they do not establish which model will perform best on other users’ tasks.

Thorsten Meyer says he now uses Claude Opus 5.5 as his main model for building and GPT-6.1 Sol for detailed work and review, following Sol’s release on Sept. 29. His comparison of six models argues that reported task costs can differ sharply even when benchmark scores are relatively close, shifting his selection criteria toward the least expensive model that meets a task’s quality bar.

Meyer’s figures are drawn primarily from the Artificial Analysis Intelligence Index v4.3.x, which he describes as a general capability measure rather than a verdict on a particular workload. In his table, Opus 5.5 scores 58 at its top setting and costs $5.98 per task; GPT-6.1 Sol scores 51 at xhigh and costs $0.39. The other entries are Sonnet 5.5 at 56 and $7.60, Fable 5.1 at 53 and $7.63, GPT-6 Astra at 53 and $3.26, and GPT-6 Luna at 37 and $0.07.

Those cost figures are reported per task in the source. Meyer also lists token prices: Opus 5.5 at $4 per million input tokens and $20 per million output tokens, GPT-6.1 Sol at $2 and $10, and Luna at $0.10 and $0.50. He says Opus at high effort scores 54 for $1.82 per task, while xhigh scores 56 for $3.46. At max, it scores 58 for $5.98. These figures illustrate how effort settings change his reported costs as well as the scores.

For Sol, the source lists three settings: medium at 48 and $0.21 per task, high at 50 and $0.32, and xhigh at 51 and $0.39. Meyer says high and xhigh took 57 and 69 seconds, respectively, to produce a first token in the index results. He assigns Sol to reviewing specific files or code changes and examining details, while using Opus for features, APIs, multi-file work, and refactoring. He says Sonnet, Luna, Astra, and Fable serve as alternatives for narrower tasks or second opinions.

At a glance
reportWhen: Published Sept. 29, 2026; GPT-6.1 Sol w…
The developmentThorsten Meyer published a September 2026 account of how he assigns six AI models to development, review, and routine decisions using benchmark scores and reported cost per task.

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 Task Costs Shape Model Choice

Meyer’s account reflects a practical change in how he evaluates AI tools: a top benchmark score is only one factor if a lower-cost model can meet the needs of a particular task. The reported gap between Opus 5.5 and Sol is relevant to teams that run repeated review passes, where per-task expenses can accumulate. However, the source does not provide a standardized measure of the models’ performance on Meyer’s own development work, so the cost comparisons alone cannot establish which setup saves money overall.

His workflow also gives a separate model a review role. Meyer argues that a model from a different family can offer a useful second perspective on Opus-generated work. He says he uses Sol routinely because its reported cost is low enough for frequent checks. That is his operating choice, not evidence that a second model will catch every error: he also warns that reviewers can share the same flawed requirements, and that passing tests should not be treated as permission to ship.

The September Model Lineup

The source describes a series of releases across September 2026: Fable 5.1 on Sept. 1, GPT-6 Astra on Sept. 3, Opus 5.5 on Sept. 22, Luna on Sept. 22, Sonnet 5.5 on Sept. 28, and GPT-6.1 Sol on Sept. 29. Meyer says six models fall within roughly 20 points on the index while their reported task costs vary by about 100 times. The index comparisons are snapshots, and the source cautions that scores do not substitute for testing against a user’s own workload.

Meyer further reports that Opus 5.5’s xhigh setting adds two index points over high at a higher listed task cost. He says Sonnet 5.5’s max setting costs $7.60 per task for a score of 56, while its high setting costs $1.08 for a score of 47. His preferred settings therefore vary by job: high or xhigh for development with Opus, and medium for documents and routine work. These are recommendations based on his reading of the index and his stated workflow.

““Which model clears my quality bar at the lowest cost per task?””

— Thorsten Meyer

What the Benchmarks Cannot Show

The source does not provide the underlying task definitions, measurement methods, or confidence intervals for the reported per-task costs, so readers cannot assess how closely those figures match their own use. Meyer notes that a one-point index difference is within the noise and says low and max results for GPT-6.1 Sol had not been published at the time of writing. The account also does not establish whether Sol’s reported first-token delays would apply across different prompts or service conditions.

Most importantly, the index is a general benchmark. The source gives no independent comparison of how often each model produces correct code, catches defects, or reduces human review time on a shared set of real projects. The article’s workflow and cost judgments are Meyer’s reported choices; performance on other workloads remains to be tested.

Test Models Against Your Work

Meyer recommends shadow-testing a candidate model before switching a workflow. That means checking it against the work it would actually handle and comparing the results with the existing process. For his own setup, the next step is continued use of Opus for building and Sol for review, with Astra or Fable as alternatives when those models prove more useful in a specific comparison. No later benchmark release or change to his stack is specified in the source.

Key Questions

Which models does Thorsten Meyer use for building and review?

Meyer says Opus 5.5 is his main model for building, while GPT-6.1 Sol handles detailed investigation and review. He uses other models for specific tasks or as alternatives.

Why does Meyer use GPT-6.1 Sol for reviews?

He reports that Sol costs $0.32 per task at high and $0.39 at xhigh in the cited index results. He says that makes a separate review pass affordable to run routinely. The source does not show that this cost or performance will apply to every user’s workload.

Does the benchmark identify the best model for every task?

No. Meyer says the Artificial Analysis Intelligence Index measures general capability and advises readers to test models on their own work before changing systems.

What is still missing from the GPT-6.1 Sol results?

At the time of Meyer’s Sept. 29 account, he said the index had not published Sol’s low or max settings. He also notes that the reported high and xhigh settings had long first-token times in the index, while real-world timing may depend on the task and service conditions.

Source: ThorstenMeyerAI.com

This content is for general information only and is not financial, tax or legal advice. Consult a qualified professional for decisions about your money.
FALL

Fall Picks

As an affiliate, we earn on qualifying purchases.

You May Also Like

The Delegation Ladder: The Four Agentic Loops, and What Each One Lets You Stop Doing

An analysis of the four agentic loops in AI development, detailing what each enables developers to delegate and how it impacts AI process automation.

The Menu: What Ten Answers Reveal

A detailed analysis of how ten jurisdictions respond to automation, AI, and income risks, revealing varied policy models and their implications.

The Workplace Systems Audit Every Growing Office Needs

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

The Role Of AI In Shaping 2026’S World

Exploring how artificial intelligence is transforming global society, economy, and technology in 2026, with confirmed developments and ongoing uncertainties.