Savings & pricing

RouteShift is BYOK by default: you bring provider keys, the proxy never resells inference. The only thing RouteShift charges for is the routing layer itself — and the charge is 3% of the measured savings, not a flat platform fee. If you don't save money, you don't pay.

Rendering diagram…

Where prices come from

Token prices are pulled from the LiteLLM model_prices_and_context_window.json catalog — the de-facto open-source registry of every public LLM's pricing. RouteShift syncs the catalog weekly via a GitHub Action that opens a PR if the catalog has changed; merge the PR and the new prices ship on the next deploy.

This means:

• New model launches show up in RouteShift's pricing within a week without any manual data entry.
• Provider price drops propagate the same way.
• The proxy and the dashboard read from the same generated TypeScript file (packages/shared/src/litellm-pricing.generated.ts), so analytics and routing decisions always use the same numbers.

If a model isn't in the catalog (e.g. a private deployment), RouteShift falls back to an explicit per-deployment price you set in Settings → Providers.

How savings are measured

For every request, RouteShift records:

• Actual cost — what the request actually cost on the model it was routed to.
• Baseline cost — what the same request would have cost on your declared baseline model. The baseline defaults to the model the client originally asked for; teams can override it (e.g. "everyone was on gpt-4o before — measure against that").

Savings = baseline cost − actual cost. RouteShift floors negative savings (a "savings" that's actually more expensive than baseline) to zero before billing — you only pay on net wins.

Choosing a baseline

The baseline model is the "what would we have paid without RouteShift" reference. By default it's the model the client originally requested — so if your code asks for gpt-4o and RouteShift routes it to gpt-4o-mini at lower cost, the savings are measured against gpt-4o pricing.

You can override the baseline per team at Settings → Teams → … → Baseline model. Common patterns:

The 3% savings-share

Once a month, RouteShift sums total savings for the workspace and bills 3% of it through Stripe. The line item shows up in your invoice with a link to the underlying calculation.

• Generous free tier — workspaces under a configurable monthly threshold pay nothing.
• No platform fee — there is no monthly base charge, no seat charge, no minimum.
• No markup on tokens — the 3% comes out of savings RouteShift produced, not on top of provider pricing.
• Transparent ledger — every billed dollar links to the request logs that produced it.

Reading the savings dashboard

The Billing → Savings page shows:

• Trailing 30-day savings — total USD saved across all keys, with a daily sparkline.
• Per-model breakdown — which model swaps produced the most savings (e.g. gpt-4o → gpt-4o-mini saved $X, claude-3-5-sonnet → claude-3-5-haiku saved $Y).
• Per-key breakdown — which teams or API keys are driving the savings.
• Projected monthly bill — 3% of trailing savings, updated daily.

Billing FAQ