Benchmark

Task Cost Benchmark

What 10 real product features actually cost across OpenAI, Anthropic, Gemini, and Kimi. Not price per token, real task cost.

Most benchmarks compare raw price per million tokens, or they score models on academic tests. Neither answers the question a founder actually has, which is what one feature costs to run. This benchmark measures that. Ten realistic tasks, each written out in full, run against every provider's live API, priced with the same table Weckr uses to recompute cost on every logged call.

The gap between the two questions is wider than it looks. A flat per token rate says nothing about how many tokens a model decides to spend, and models differ enormously on that. Multi turn and agentic features resend their accumulated context on every step, so the same sticker price produces very different bills. Those are the tasks where cost compounds, and they are the tasks most likely to be in the product you are shipping.

The research gap this fills

Two recent papers make the same point from the academic side. CostBench (ACL 2026) argues that current agent evaluations emphasise task completion while overlooking resource efficiency and adaptability, and finds that leading models routinely fail to choose cost optimal plans, with even GPT-5 scoring under 75 percent exact match on the hardest tasks. TerminalWorld (arXiv 2026) documents an efficiency paradox in real terminal work, where success correlates negatively with resource use, reporting r = -0.62 against token usage, because failed attempts burn disproportionately more tokens than successful ones.

Both describe the same blind spot: we measure what a model can do and rarely what it costs to make it do that. This benchmark is the practical, founder facing translation of that concern. It is not a capability ranking and it is not a price list. It asks one question, which is what a feature costs when you actually ship it.

Results

Last run July 23, 2026. Suite version 1.0.0. 40 of 40 task runs completed.

Cost to run all 10 features 1,000 times each

Gemini costs 10.6 times more than OpenAI for identical work. Total USD across the whole suite.

Weckruseweckr.com

Cost per task, per 1,000 runs

Log scale: every gridline to the right is 10 times more expensive. Dots rather than bars, because on a log axis a bar length would understate the gap it is meant to show.

Weckruseweckr.com
OpenAIAnthropicGeminiKimi

Every figure

gpt-5.4-miniclaude-haiku-4-5gemini-3.6-flashkimi-k2.6
Customer support replyGenerate a reply to a support ticket given short account context$0.935$1.19$10.22$5.58
Ticket classificationClassify a support message into one of five categories$0.083$0.108$1.61$0.478
Receipt extractionPull structured fields from messy realistic receipt text$0.395$0.590$12.96$23.55
Product descriptionWrite a short product description from five bullet points$0.654$0.887$23.36$7.52
RAG style question answeringAnswer a question using only a provided context chunk$0.475$0.766$4.92$1.37
Tone rewriteRewrite a formal paragraph into a casual one$0.605$0.710$12.83$2.74
Code test generationWrite three test cases for a given function signature$1.04$2.60$16.77$29.09
Multi turn support conversation3 turnsThree back and forth exchanges where context accumulates each turn$2.56$3.54$16.30$10.79
Long document summarizationSummarize a 3047 word internal review document into a short summary$4.36$6.07$23.28$8.37
Agentic multi step task4 turnsPlan first, then execute the plan across three steps with full context carried forward$2.91$5.10$26.09$25.97
All 10 tasksOne run of the full suite$14.02$21.56$148.35$115.46

Amber marks the cheapest provider for that task. Thinking tokens are counted inside output tokens and billed at the output rate, which is why a one word answer is not free. Sort by clicking a provider.

What the numbers show

Running the full suite once cost $0.0140 on OpenAI and $0.1484 on Gemini, a spread of 10.6 times for the same ten tasks. The published rates for these 4 models span only 2.0 times on input and 1.9 times on output, so almost none of that spread comes from the sticker price. It comes from how many tokens each model chose to spend.

The clearest example is the classification task. The correct answer is one word, and every model got it right. Gemini spent 198 output tokens producing it, of which 197 were thinking tokens you never see in the response. Thinking tokens are billed at the output rate, so a one word answer is not close to free, and nothing in a per million token price list tells you that.

Compounding is the other effect. The agentic task plans and then executes across four calls, each one resending everything before it, and the multi turn support conversation does the same across three. On Kimi the agentic task costs 4.6 times the single turn support reply on the identical model at the identical rate. A cost model built on price per token will miss that entirely, because the rate never changed.

OpenAI was the cheapest option on 10 of the 10 tasks in this run. The useful reading is not the leaderboard, which a single pricing update can rearrange. It is the size of the gap. Ten identical pieces of work cost 10.6 times more at one end than the other, on models whose published rates differ by far less. That gap is produced by model behaviour rather than by price, and it stays invisible until you measure the task itself.

Methodology

The 10 tasks

  1. 1Customer support reply. Generate a reply to a support ticket given short account context
  2. 2Ticket classification. Classify a support message into one of five categories
  3. 3Receipt extraction. Pull structured fields from messy realistic receipt text
  4. 4Product description. Write a short product description from five bullet points
  5. 5RAG style question answering. Answer a question using only a provided context chunk
  6. 6Tone rewrite. Rewrite a formal paragraph into a casual one
  7. 7Code test generation. Write three test cases for a given function signature
  8. 8Multi turn support conversation. Three back and forth exchanges where context accumulates each turn 3 calls, context accumulates.
  9. 9Long document summarization. Summarize a 3047 word internal review document into a short summary
  10. 10Agentic multi step task. Plan first, then execute the plan across three steps with full context carried forward 4 calls, context accumulates.

The exact models

ProviderModelPer 1M in / outStatus
OpenAIgpt-5.4-mini$0.75 / $4.5ran
Anthropicclaude-haiku-4-5$1 / $5ran
Geminigemini-3.6-flash$1.5 / $7.5ran
Kimikimi-k2.6$0.95 / $4ran

One tier was chosen per provider: the fast, cost optimized tier, which is the tier most SaaS features actually run on in production. These are not the flagship reasoning models. Comparing flagships would measure something real but different, and it is not what a high volume product feature is usually built on. Kimi K2.6 is the exception in that it serves as Moonshot's primary tier rather than a cheaper sibling of a larger model, because Moonshot does not currently offer a separate economy model in the way the other three do. Model identifiers were verified against each provider's live model list on the run date.

How it was run

  • Settings. Provider defaults. No reasoning effort, thinking budget, temperature, or sampling parameter is set. Only the per task max output token cap from tasks.json is sent. Providers were not tuned to match each other, because they do not expose equivalent settings and choosing which settings count as equivalent would quietly decide the outcome.
  • Tokens. Input and output token counts are taken from each provider's own API response, never estimated locally. Thinking and reasoning tokens are included in output tokens because that is how they are billed.
  • Pricing. Cost is computed from weckr-api/lib/caps.ts PRICING, the same table the /log route uses to recompute cost server side. It is the same code path that prices a real customer call, so the benchmark cannot flatter Weckr by pricing differently from the product.
  • Multi turn tasks. Each turn resends the full prior conversation, which is how a real feature behaves. Cost for those tasks is the sum of every call.
  • Missing providers. A provider with no usable API key is skipped and reported. It is never estimated and never written into the results as though it ran.

Raw data and full test suite

The complete prompt text for all 10 tasks, the 3,047 word source document, the runner, and the raw results including every response are published in the public SDK repository. A cost tracking company publishing a cost benchmark should be auditable, so all of it is open. View the benchmark on GitHub.

This is version 1.0.0. The task set is deliberately small and will expand. Results are a single run per task, not an average of several, so treat small differences between providers as noise and large ones as signal. Model pricing and default behaviour both change often, so the benchmark will be rerun periodically and every run is kept with its date.

Your real users are not synthetic tasks

These 10 tasks approximate a product. Your product is the real thing, with real users, some of whom cost you far more than others and none of whom show up on a pricing page. Weckr gives you this same cost view for your own application, broken down per user and per feature, so you can see which customers are quietly unprofitable before the bill arrives.

Keep reading