How I Organize AI Work With Opus, Sol, And Jev
AIThis post was created with the assistance of artificial intelligence (AI).

🔍 Read the full analysis: How I Organize AI Work With Opus, Sol, And Jev on ThorstenMeyerAI.com

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

Get the little things that make your day 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

On 29 September 2026, Thorsten Meyer published a cost-driven AI workflow: Claude Opus 5.5 at high or xhigh effort as the main builder, the newly released GPT-6.1 Sol as a low-cost reviewer, and Jev for high-volume routing decisions. With six frontier models within roughly 20 index points but 100x apart in cost per task, model selection shifts from capability to cost-efficiency.

AI analyst Thorsten Meyer published a working model stack on 29 September 2026 that routes daily AI work across Claude Opus 5.5, the newly released GPT-6.1 Sol, and Jev, a decision-only model, arguing that with six frontier models clustered within about 20 index points of each other but roughly 100x apart in cost per task, the practical question has shifted from “which model is smartest?” to “which model clears my quality bar at the lowest cost per task?”

The core of the workflow is a two-model pairing. Opus 5.5, released 22 September, is the main builder, run at high effort for features, APIs, and multi-file work ($1.82 per task, 54 points on the Artificial Analysis Intelligence Index v4.3.x) and at xhigh for architecture, migrations, and trust boundaries ($3.46 per task, 56 points). GPT-6.1 Sol, released the day of publication, serves as the second pair of eyes: at high or xhigh effort it costs $0.32 to $0.39 per task for scores of 50 to 51, making routine review passes affordable on every meaningful change.

Meyer’s comparison table, built on Artificial Analysis Intelligence Index v4.3.x data, shows the spread: Opus 5.5 tops the field at 58 points ($5.98 per task at max), while GPT-6 Luna sits at 37 points but costs $0.07 per task — 1,429 tasks per $100. Between them, Claude Sonnet 5.5 (56 points, $7.60 at max), Claude Fable 5.1 (53, $7.63), GPT-6 Astra (53, $3.26), and Sol fill specific niches across the frontier model lineup. Meyer notes that Sonnet 5.5 at max effort costs more per task than Opus at max while scoring 2 points lower, and that Opus now outscores its more expensive sibling Fable by 5 points at lower cost.

The effort setting emerges as the biggest cost lever. On Opus 5.5, moving from xhigh to max adds 2 index points for 73% more cost per task; from medium to max, cost rises 4.46x for 7 points. Sol has real catches, per Meyer: high and xhigh settings take 57 to 69 seconds to first token, ruling out interactive use, and Opus still leads it by 5 points at xhigh.

At a glance
reportWhen: published 29 September 2026, coinciding…
The developmentThe release of GPT-6.1 Sol on 29 September 2026 prompted a published workflow showing how the model compresses the cost of AI review work to $0.32-$0.39 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 Cost-Per-Task Now Drives Model Choice

The report captures a structural change in how AI work gets done. When capability gaps between frontier models shrink to single index points while prices differ by orders of magnitude, the marginal value of “the best model” collapses for most tasks. Meyer’s example makes the point: Sol xhigh sits 1-2 points under Astra and Fable at $0.39 instead of $3.26 or $7.63 per task — meaning a review pass costs little enough to run routinely rather than selectively.

The cross-family review pattern is the second takeaway. A different model family reviewing Opus’s output is, in Meyer’s framing, a better check than Opus reviewing itself — but he adds the caveat that a second model reading the same flawed spec is not an independent review. The workflow also assigns Jev, a decision model that cannot write a sentence, to high-volume yes/no and routing judgements, extending the cost logic below the text-generation tier.

A Month of Rapid Frontier Releases

: “

The stack rests on an unusually dense release window. In September 2026 alone: Fable 5.1 (1 September), Astra (3 September), GPT-6 Luna and Opus 5.5 (22 September), Sonnet 5.5 (28 September), and GPT-6.1 Sol (29 September). Sol launched at the same $2/$10 per 1M tokens as its week-old predecessor; even its medium setting matches the earlier GPT-6 Sol’s score of 48 at one-fifth of that model’s $1.06 per task, per Artificial Analysis data cited by Meyer.

Meyer grounds his choices in four stated rules: effort is not capability; more effort cannot fill in missing requirements; passing tests are not approval to ship; and failing cases get handed to the builder with evidence, never just “try harder.”

“In four weeks, the AI frontier stopped being a leaderboard and became a price curve. Six models now sit within about 20 index points of each other, while their cost per task differs by roughly 100×.”

— Thorsten Meyer

Limits of the Benchmark and the Math

Meyer is explicit that his scores come from one source — the Artificial Analysis Intelligence Index v4.3.x — and that one index point is inside the noise. Artificial Analysis has not yet published low or max settings for Sol, so the full cost curve for that model is incomplete.

The cost-of-ownership math is also qualified by the author himself. His observation that halving model price saves only 12.5% of real cost, and that a single extra minute of human review can erase the saving, is described as illustrative, not measured. Whether the Opus-plus-Sol split generalizes beyond Meyer’s own development workload is untested; he recommends shadow-testing before any switch.

Watching Sol’s Missing Settings

The immediate open item is Artificial Analysis publishing low and max effort settings for GPT-6.1 Sol, which would complete its cost curve and show whether cheaper settings preserve usable quality. Meyer indicates he will keep Opus at high/xhigh as his default and reserve max settings for rare cases, while running Sol review passes on every meaningful change and using Astra or Fable as tie-breakers only when Sol and Opus disagree. Whether vendors respond to the price compression with their own cuts, and whether the September release cadence continues into October, remains to be seen.

Key Questions

What is the core workflow described?

Opus 5.5 at high or xhigh effort builds software and handles knowledge work; GPT-6.1 Sol at $0.32-$0.39 per task performs detail dives and independent review; Jev, a decision model, handles high-volume yes/no and routing calls.

Why not just use the highest-scoring model for everything?

According to Meyer, the top settings rarely justify their cost. Opus 5.5 max adds only 2 points over xhigh for 73% more cost per task, and Sonnet 5.5 at max costs more than Opus at max while scoring lower.

What are GPT-6.1 Sol’s main drawbacks?

High and xhigh settings take 57 to 69 seconds to produce a first token, making it unsuitable for interactive use, and Opus 5.5 still leads it by 5 index points at xhigh (56 vs. 51).

Are the benchmark scores a reliable guide for my own work?

Meyer says no — the Artificial Analysis index maps general capability, not any specific workload, and one index point is within measurement noise. He recommends shadow-testing models before switching.

Does a cheaper model actually reduce total costs?

Only partially. Meyer’s illustrative (not measured) example holds that halving model price saves about 12.5% of real cost, an amount a single extra minute of human review can erase.

Source: ThorstenMeyerAI.com

FALL

Fall Picks

As an affiliate, we earn on qualifying purchases.

You May Also Like

7 Best Wireless Smartwatches for Prime Day Deals in 2026

Discover the best wireless smartwatches on Prime Day 2026, including Apple, Garmin, and budget options, with details on features, prices, and suitability.

The Top Portable Power Stations Supporting AI In 2026

Discover the leading portable power stations in 2026 optimized for AI applications, balancing capacity, portability, and advanced features for diverse needs.

The Eye Over The City: How Wide-Area Motion Imagery Works — And Where It Goes Blind

An in-depth look at how Wide-Area Motion Imagery (WAMI) works, its applications, limitations, and future developments in surveillance technology.

The High-End PC And Workstation Tax

Memory costs spike in 2026, reversing long-standing PC building rules. DIY builders face higher prices; prebuilt options may be cheaper now.