Skip to main content
RouteShift charges 3% of measured savings — see Savings & pricing for the full mechanics. This page covers what you see in the dashboard, how invoices are produced, and how to slice spend across keys.

​
Spend breakdown

The Billing → Spend page shows total workspace spend with three breakdowns:
  • By virtual key — every key ranked by 30-day spend, with request count and a sparkline. Drill into any key to see the underlying request log.
  • By metadata tag — group by any tag dimension (env, customer, agent, experiment, etc.). Useful for chargebacks or per-customer attribution.
  • By model — every model that produced spend, with mean cost per request and total tokens. The companion view at /models/compare lets you A/B alternatives.
All numbers are computed in microcents and rendered as USD with millicent precision so small calls aggregate without rounding error.

​
Plans

RouteShift ships a single tier: 3% of measured savings, no monthly fee, no seat fee, no minimum. A generous free tier covers low-volume usage at zero cost. For organizations that need invoicing, custom retention, or BYO Stripe — contact sales@routeshift.io. Otherwise, billing is fully self-serve through the Stripe customer portal.

​
Stripe customer portal

Open Billing → Manage to launch the Stripe-hosted portal. From there you can:
  • Update payment method.
  • Download past invoices.
  • Cancel the subscription (data and keys are retained; new requests stop billing immediately).
  • View upcoming invoice with line items linked to the underlying request logs.

​
How invoices line up with usage

Every monthly invoice contains a single line item — “RouteShift savings share” — with the following metadata:
  • period_start / period_end — calendar month boundaries (UTC).
  • gross_savings_microcents — total savings produced in the period.
  • share_rate — currently 0.03.
  • audit_url — link back to the dashboard’s billing breakdown for that month.
The audit URL is durable: if you ever need to reconcile a charge, the underlying request logs are preserved for the lifetime of the workspace.