Cost mode:

Category: Infrastructure & Utility · Rail: absolute · Typical I/O: 409→552 tokens

Models

Frontier on this task: Claude Sonnet 5 at 9.51 / 10. Quality bar at 90%: 8.56.

point-estimate floor (CI low) · upper CI (less certain) · Bars sorted by blended cost; best-value model first. Greyed rows are MEDIUM+ models whose point estimate clears the bar but whose CI low does not.

ModelQuality scoreCI lowCost / 1k runsvs best value
Claude Sonnet 59.51 / 109.40$1.71best value
Gemini 3.5 Flash9.10 / 108.90$5.933.5x more expensive
GPT-5.4 Mini6.68 / 106.30$0.4176% cheaper
GPT-5.57.61 / 107.27$4.922.9x more expensive
Claude Haiku 4.55.61 / 105.11$1.0340% cheaper
Gemini 3.1 Flash Lite7.58 / 107.35$0.2784% cheaper
DeepSeek V4 Pro8.18 / 107.88$0.4574% cheaper
Qwen 3.6 Plus8.50 / 108.27$1.4118% cheaper
Qwen 3.5 Flash8.07 / 107.83$0.7457% cheaper
GPT-5.4 Nano7.15 / 106.80$0.2287% cheaper
Gemini 3.1 Pro Preview7.45 / 107.19$1.751x more expensive
NVIDIA Nemotron-3 Nano 30B-A3B6.55 / 106.17$0.1392% cheaper
NVIDIA Nemotron-3 Ultra 550B8.55 / 108.25$2.231.3x more expensive
GPT-5.6 Sol6.09 / 105.81$2.961.7x more expensive
NVIDIA Nemotron-3 Super 120B7.35 / 106.85$0.3480% cheaper
Qwen 3.7 Plus7.18 / 107.01$4.912.9x more expensive
GPT-5.6 Terra6.40 / 106.16$1.1135% cheaper
Tencent Hy36.70 / 106.47$0.5269% cheaper
GPT-5.6 Luna6.34 / 106.09$0.6065% cheaper
Meta Muse Spark 1.15.80 / 105.54$9.625.6x more expensive
Qwen 3.6 Flash6.96 / 106.82$5.463.2x more expensive
Grok 4.56.11 / 105.92$10.726.3x more expensive

Cost breakdown

ModelQualityConfidenceCost / 1k runsOverpayMode
Claude Sonnet 5 best Anthropic9.51 / 10 CI [9.40, 9.61]RANKED$1.71best valuebatch
Gemini 3.5 Flash Gemini9.10 / 10 CI [8.90, 9.31]HIGH$5.933.5xbatch

Overpay shows how much more you pay than the best-value model that clears the quality bar (marked ★) — the best-value good-enough option. "16x" means you overpay 16× — 16× that reference for no quality benefit above the bar. Typical call shape for this task: 409 input tokens → 552 output tokens, EMA-tracked from production traffic. Cost is the observed, all-in $ per 1,000 task runs: each model's own measured usage on this task — output verbosity, thinking/reasoning tokens, cache reads and writes, and the spend on its billed failures — priced at current list rates and adjusted by the billing overhead we actually reconcile against provider invoices. Models that answer tersely cost what they actually cost; models that think at length pay for it. Not comparable to providers' advertised $/1M list rates — this is what running the task costs, not a per-token price.

Prompt templates

This is a pooled capability — 2 prompt families share it. The pair shown first is the most frequently used in production.

METADATA_PARAGRAPH_IMPROVEMENT_SYSTEM_PROMPT + METADATA_PARAGRAPH_IMPROVEMENT_USER_PROMPT (1647 calls in window)

System prompt

You are an expert editor specializing in creating polished, professional metadata paragraphs for research reports.

Your task is to take a draft metadata paragraph that describes the research period and sources, and improve its wording to make it:
- More professional and polished
- Clear and concise
- Reader-friendly
- Accurate to the data provided

IMPORTANT GUIDELINES:
1. Preserve all factual information (dates, numbers, source types)
2. Do NOT add information that wasn't in the original
3. Do NOT change the meaning or facts
4. Keep the paragraph approximately the same length
5. Maintain a professional, informative tone
6. Start with a clear statement about the research period
7. Include source count and types naturally in the flow

The improved paragraph should be suitable for inclusion at the beginning of a professional research report or analysis document.

User prompt

Please improve the wording of this metadata paragraph while preserving all factual information:

{draft_paragraph}

Key facts to preserve:
- Date range: {date_from} to {date_to}
- Number of sources: {source_count}
- Content types: {content_type_summary}

Return the improved paragraph that maintains these facts while improving clarity and professionalism.
JSON_REPAIR_SYSTEM + JSON_REPAIR_USER (5 calls in window)

System prompt

You are a JSON repair tool. The user gives you malformed or partial model output and a JSON Schema. Return ONLY a single valid JSON object that satisfies the schema, salvaging as much real content from the input as possible. Do not invent data for fields the input doesn't support — use the schema's allowed empty/null values. Output the JSON object only: no prose, no markdown, no code fences.

User prompt

JSON Schema:
{schema_json}

Malformed output to repair:
{raw_text}

Return only the corrected JSON object.