Everyone is building LLM routers, we deprecated ours
The company has deprecated its LLM router due to mixed results and various problems. The router was intended to reduce inference costs by selecting the most cost-effective model for each request. However, the company found that complexity cannot be deduced from the prompt alone, cache is more effective than routing for reducing costs, and LLM routers break behavior consistency.
- ▪The company launched its LLM router in March and deprecated it in June due to mixed results.
- ▪The router was designed to classify each request into one of four different tiers of complexity: simple, standard, complex, and reasoning.
- ▪The company found that cache reads are between 75% and 90% cheaper than uncached inputs, making cache more effective than routing for reducing costs.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,089 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Manifest |
| Canonical URL | https://manifest.build/blog/why-we-deprecated-our-llm-router/ |
| Publication time | Fri, 31 Jul 2026 18:06:39 +0000 |
| Retrieval time | 2026-07-31T18:23:59.191Z |
| Last seen | 2026-07-31T18:23:59.191Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 4TP_Q2BTFO6L · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
← Back to blog Everyone is building LLM routers, we deprecated ours Bruno Perez · Jul 31, 2026 · 3 min read We don’t believe in model routing anymore. For most use cases, sticking to a single battle-tested model is the best thing you can do. Recently, there’s been huge hype around AI model routers that select the model that will respond to your request on the fly. There have been many launches in recent weeks with similar promises of reducing inference costs. We had our LLM router too, and decided to remove it. Some context first: we launched the Manifest LLM router in March as a key feature in our LLM gateway, and we deprecated it in June, shutting it down for good on September 1st.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Manifest.
Discussion
0 commentsMore from Manifest
