Mercury 3 vs GPT-6 Astra: 28 Times the Output Price, Bought One Effort Level at a Time

Mercury 3 and GPT-6 Astra differ by 28 times on output price — $0.35 per million during Inception's launch window against $50.00 from O​penAI — and by roughly 18 times on throughput in the opposite direction. Those two numbers are easy to quote and nearly useless on their own, because Astra is not one model at one price. It is a reasoning ladder: five effort levels, an index score that climbs from 46 at the bottom to 53 at the top, and a bill that climbs with it. Mercury 3 has a ladder too, of sorts — four effort settings and a default at the bottom — but no independent score at any of them. So the real question in this matchup is not whether Astra is worth 28 times Mercury 3. It is how far up Astra's ladder you actually need to climb, and whether the work you are doing needs a ladder at all. The documented AI failures and agent incidents behind releases like this one are collected in the OrcaRouter AI Incident Archive where each entry carries its own sources, severity, confidence grade and disputed flag.

The number that decides this, and it is not the price

Artificial Analysis measures GPT-6 Astra at 53 on its Intelligence Index at the model's maximum effort setting, ranked seventh of the 216 models in the index, at about $3.26 of compute per index task. Run the same suite at the lowest effort setting and the score is 46. The five rungs, in order, are 46, 50, 51, 52 and 53.

Read that ladder twice. The first reading is that the top rung is only seven points above the bottom one, on a suite where seven points is a lot — the models below Astra and the models above it are separated by smaller margins than that. The second reading is that rung four, at 52, is within one point of the top and presumably cheaper. If your task does not need the last point, you are not choosing between Mercury 3 and a 53-point model; you are choosing between Mercury 3 and a 52-point one, and the price of getting there is a parameter rather than a different model.

Mercury 3 offers no such choice, because there is nothing to climb toward. There is no index score at instant, low, medium or high. Inception's own comparative claim — that Mercury 3 outperforms GPT-6 Luna and Claude Haiku 5.5 — is a claim about the fast tier, made without margins, and its one structured quality result is 50% completion on 50 live Mind2Web navigation tasks inside its own agent harness. That is a real result and a small sample, and it does not tell you where Mercury 3 would land on a 216-model index if it were entered tomorrow.

What $50 an output token actually contains

GPT-6 Astra takes text, images and files, holds a 1.05M-token context window and returns up to 128K tokens. Its standard rate card is $10.00 per million input and $50.00 per million output, with cached input at $1.00. Above 272,000 input tokens it reprices the entire request at $20.00 and $75.00, cached input at $2.00 — the boundary is not a marginal tier, it is a switch that doubles the whole bill. Batch and flex processing halve the rates; fast mode doubles them. Reasoning is always on and runs from low to max.

Two traps sit in that paragraph. The 272,000-token boundary means a 280,000-token request costs twice what a 270,000-token request costs, with no partial credit — so context trimming near the boundary is worth more engineering effort than most teams give it. And what O​penAI markets as "GPT-6 Astra Pro" is not a separate model or a separate SKU; it is the pro setting of the reasoning dial, which means it is reachable from the same endpoint at the same rates and is not something you need a new contract to use.

Mercury 3, for contrast, is $0.20 and $0.70 at list, halved for the launch period to $0.10 and $0.35, with cached input at $0.02 and $0.01. One context window of 1M tokens, one maximum output of 131,072, no tiers, no boundary, no batch multiplier. The rate card is four lines long. That simplicity is worth something on its own — a cost model you can hold in your head does not drift.

The cost model nobody runs: tokens per task, not price per token

Astra's per-token price is the least interesting number about Astra's cost. Artificial Analysis reports that a full Intelligence Index run on Astra consumes about 60 million output tokens in total, and that one index task costs about $3.26. Divide one by the other and you get the ratio that matters: Astra spends a great deal on thinking before it spends anything on answering.

Mercury 3 is priced fourteen times below Astra at launch and 71 times below at Mercury's list against Astra's standard rate. But the comparison of price per token assumes the two models emit comparable token counts for the same task, and everything known about diffusion decoding argues they do not. A diffusion model resolves a block of positions over a fixed number of denoising passes; its output length is a property of the answer, not of an internal monologue that unfurls before the answer. Astra's output length is dominated by the monologue.

That cuts both ways, and both cuts are worth stating. On a reasoning-heavy task where Astra spends 100,000 reasoning tokens to get the right answer, Mercury 3's advantage is far larger than 14x, because Mercury 3 is not paying for the monologue at all — though whether it reaches the same answer without one is precisely the open question. On a short-answer task where Astra answers in three hundred tokens at low effort, the monologue never happens, and the comparison collapses to the rate card: 14x at launch, 71x at Mercury's list.

Put a real workload on it. Ten million input tokens and two million output tokens per day, a support-and-summarisation mix. On Astra at standard rates that is $100 of input and $100 of output — $200 a day, about $6,000 a month. On Mercury 3 at list it is $2 and $1.40 — $3.40 a day, about $102 a month. At launch rates it is half that again. The same traffic, 59 times the spend, and the question of whether Astra's answers are 59 times better is one nobody can currently answer with a number.

Where a router actually helps in this matchup

GPT-6 Astra is on the OrcaRouter catalogue. It is reachable from the same O​penAI-compatible endpoint as the rest of the models we route, at OpenAI's list rates with nothing added on our side — $10.00 input, $50.00 output, $1.00 cached, and the long-context tier at $20.00 and $75.00 above the 272,000-token boundary — with both chat completions and the Responses API available, depending on which shape your code already speaks.

Mercury 3 is not on the catalogue. Our model API returns nothing for any Inception model, so calling it means going to Inception's own platform, where new accounts currently get 100 million free tokens, or to one of the inference platforms Inception lists. We would rather say that than let a comparison piece imply a route we do not have.

What the routing layer buys you here is a second dial of a different kind from Astra's effort levels. The five effort levels are Astra's own dial, and climbing it costs money at every rung. Routing lets you choose how rarely you pay Astra at all: send the bulk of traffic to a model in the fast tier we do route — GPT-6 Luna at $0.10 and $0.50, or Claude Haiku 5.5 at $1.00 and $5.00 — and reserve Astra at high or max for the fraction of requests that are actually hard, with automatic failover if a provider degrades and the routing DSL to express the split as a rule rather than a code branch. The saving is not in Astra's rate; it is in how often you avoid it.

That is also, incidentally, the honest way to evaluate Mercury 3. Put it on the fast-tier path alongside Luna and Haiku 5.5, where Inception's own comparison places it, and see whether it wins on your tasks. Comparing it to Astra directly is comparing a model with no index score to a model on the seventh rung of a 216-model index, and the result will tell you more about the mismatch than about either model.

One detail a routing layer should not round off, and we do not: Astra's rate card has a boundary at 272,000 input tokens that reprices the entire request, and a batch mode that halves it. Those are not marginal adjustments, and a pass-through at list price is only worth having if it passes the awkward parts through too.

The comparison that would settle it

What would settle Mercury 3 vs GPT-6 Astra is not a launch post and not this article. It is one number: Mercury 3's position on the same index Astra sits on, at a stated effort setting, on the same suite, measured by somebody who is not Inception. Until that exists, every comparison between these two is a comparison between a measured model and an unmeasured one, and the measured one should get the benefit of the doubt by default — not out of deference to O​penAI, but because a score you can check is worth more than a throughput figure you cannot.

The useful posture in the meantime is the one Astra's own ladder suggests. Most work does not need the top rung of anything. Point the bulk of your traffic at the cheapest model that clears your quality bar, keep the expensive rung for the requests that fail it, and treat Mercury 3 as a candidate for the cheap path rather than as an alternative to the expensive one. If it turns out to clear the bar at a fourteenth of the price, you will find that out on your own tasks, which is the only suite whose results you can actually act on.