Hugging Face Blog

Model Routing Is Simple. Until It Isn’t.

Towards Data Science
Oct 5

How to Build a Cheap, Yet Reliable Model Router With Jev

The article explains how to create an inexpensive yet dependable model router using Jev, highlighting that model routing can now be considered a design decision rather than merely a system improvement. It outlines the steps and benefits of implementing this approach, emphasizing its practicality and cost-effectiveness. The piece serves as a guide for developers looking to integrate efficient model routing into their workflows.

By Thuwarakesh Murallie
arXiv AI
Sep 30

Routing Should Pay for Itself: Sparse Supervision for Economical LLM Routing

The paper introduces SaveRouter, a sparse‑supervision framework for large language model routing that selectively gathers informative model feedback and shares capability information across related queries. By using only about 33–41% of available training feedback, SaveRouter achieves competitive or superior routing quality while reducing the break‑even deployment volume by 1.9–9.5× compared to conventional routers. The study also shows that the supervision level that minimizes serving cost may differ from the one that yields the earliest payback.

By Guannan Lai, Gelin Bian, Hao-Xuan Ma, Jun-Peng Jiang, Long Chen, Jian-Dong Liu, Zhi-Hao Tan, Han-Jia Ye
arXiv Computation and Language
1d ago

Cluster, Route, Escalate: Cascaded Framework for Cost-Aware LLM Serving

arXiv:2606.27457v2 Announce Type: replace-cross Abstract: Serving open-weight language models on premises forces a trade-off between accuracy and computational cost. Hosting models of different sizes...

By Yasmin Moslem, Magdalena Kacmajor, Vasudevan Nedumpozhimana, Ammar Abbas, Solmaz Panahi, David Lynch, Zhuangzhuang Nie, Alexandros Agapitos, Aleksandar Milenovic, Hongmeng Song, Yucheng Shi, Yue Pan, Patricia Buffini, John D. Kelleher
arXiv AI
6d ago

COMPASS: Routing via Capability-Oriented Model Profiling with Adaptive Search, Selection, and Tool Use

COMPASS is an agentic router that uses a capability-oriented model profiling approach to select large language models (LLMs) efficiently. It follows a routing recipe, gathers performance and cost evidence through tools, and can inspect candidate answers before making a selection. In evaluations on LLMRouterBench and DeepSWE, COMPASS improves accuracy while reducing model‑call cost compared to specialized and trained routing baselines, and it can adapt to new models without retraining.

By Amin Rezaei, Pouya Parsa
Towards Data Science
Oct 20

The Hidden Cost of LLM Routing: Why Switching Models Costs More

The article examines the practice of routing requests to different large language models (LLMs) during a single session. It reports that switching models mid‑session can negate the expected cost savings from using cheaper inference options. The author conducted tests to illustrate how these switches impact overall expenses.

By Nhu Hoang
arXiv Machine Learning
Oct 12

CopRoute: Dependence-Aware Conformal Routing for Language Models

CopRoute introduces a dependence-aware conformal routing method for language models that orders models by the number of new queries each correctly answers beyond those already covered, selecting the minimal cutoff that satisfies a target all‑miss risk. This approach accounts for model failure dependencies—such as shared training data or architecture—that traditional risk‑controlled policies ignore. Experiments on RouterBench and RouterEval show CopRoute achieves fewer certified inference calls than state‑of‑the‑art methods, reducing calls by up to 79 % in some cases while maintaining the same risk level.

By Siva Rajesh Kasa, Santhosh Kumar Kasa, Karan Gupta
Simon Willison
Sep 11

So you want to use OpenRouter?

OpenRouter advertises automatic fallback and cost‑effective routing to the best backend provider for a single API endpoint. However, Mohamed Moustafa highlights that different providers use varied serving software, optimizations, and capabilities, leading to inconsistent behavior across the same endpoint. Users can mitigate this by specifying a provider with the provider.only option and checking available providers via the /endpoints method.