Skip to content
ML Academy

LLMs, GenAI, RAG, agents, evaluation · insight-0672

Route easy requests to a small model and escalate only when a check fails

Evidence type
empirical finding
Difficulty
medium
Roles
Applied AI, ML engineer, Data scientist
Industries
e-commerce, cross-industry

Summary: situation, action, reason, boundary

  1. Situation

    All traffic goes to the largest available model, although most requests are simple lookups or classifications.

  2. Action

    Build a cascade: a small model answers first, a cheap check (schema validity, retrieval confidence, a verifier score) decides whether to accept, and failures escalate to a larger model; tune the threshold on the golden set.

  3. Reason

    FrugalGPT showed that a learned cascade over models of different prices could match the strongest single model at much lower cost on the authors' tasks, because many queries do not need the expensive model.

  4. Boundary

    High-volume classification, extraction and FAQ-style traffic.

Symptom or risk

Cost and latency are set by the hardest few percent of requests.

Exceptions

When the acceptance check is unreliable, escalation errors cost more than the savings.

Trade-offs

Escalated requests pay for two calls and more latency.

Pitfalls

Tuning the router on aggregate accuracy and missing a slice it consistently misroutes.

Lessons and concepts

Claims and their sources