Live data from Hacker News

Show HN: Echo – Fable-level results at 1/3 the cost using open-weight models

news.ycombinator.com

161–170 of 254 posts

Re: Show HN: Echo – Fable-level results at 1/3 the cost using open-weight models

#161
post #83

This does not really work well, if you don't know the complexity of the problem ahead of time and ensure all future conversations go to the same model. Else, you break the cache by doing a round robin of the same conversation across different models. Likely you'll end up paying more than what it would've cost with a cache aware system

Cache hits should be part of the strategy.

Re: Show HN: Echo – Fable-level results at 1/3 the cost using open-weight models

#163

How is this different from what that feature OpenRouter does?

Not much probably but I'd rather my agentic system route to model choice (happy to use OpenRouter as a catalog) than something in the cloud. I.e. pi.dev routes > call this and it decides based on today's algo. In other words routing should be in my source code not yours.

Re: Show HN: Echo – Fable-level results at 1/3 the cost using open-weight models

#164
I wouldn't be surprised if "the best model" becomes a niche concept over the next few years. For most production systems the winning architecture may end up being an orchestrator that knows when to call a cheap model when to escalate to a stronger one and when to combine multiple outputs.

Re: Show HN: Echo – Fable-level results at 1/3 the cost using open-weight models

#166

I wouldn't be surprised if "the best model" becomes a niche concept over the next few years. For most production systems the winning architecture may end up being an orchestrator that knows when to call a cheap model when to escalate to a stronger one and when to combine multiple outputs.

[deleted]

Re: Show HN: Echo – Fable-level results at 1/3 the cost using open-weight models

#170

> Fable-level results at 1/3 the cost I am guessing this is not targeting those of us on the heavily subsidized $200/mo plans. Sure, these plans may be temporary, but none of us really know how temporary they are. Until then, 1/3rd of the published API pricing is not very appealing.

I burned though my weekly fable usage last night on the $200 plan. I had $200 in promotional usage credits and was in the middle of executing a moderate sized coding plan. Ran on usage credits for about 1h 15m and burned $120 in usage credits. I was astounded to see how fast the $ usage added up. One problem was that I was using sub-agent execution so multiple agents were running simultaneously and I realized at the…

You're good.

Dude that topped Meta's tokenmaxxxing board before it was shut down used 265 billion tokens in a month. I kid you not.

Post reply on HN