Cost estimator
Paste a prompt. The router estimates tokens, scores every target and quotes each one with its price split into input and output, expected quality and latency, then names the recommended, cheapest capable, best-quality and fastest picks.
Nothing is executed and the prompt is not stored. Tokens are estimated from the text; costs use each model's list price.
The router reads your prompt, estimates tokens, scores every model, agent and skill in the catalogue and quotes each one with its expected quality and latency.
Recommended models
Live quotes of representative prompts against this deployment's catalogue, recomputed every minute. Rankings follow the targets, list prices and learned quality, not a hand-maintained list.
Qwen3.5 4Bllm
Why: domain fit 50% · action fit 50% · complexity fit 100%
Qwen3.5 4Bllm
domain fit 50% · complexity fit 100% · quality prior 0.60
GLM 4.7 Flashllm
domain fit 67% · complexity fit 100% · quality prior 0.93
skill-summarizeskill
Qwen3.5 4Bllm
domain fit 33% · complexity fit 100% · quality prior 0.55
Qwen3.5 4Bllm
router's pick for 2 use cases · cheapest 1x · best quality 1x
router's pick for 1 use case · cheapest 1x · best quality 2x
router's pick for 1 use case · cheapest 3x · best quality 1x
Before the bill, not after
Photo: Jakub Zerdzicki
The same quote is one call away: anonymous quotes are rate limited per client, keyed quotes apply your tenant rules and show up in your usage.
curl -s /api/v1/estimate -H "Authorization: Bearer $OSR_KEY" \
-H "Content-Type: application/json" \
-d '{"text": "Summarise this contract...", "monthly_requests": 50000}'osr estimate quotes against a local catalogue and the MCP server exposes estimate and recommend tools to VS Code, Cursor and Claude.
from opensmartroute.estimate import estimate
q = estimate(router, "Summarise this contract...", output_tokens=300)
print(q.recommended.name, q.recommended.cost_usd, q.savings_usd)Set up the IDE integration under Integrations or read the MCP guide.
Why: rule 'legal-persona' prefers · domain fit 100% · complexity fit 100%
Why: rule 'pii-stays-onprem' prefers · domain fit 50% · complexity fit 100%
router's pick for 1 use case · best quality 1x
router's pick for 1 use case
2 placements · best quality 1x