Cheapest-LLM Router
Related Servers
Alternatives to Cheapest-LLM Router
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to compare costs, performance, and quality across 150+ models from 26 LLM providers, estimate or predict workload spend, route tasks to cost-effective models, and track actual recorded usage. Prices are cross-checked against a live external registry so drifted figures are flagged rather than silently served.MIT
- AlicenseNot gradedqualityBmaintenanceEnables LLM clients and coding agents to analyze prompts and recommend the cheapest AI model that meets the task requirements across text, voice, video, and other modalities, projecting monthly cost savings against a flagship baseline.MIT
- FlicenseNot gradedqualityAmaintenanceExposes 178 enabled chat routes across 23 cataloged LLM providers behind one OpenAI-compatible endpoint, so agents can query pooled free-tier and keyless models with automatic failover and per-day usage tracking. It can also report live provider capacity and health when a route is rate limited or down.-
- AlicenseNot gradedqualityDmaintenanceDiscovers LLM models in real time from cloud providers and local Ollama instances, returning compatibility profiles and live pricing so AI agents can route tasks to the cheapest viable model without breaking tool calls or context clipping.10MIT
- AlicenseNot gradedqualityDmaintenanceA model routing advisor for autonomous agents — get cost-optimised LLM recommendations via MCP.6 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables agents to query and route requests across a pooled catalog of free and keyless LLM provider routes through one OpenAI-compatible gateway. Supports model discovery, failover, and capacity checks without requiring credentials when a keyless route is available.-
TDQS
Scored across 4 tools
route and cache_route overlap significantly—cache_route is explicitly described as 'same as route' with caching—so an agent may hesitate between them. cost_compare and list_models are clearly distinct, and cost_compare vs route is mostly clear (ranking vs selection).
All tools use snake_case consistently. cost_compare, list_models, and cache_route follow a verb_noun pattern, while route is a single verb, which is a minor deviation.
Four tools is well-scoped for a router server: one for routing, one for cached routing, one for cost comparison, and one for listing models. Each earns its place without bloat.
The surface covers routing, cached routing, cost comparison, and model listing, which are the core operations. Minor gaps exist, such as no direct single-model cost lookup or cache management, but core workflows are supported.