A curated list of awesome works in Routing LLMs paradigm (👉 Welcome to submit your contributions to this code repository)
Python
176
34 commits
updated Jul 30, 2026
A curated list of awesome works in Routing LLMs paradigm
🤩👉 Welcome to submit your contributions to this code repository.
| Paper | Conference/Journal | Code |
|---|---|---|
| Dynamic Model Routing and Cascading for Efficient LLM Inference: A Survey | arxiv'26 |
Pre‑judgment routing makes a routing decision before any generation starts. It relies only on the initial query and static model information, making it suitable for fast, one‑shot allocation. The three main strategies are feature matching, predictive scoring, and constrained optimization.
In deployment, routing often faces hard resource constraints (e.g., maximum latency or cost). This paradigm casts decision‑making as constrained utility maximization, using optimization strategies, multi‑objective formulations, or adaptive policies such as reinforcement learning to trade off quality and cost under budget limits.
Feature matching aligns the query representation and model capability representations in a shared space, then selects the model whose embedding is closest to the query. This approach can be lightweight and training‑free, but may degrade under distribution shift; adaptive methods use attention, policy learning, or prototype matching to stay robust.
| Brick: Spatial Capability Routing for the Mixture-of-Models (MoM) Paradigm (Brick) | ArXiv 2026 | General, Code, Math, Reasoning, Knowledge, Agent | github |
Predictive scoring learns a parametric estimator (e.g., a small neural network) that predicts the expected utility of each model for a given query. This enables quality‑cost trade‑offs, multi‑objective optimization, and robustness under distribution shift through techniques like minimax, causal inference, or uncertainty estimation.
Verification routing expands the decision space to intermediate generation states (partial outputs, confidence scores, or reasoning steps). It can revise routing decisions during inference, making the process more adaptive. Two common patterns are self‑assessment (reactive fallback) and collaborative generation (proactive, token‑level interleaving).
Collaborative generation integrates decision points directly into the generation process. Instead of a one‑shot model choice, multiple models collaborate step‑wise or token‑wise – e.g., switching control at reasoning boundaries or invoking expert models only at critical tokens. This enables fine‑grained, online adaptation.
Self‑assessment uses the model’s own confidence, uncertainty, or self‑consistency signals to decide whether to keep using a lightweight model or escalate to a stronger one. Decisions can be made at sequence end or at reasoning bottlenecks, often with a confidence threshold that triggers fallback.
Memory‑based routing conditions decisions not only on the current query but also on persistent historical memory – past queries, outcomes, or user interactions. This grounds uncertain online prediction in reusable evidence, enabling cross‑domain and multi‑turn adaptation. The main approaches are retrieval‑based and structured (graph‑based) routing.
Retrieval‑based routing finds a semantic neighborhood of historical samples similar to the current query, then aggregates observed model utilities from those samples (e.g., via kNN or proximity weighting). This local estimation adapts to query variations without heavy retraining and can handle distribution shifts gracefully.
Structured routing represents interactions, queries, tasks, and models as nodes in a topological history graph. Routing becomes a graph‑based scoring problem – e.g., using a Graph Neural Network to encode query and model nodes and predict their routing affinity. This supports relational reasoning, personalization, and long‑term planning.
| Title | Publish | Domain | Code |
|---|---|---|---|
| GraphRouter: A Graph‑based Router for LLM Selections (GRAPHROUTER) | ICLR 2025 | General, QA, Reasoning | GitHub |
| GMTRouter: Personalized LLM Router over Multi‑turn User Interactions (GMTRouter) | ArXiv 2025 | General, Dialogue, Math, QA | GitHub |
Analytical work studies system‑level behavior: theoretical bounds, benchmark evaluation, and safety risks. These works treat routing as part of a larger ecosystem with multiple objectives, constraints, and potential adversaries. The three sub‑categories cover theoretical modeling, benchmark & evaluation, and safety analysis.
Theoretical modeling applies tools from pricing theory, queueing analysis, and game theory to understand routing in constrained, dynamic, or strategic settings. For example, Stackelberg games model LLM service pricing, while contextual queueing bandits capture user retrials and scheduling. These studies reveal interdependencies among routing quality, latency, and cost.
Benchmarks assess routers across diverse tasks, model pools, and deployment constraints (latency, cost, robustness). They extend evaluation from static model selection to dynamic, multi‑dimensional trade‑offs. Representative benchmarks include RouterBench, RouterEval, VL‑RouterBench (multimodal), and AgentSelect (agentic scenarios). A unified framework is needed to jointly evaluate quality, latency, cost, robustness, and resource efficiency.
Safety analysis studies routing failures under adversarial, unreliable, or privacy‑sensitive conditions. Attackers can redirect queries to expensive models or bypass policies (e.g., confounder gadgets, adversarial suffixes). Defenses include contrastive learning, embedding‑based filtering, and hybrid surrogate models. Future routers must embed safety, privacy, and security as core design constraints.
| Method | Domain | Publish | Code |
|---|---|---|---|
| RerouteGuard (Understanding and Mitigating Adversarial Risks for LLM Routing) | STEM, Safety | ArXiv 2026 | – |
| Rerouting LLM Routers | General, Security | COLM 2025 | GitHub |
| R2A (Route to Rome Attack: Directing LLM Routers to Expensive Models via Adversarial Suffix Optimization) | Safety, Security | ACL 2026 | GitHub |
| Your Agent Is Mine: Measuring Malicious Intermediary Attacks on the LLM Supply Chain (Mine (research proxy)) | Agent, Security, Safety | ACM CCS 2026 | – |
Python
100.0%
A curated list of awesome works in Routing LLMs paradigm (👉 Welcome to submit your contributions to this code repository)
Python
176
34 commits
updated Jul 30, 2026
A curated list of awesome works in Routing LLMs paradigm
🤩👉 Welcome to submit your contributions to this code repository.
| Paper | Conference/Journal | Code |
|---|---|---|
| Dynamic Model Routing and Cascading for Efficient LLM Inference: A Survey | arxiv'26 |
Pre‑judgment routing makes a routing decision before any generation starts. It relies only on the initial query and static model information, making it suitable for fast, one‑shot allocation. The three main strategies are feature matching, predictive scoring, and constrained optimization.
In deployment, routing often faces hard resource constraints (e.g., maximum latency or cost). This paradigm casts decision‑making as constrained utility maximization, using optimization strategies, multi‑objective formulations, or adaptive policies such as reinforcement learning to trade off quality and cost under budget limits.
Feature matching aligns the query representation and model capability representations in a shared space, then selects the model whose embedding is closest to the query. This approach can be lightweight and training‑free, but may degrade under distribution shift; adaptive methods use attention, policy learning, or prototype matching to stay robust.
| Brick: Spatial Capability Routing for the Mixture-of-Models (MoM) Paradigm (Brick) | ArXiv 2026 | General, Code, Math, Reasoning, Knowledge, Agent | github |
Predictive scoring learns a parametric estimator (e.g., a small neural network) that predicts the expected utility of each model for a given query. This enables quality‑cost trade‑offs, multi‑objective optimization, and robustness under distribution shift through techniques like minimax, causal inference, or uncertainty estimation.
Verification routing expands the decision space to intermediate generation states (partial outputs, confidence scores, or reasoning steps). It can revise routing decisions during inference, making the process more adaptive. Two common patterns are self‑assessment (reactive fallback) and collaborative generation (proactive, token‑level interleaving).
Collaborative generation integrates decision points directly into the generation process. Instead of a one‑shot model choice, multiple models collaborate step‑wise or token‑wise – e.g., switching control at reasoning boundaries or invoking expert models only at critical tokens. This enables fine‑grained, online adaptation.
Self‑assessment uses the model’s own confidence, uncertainty, or self‑consistency signals to decide whether to keep using a lightweight model or escalate to a stronger one. Decisions can be made at sequence end or at reasoning bottlenecks, often with a confidence threshold that triggers fallback.
Memory‑based routing conditions decisions not only on the current query but also on persistent historical memory – past queries, outcomes, or user interactions. This grounds uncertain online prediction in reusable evidence, enabling cross‑domain and multi‑turn adaptation. The main approaches are retrieval‑based and structured (graph‑based) routing.
Retrieval‑based routing finds a semantic neighborhood of historical samples similar to the current query, then aggregates observed model utilities from those samples (e.g., via kNN or proximity weighting). This local estimation adapts to query variations without heavy retraining and can handle distribution shifts gracefully.
Structured routing represents interactions, queries, tasks, and models as nodes in a topological history graph. Routing becomes a graph‑based scoring problem – e.g., using a Graph Neural Network to encode query and model nodes and predict their routing affinity. This supports relational reasoning, personalization, and long‑term planning.
| Title | Publish | Domain | Code |
|---|---|---|---|
| GraphRouter: A Graph‑based Router for LLM Selections (GRAPHROUTER) | ICLR 2025 | General, QA, Reasoning | GitHub |
| GMTRouter: Personalized LLM Router over Multi‑turn User Interactions (GMTRouter) | ArXiv 2025 | General, Dialogue, Math, QA | GitHub |
Analytical work studies system‑level behavior: theoretical bounds, benchmark evaluation, and safety risks. These works treat routing as part of a larger ecosystem with multiple objectives, constraints, and potential adversaries. The three sub‑categories cover theoretical modeling, benchmark & evaluation, and safety analysis.
Theoretical modeling applies tools from pricing theory, queueing analysis, and game theory to understand routing in constrained, dynamic, or strategic settings. For example, Stackelberg games model LLM service pricing, while contextual queueing bandits capture user retrials and scheduling. These studies reveal interdependencies among routing quality, latency, and cost.
Benchmarks assess routers across diverse tasks, model pools, and deployment constraints (latency, cost, robustness). They extend evaluation from static model selection to dynamic, multi‑dimensional trade‑offs. Representative benchmarks include RouterBench, RouterEval, VL‑RouterBench (multimodal), and AgentSelect (agentic scenarios). A unified framework is needed to jointly evaluate quality, latency, cost, robustness, and resource efficiency.
Safety analysis studies routing failures under adversarial, unreliable, or privacy‑sensitive conditions. Attackers can redirect queries to expensive models or bypass policies (e.g., confounder gadgets, adversarial suffixes). Defenses include contrastive learning, embedding‑based filtering, and hybrid surrogate models. Future routers must embed safety, privacy, and security as core design constraints.
| Method | Domain | Publish | Code |
|---|---|---|---|
| RerouteGuard (Understanding and Mitigating Adversarial Risks for LLM Routing) | STEM, Safety | ArXiv 2026 | – |
| Rerouting LLM Routers | General, Security | COLM 2025 | GitHub |
| R2A (Route to Rome Attack: Directing LLM Routers to Expensive Models via Adversarial Suffix Optimization) | Safety, Security | ACL 2026 | GitHub |
| Your Agent Is Mine: Measuring Malicious Intermediary Attacks on the LLM Supply Chain (Mine (research proxy)) | Agent, Security, Safety | ACM CCS 2026 | – |
Python
100.0%