Fireworks AI 发布 Ember-1:基于 Kimi K3 后训练,token 用量减少约 40%
Fireworks AI Releases Ember-1: A Post-Trained Kimi K3 That Uses About 40% Fewer Tokens
Fireworks AI 发布 Ember-1,这是 Fireworks Research 基于 Moonshot AI 开源权重模型 Kimi K3 后训练得到的专用模型,官方称在保持 Kimi K3 质量的同时减少约 40% 的 token 用量。该模型目前仅通过 Fireworks serverless API 以 Research Preview 形式提供,未公开权重、训练代码和具体训练算法,因此暂不支持自托管。Fireworks 称在 7 项基准和 2 家客户的生产流量中,K3 的推理过程被缩短 35% 至 50% 且未牺牲准确率;与 2 家客户的生产编码负载 A/B 测试中,每任务输出 token 从 49.3K 降至 29.9K,推理 token 下降 71.3%,总 token 下降 39%,任务得分 0.753 对 0.751 基本持平,其中一家客户已在生产环境使用。Ember-1 在 Fireworks 上每 token 价格与 Kimi K3 相同,为输入 $3.00、缓存输入 $0.30、输出 $15.00 每 1M tokens,节省完全来自生成更少的 token。
推荐理由
AI 评分 66
Fireworks 公开了 Ember-1 的评测与 A/B 数据,读者可据此判断缩短推理链能否在不掉质量的前提下降低 token 成本。
主题
正文
当前显示原文,中文全文译文尚未就绪。
Fireworks AI has released Ember-1 , a specialized model from Fireworks Research built by post-training Moonshot AI’s open-weight Kimi K3 . Ember-1 learns to produce shorter reasoning traces while keeping task accuracy. This is different from lowering the reasoning effort setting at inference time. According to the Fireworks release post , Ember-1 delivers Kimi K3’s quality with about 40% fewer tokens.
Is it deployable? Yes, but only through the Fireworks serverless API as a Research Preview. Fireworks has not released Ember-1’s weights, training code, or exact training algorithms, so self-hosting is not an option today.
Fireworks team reports that reasoning models like Kimi K3 sometimes spend more than 90% of generated tokens on internal reasoning. That cost compounds in multi-turn agentic workloads. Each turn replays prior reasoning back to the model. Context grows roughly quadratically with the number of turns. Long traces from early turns get re-read, and re-billed, on every later call.
Fireworks team explains how customers wanted K3’s coding capability at lower cost. Turning down K3’s reasoning effort did not solve it. Lower effort settings gave up too much quality. So the team trained the model to reason more efficiently instead.
Not all of K3’s reasoning is waste. Some of it is useful self-reflection, like revisiting an assumption or reacting to feedback. Ember-1 keep that behavior while cutting redundant reasoning and unproductive loops.
The training collection spans mathematics, coding, instruction following, conversation, search, tool use, and software engineering. It covers both standalone problems and extended multi-step interactions. Task and environment feedback guides on-policy planning and learning. Fireworks team ran more than 50 training experiments and over 200 evaluations. They also developed new training algorithms, which it has not published. All training ran on Fireworks Serverless Training . Fireworks states it used its own data and no customer data.
Fireworks compared Ember-1 with Kimi K3 at three reasoning effort levels. Cost was computed with public Kimi K3 API pricing. These are Fireworks’ own published evaluations.
Ember-1 leads K3 Max on Terminal Bench 2.1 and DeepSWE 1.1. It trails slightly on SWE-bench Verified and SWE-Interact. Across seven benchmarks and two customers’ production traffic, Fireworks says K3’s reasoning was shortened by 35 to 50% without sacrificing accuracy.
On Doximity’s Bedside Bench, a physician-validated set of 500 clinical cases, Ember-1 set a new cost-per-task Pareto frontier. That result comes from Fireworks’ new Specialized Intelligence Index .
Fireworks ran live A/B tests with 2 customers on production coding workloads. Both saw roughly 35% fewer tokens per task at comparable quality. In the published run, output tokens fell from 49.3K to 29.9K per task. Reasoning tokens dropped 71.3% and total tokens dropped 39%. The task score was essentially unchanged: 0.753 for Ember-1 versus 0.751 for K3. Average steps fell from 23.8 to 21.4. One customer now runs Ember-1 in production.
Ember-1 costs the same per token as Kimi K3 on Fireworks: $3.00 input, $0.30 cached input, and $15.00 output per 1M tokens. The savings come entirely from generating fewer tokens. At that output rate, the A/B figures work out to about $0.74 versus $0.45 in output cost per task (our calculation, output only).