The most expensive part of a reasoning model's bill is often not the answer but the thinking. Fireworks gives a number in its official blog: reasoning models like Kimi K3 can spend more than 90% of their generated tokens on internal reasoning before writing anything a user sees. That is merely expensive on a single request, but it compounds in multi-turn agentic workloads — every turn replays prior reasoning back to the model, so context cost grows roughly quadratically with turn count. Early-turn thinking traces get re-read and re-billed on every subsequent call.
Ember-1: teach the model to think less, don't dial effort down
The cheap fix already existed: turn K3's reasoning effort down to low. Fireworks tried it; the low setting gave up too much quality. Ember-1 takes another path — leave the effort switch alone and retrain the model itself. Fireworks Research ran more than 50 training experiments and over 200 evaluations, training K3 across mathematics, coding, instruction following, conversation, search, tool use, and software engineering, with one goal: remove reasoning that does not change the answer while keeping self-correction that does. The official claim: across seven public benchmarks and two customers' production traffic, K3's reasoning could be shortened by 35–50% without sacrificing accuracy. Ember-1 is the first in Fireworks' own model series, live as a research preview on Fireworks Serverless with a two-week window, made permanent based on community demand.
What the numbers show
The benchmark sheet's most informative rows: on Terminal Bench 2.1, Ember-1 scores 82.0%, beating K3's default max of 80.9% while using 51.9% fewer tokens; on DeepSWE 1.1 it is 75.2% versus 66.4%, another outright win; on SWE-bench Verified it posts 92.2% against 93.2%, narrowly behind but saving 15.5% of tokens. The production A/B test is more tangible: in one customer's coding workload, Ember-1 scored 0.753 versus K3's 0.751, with output tokens down from 49.3K to 29.9K — a 71.3% reduction in reasoning tokens and 39% in total tokens. Fireworks also switched its own internal coding traffic first; the official punchline is that developers never noticed the model had changed.
Read the fine print
An independent analysis (OrcaRouter's review blog) pours some useful cold water on the launch. First, every number is vendor-reported, with no third-party reproduction as of that writing. Second, the "about 40%" headline is an average: actual savings range from 5.9% on τ-2 Bench Airline to 51.9% on Terminal Bench — if your workload is short single-turn calls, you will barely feel it. Third, Ember-1 is a research preview with no independent rate card of its own; the dollar savings in the benchmark table are derived from K3's public pricing, and the OpenRouter model page lists the same price as K3 — meaning saved tokens equal saved money.
So what
The Ember-1 template is worth remembering: take an open-weight model that is already good, retrain exactly one axis — thinking length — and sell the token delta. Fireworks says token efficiency is becoming a theme for them, and that the future of open models is specialized models trained on specific workloads. For teams running K3 in agent loops, the pragmatic advice is to skip the leaderboard and shadow-test on your own traffic: send a share of real requests to both models and wait a week or two before switching anything. Compressing wasted deliberation is free profit; compressing a step the model actually needed shows up turns later as a wrong tool call.
Reference: Fireworks announcement · OrcaRouter analysis · OpenRouter model page