Local routing calculator

Route batch work before you spend.

Load real counts and token estimates. The studio checks context, complexity, per-item cost, and budget using editable sample assumptions, then shows every operand behind the route.

Workload ledger

What needs to run?

Average tokens are per item. Changes recalculate immediately and stay on this device.

Computed routes

See the choice and the rejected alternatives.

Each row exposes the selected model, input/output split, context use, and every eligibility failure before any export.

Editable assumptions

Make the economics yours.

These sample values are deliberately visible. Verify them against the provider and workload before approving spend.

Checking local libraries...

Model table

Routing rules

Batch budget USD Maximum per-item cost USD Batch discount %

Formula audit

The arithmetic stays inspectable.

items x ((input tokens x input $/M + output tokens x output $/M) / 1,000,000) x (1 - discount)

Edge-case handling

Context overflow, tier mismatch, zero items, negative values, duplicate IDs, malformed CSV, and impossible budgets produce explicit diagnostics without erasing the last valid plan.

Decision evidence

“I can defend the route because the assumptions and rejected alternatives are visible.”

“Changing one token estimate updates the route, total, and budget consequence together.”

“The manifest carries the same operands the team reviewed on screen.”