Loading
90 days of the enterprise, pro and team plans free, no card needed. See the plans
AI cost savings calculator
Change the figures to match your workload and the business case recomputes - gross savings, the plan fee, net benefit, payback and first-year ROI. It opens with an example workload so you can try it before you have numbers of your own. The two figures that decide the outcome - how much routing saves on a request and how many requests it may move - come from your own traffic: the quickest way is to upload last month's provider bill; the thorough way is the routing audit below.
Start from the example. The two figures that decide the outcome - the saving and the eligible share - should come from your own bill analysis or routing audit, not a guess.
These are the example workload's figures, not a customer's result - replace the inputs with your own spend. Read the conservative column first: it takes ten points off the audit saving; a router that has learned from your outcomes typically adds about eight.
Year-1 net saving - Conservative
$172,140
after the plan fee and the integration effort
Year-1 net saving - Audit
$215,820
after the plan fee and the integration effort
Year-1 net saving - Audit + learned
$250,764
after the plan fee and the integration effort
| Per month | Conservative | Audit | Audit + learned |
|---|---|---|---|
| Gross savings | $13,104 | $16,744 | $19,656 |
| Platform fee | $999 | $999 | $999 |
| Engineering time recovered | $2,400 | $2,400 | $2,400 |
| Net benefit | $14,505 | $18,145 | $21,057 |
| Payback | 0.1 mo | 0.1 mo | < 0.1 mo |
| First-year ROI | 12.4x | 15.5x | 18.0x |
| Year-1 net (after integration) | $172,140 | $215,820 | $250,764 |
Gross savings = spend x saving x share the router may move. Net benefit adds the engineering time recovered and any avoided incidents and subtracts the plan fee; payback = integration effort / net benefit; first-year ROI = (12 x net - integration) / (12 x fee + integration). In production the savings ledger records baseline and routed cost per request, so finance can recompute the gross figure from the export. Cost per request today: $0.0133.
No credit card. The default saving (46%) is a conservative reading of the published benchmark; your own bill replaces it.
Photo: RDNE Stock project
The quickest way: upload the usage export your provider already gives you under AI spend and read the saving and the share of the bill the router could move. The thorough way: replay a week of your traffic through your catalogue on your own machine. The report returns the saving, the share of requests above the quality floor and every policy violation your current routing allowed.
pip install "opensmartroute[yaml]"
# --baseline is the id in your targets.yaml of the model your traffic runs on today
osr -t targets.yaml audit traffic.jsonl --baseline llm-frontier --monthly 3000000 --markdownThe traffic file is one JSON object per line exported from your current gateway's logs: the request text, and where you have them the model that answered, the token counts and the cost. Nothing is executed and nothing is sent anywhere - the replay runs on your machine against your own catalogue. Ask us to run it with you if you would rather not do it alone.
In production the savings ledger records baseline versus routed cost per request together with the reported quality, so finance can reconcile the fee against real spend.
ep = RouterBuilder(registry).with_savings(baseline="max").build()
print(ep.savings.report(window_s=30 * 86400).to_markdown())Reference formulas and worked examples: plans and quotas. Want the numbers checked against your own traffic before you commit? Ask for a routing audit. Compare against your current gateway on the comparison pages.