routerllm
Smart LLM request router — automatically route prompts to the right model based on cost, speed, quality or complexity.
pip install routerllm
The Problem
You have access to multiple LLMs — cheap ones, fast ones, powerful ones. But you use the same model for everything. Simple questions go to GPT-4o (overkill, expensive). Complex analysis goes to GPT-4o-mini (not enough, bad output).
routerllm fixes this automatically.
Quick Start
from routerllm import Router
router = Router(strategy="complexity")
router.add("openai", "gpt-4o-mini", api_key="sk-...") # cheap, fast
router.add("openai", "gpt-4o", api_key="sk-...") # powerful, expensive
# Simple → gpt-4o-mini
result = router.complete("What is 2+2?")
print(result.model) # "gpt-4o-mini"
print(result.cost_usd) # ~$0.000002
# Complex → gpt-4o
result = router.complete(
"Analyze the long-term macroeconomic impact of AI on developing nations, "
"comparing Keynesian and neoclassical perspectives."
)
print(result.model) # "gpt-4o"
print(result.routing.reason) # "Complex prompt (score: 0.78) → most powerful model"
Strategies
| Strategy | Description |
|---|---|
complexity |
Analyze prompt complexity → route accordingly (default) |
cost |
Always use cheapest model |
quality |
Always use most powerful model |
speed |
Always use fastest model |
# Set default strategy
router = Router(strategy="cost")
# Override per call
result = router.complete("Explain quantum entanglement", strategy="quality")
Dry Run (no API call)
decision = router.dry_run("What is machine learning?")
print(decision)
# {
# "would_use": "openai/gpt-4o-mini",
# "strategy": "complexity",
# "reason": "Simple prompt (score: 0.28) → cheapest model",
# "complexity_score": 0.28,
# "estimated_cost_per_1k": 0.00075
# }
Multi-Provider
router = Router(strategy="complexity")
router.add("openai", "gpt-4o-mini", api_key="sk-...")
router.add("openai", "gpt-4o", api_key="sk-...")
router.add("anthropic", "claude-haiku-4", api_key="sk-ant-...")
router.add("anthropic", "claude-opus-4", api_key="sk-ant-...")
router.add("gemini", "gemini-2.5-flash", api_key="AIza...")
RouterResult
result.output # LLM response text
result.model # Model that was used
result.provider # Provider that was used
result.cost_usd # Cost in USD
result.tokens_in # Input tokens
result.tokens_out # Output tokens
result.latency_ms # Response time in ms
result.success # True if no error
result.routing.reason # Why this model was chosen
result.routing.complexity_score # 0.0-1.0
License
MIT
Metadata
Release files for routerllm 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| routerllm-0.1.0.tar.gz | 11.1 kB | Without provenance | Details for routerllm-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| routerllm-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for routerllm-0.1.0-py3-none-any.whl |
Total release size: 21.0 kB
Release files / routerllm-0.1.0.tar.gz
| Download URL | routerllm-0.1.0.tar.gz |
|---|---|
| Size | 11.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fc6e7ca780ca12e90bc04d0fc20038a57df59458d435d692290777fca4457698
|
|
BLAKE2b-256 checksum How to use checksums |
78b195053b387b52fa98ac6ba23690efed17071bbb054315d3022892b8ed6031
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Release files / routerllm-0.1.0-py3-none-any.whl
| Download URL | routerllm-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ed1a9c5a873b49796edfcfa42b6ae01588890673d9879338e2551460c4d18c1d
|
|
BLAKE2b-256 checksum How to use checksums |
fb2be092d550310d9c591812e17a97e933e952e114f4bce9d0c92f3a3b8428aa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.0
|
Security for routerllm 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.