Entelligence Model Router

What the router changes

The developer workflow stays the same. Routing happens between the supported coding agent and the model provider.

The policy is global. Choose Balanced or Eco, then activate or pause routing for the workspace.

Every routed request is measurable. Sessions show the selected model, token usage, cost, and savings.

Balanced or Eco

Mode	Best for
Balanced	A first rollout that prioritizes quality while reducing avoidable spend
Eco	A more aggressive cost policy that routes to the cheapest model expected to clear the quality floor

Start with Balanced. Move to Eco after representative tasks perform well and the team understands the decision log.

Read the dashboard

Signal	What it tells you
Baseline spend	Estimated cost using the comparison model shown by the product
Sessions auto-routed	Share of eligible sessions handled by the router
Monthly savings	Difference between the displayed baseline and routed cost
Projected spend	Estimated routed spend for the selected period
Savings over time	When routing produced the largest cost difference
Model distribution	Where routed requests went

Savings are a comparison against the displayed baseline. Use the same date range and pricing source when reconciling the number with billing.

What the router changes