Fetching from the wire…
Public story · 2026-09-12 · high
AWS benchmarks find a pricier model wins on cost once you count only the answers it gets right, especially across multi-turn agent runs.
Why now: AWS published the comparison in a Bedrock model-selection post covered as of September 12, 2026.
AWS ran gpt-5.6-luna, terra and sol against gpt-5.4-mini and nano on Bedrock and measured cost per correct answer instead of cost per token. Anyone picking a model by list price alone is the target here, because the results flip that logic. On AIME math problems, Luna cost $0.0021 for each passing answer. Mini, despite a lower price per token, cost $0.0139 per passing answer, per AWS's benchmark post.
The gap grows with conversation length. On DeepSearchQA, a multi-turn agent benchmark, Luna cost $0.05 per passing answer against Mini's $0.40, while also scoring higher (F1 0.50 versus 0.39).
AWS ties the widening gap to how multi-turn agents work. Every turn re-sends the full conversation history. Token spend then accumulates roughly quadratically as a task runs longer, so a model that looks cheap on a single-turn benchmark can rack up cost fast once it's chaining tool calls or asking follow-up questions.
GDPval, which scores real deliverables, told the same story. Luna passed 56% of tasks at $0.010 each. Mini passed 42% at $0.030 each: lower quality and higher cost per usable output, from the model with the lower list price.
AWS doesn't publish the turn count where the crossover happens, only that the curve bends upward with each additional turn. That's the number worth pulling out of your own agent logs before the next model swap, not the AIME gap. If your workflow chains tool calls or asks clarifying questions, benchmark cost per correct output on your actual trajectories before trusting the per-token sticker price.
Each link below shares sources, entities, or timing with this story.
The full family, Sol, Terra, and Luna, is generally available on Amazon Bedrock with IAM and VPC controls (LLM Boss, AWS). Sol targets coding, biology, and cybersecurity agentic work. Terra runs everyday tasks at about half GPT-5.5's cost, and Luna optimizes for speed. The thr...
AWS made the managed AgentCore harness generally available on June 18. You define model, tools, skills, and memory with CreateHarness, then run it with InvokeHarness. It ships multi-model support (Bedrock, OpenAI, Gemini, LiteLLM), mid-session context preservation, built-in br...
The walkthrough uses utility bills queried at scale as its worked example, and argues for preprocessing before ingestion rather than a better embedding model. That matches what I hit building Rayni: the retrieval was usually fine and the extraction was wrong, and no amount of...
Bedrock invocation logs to S3 carrying model ID, token counts and IAM Identity Center user identity; an Athena view computing per-user daily spend; a Lambda on a 15-minute EventBridge schedule rewriting Customer Managed Policies via iam:CreatePolicyVersion (AWS). Denials take...
Loom (github.com/awslabs/loom) is a reference implementation: "paved path" blueprints baking in least-privilege IAM, abstracted configuration, and strict deployment guardrails for agents built on Strands Agents running on Bedrock AgentCore Runtime. The repo ships the specs use...
The walkthrough covers implementing MCP tools, wiring authentication, and deploying with AWS CDK against Bedrock AgentCore and Mistral AI Studio. Steal the two-layer JWT pattern: agent identity and end-user identity as separate token layers. Most MCP server tutorials hand-wave...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.