Echo——使用开放权重模型,以三分之一成本实现 Fable 级结果
Show HN: Echo – Fable-level results at 1/3 the cost using open-weight models
我们发现了什么
我一直在构建 Echo(https://echo.tracerml.ai/),这是一个实验:将一组开放权重模型组成一个 AI 系统,而不是选择单一模型并将其用于每项任务。我目前花了很多时间理解这些失败案例,并测试同样的方法是否适用于编程和智能体任务;在这些任务中,衡量每个决策的质量会困难得多。
- 来源:Hacker News(发现于 2026-07-24)
- 证据等级:D · 发现产品或需求信号,暂未获得可核验的商业证据。
- 商业模式:API / Usage-based
- 主题:独立产品
- 初筛评分:22.9/100 · 收录 1 次
证据,比故事更重要。
规则清洗与初筛,未经人工商业核验。原文语境、实际客户和付费情况仍需自行验证。
引用与数字披露
来源类型(原作者自述/第三方测算/媒体转引)需采集端标注,本版尚未落字段。
- 作者
- 未标注
- 抓取日期
- 来源类型
- 未标注
- 币种
- 未标注
- 口径
- 未标注
- 披露主体
- 未标注
- 披露日期
- 未标注
中文辅助译文(全文)
我一直在构建 Echo ( https://echo.tracerml.ai/ ),这是一项实验,旨在用一组开源权重(open-weight)模型组成一个 AI 系统,而不是为每项任务都选择单一的模型。这一切源于一个简单的实验。我选取了一组模型,包括 GLM-5.2、Kimi K2.7 等,并让它们在相同的评测上运行。然后我衡量了这样一种情况:如果针对每个问题,你能够事先知道哪些模型有用,以及它们的输出应该如何组合。理论上这个系统表现得明显优于模型池中的任何一个单独模型。当然,这在实际中无法部署,因为它依赖于在看到结果之后才知道哪些决策是好的。Echo 就是我试图在事先没有这些信息的情况下,回收部分上述优势所做的尝试。对于每个请求,Echo 决定应分配多少算力、哪些模型应参与,以及它们的工作成果应如何组合。某些提示词可能只需要相对较少的推理,而另一些则受益于多个模型协同处理问题的不同部分。构建过程中让我感到惊讶的一件事是模型之间是多么互补。一个总体明显较弱的模型,在某些特定问题上或作为组合的一部分时,仍然可能极其有用。在我最初的一组评测中,Echo 始终优于其模型池中表现最好的单一模型。它还在大约三分之一的推理成本下,达到了与 Fable(我用作较强对比系统之一)大致相当的综合结果。不过在某些情况下,Echo 仍会做出错误的算力分配或组合决策。我目前正在花大量时间去理解这些失败案例,并测试同样的方法是否在编码和智能体类任务中仍然成立——在这些任务中,衡量每一步决策的质量要困难得多。
我构建了一个聊天界面(echo.tracerml.ai)和一个兼容 OpenAI 的 API ( https://echo.tracerml.ai/docs/api ),以便在评测之外测试这个系统。下面是一段简短、高层次的介绍视频,讲解它的工作原理:https://www.youtube.com/watch?v=lJFJSvOdXhg 我把评测方法、各模型的结果、成本以及目前的局限性写在了这里:https://echo.tracerml.ai/eval 非常欢迎你来试用!尤其是当你遇到一些奇怪的失败案例,或者发现算力分配看起来不太合理的地方。
译文由上游机器翻译生成,可能有误;判断请以英文原文为准。
英文原文(来源本站未改写)
I’ve been building Echo ( https://echo.tracerml.ai/ ), an experiment in making one AI system out of a pool of open-weight models rather than choosing a single model and using it for every task.It started with a simple experiment.I took a group of models, including GLM-5.2, Kimi K2.7 and others, and ran them on the same evaluations.Then I measured what would happen if, for each problem, you somehow knew in advance which models would be useful and how their outputs should be combined.That hypothetical system performed substantially better than any individual model in the pool.
Of course, it is not something you can actually deploy because it relies on knowing which decisions were good after seeing the result.Echo is my attempt to recover some of that advantage without having that information in advance.For each request, Echo decides how much computation to allocate, which models should participate, and how their work should be combined.Some prompts may only need a relatively small amount of inference, while others benefit from multiple models working on different parts of the problem.One thing that surprised me while building it was how complementary the models are.
A model that is clearly weaker overall can still be extremely useful on particular problems or as part of a combination.On my first evaluation mix, Echo consistently performed better than the best individual model in its pool.It also reached roughly the same aggregate result as Fable, which I used as one of the stronger comparison systems, at around one third of the inference cost.There are still some cases where Echo makes the wrong allocation or combination decision.I’m currently spending a lot of time understanding those failures, as well as testing whether the same approach holds up on coding and agentic tasks where measuring the quality of each decision becomes much harder.
I built a chat interface (echo.tracerml.ai) and an OpenAI-compatible API ( https://echo.tracerml.ai/docs/api ) so the system can be tested outside the evaluation setup.Here is a short/high level video on how it works: https://www.youtube.com/watch?v=lJFJSvOdXhg I wrote up the evaluation methodology, individual model results, costs and current limitations here: https://echo.tracerml.ai/eval I would love for you to try it!Especially if you hit any weird failure cases or places where the allocation looks unintuitive.
这条还缺什么证据?
下面每条都由本条已有字段推出(等级、理由、商业模式、来源次数、是否演示), 本站不生成推测性结论;通用验证方法放在方法论页。
- 可核验的收入或付费证据查官网定价页与付费口径;第三方数据源(如 GetLatka)只作旁证,需标注来源与时点。
- 只有单一来源找一手站点或其他渠道是否重复出现同一产品;社区热帖数量不等于商业进展。
通用验证清单(谁有这个问题/谁愿意付费/一个人能交付哪一小步)见我们的筛选方法。