TokenWise — Measurement-Driven Model Router

Overview

The upstream package advertises model-tier routing, local NDJSON usage logs and an A/B comparison command. Evaluate those capabilities only in an installed, reviewed revision with the user's authorized model budget and actual workload. Task difficulty, response-quality rubrics and reported costs remain estimates unless independently measured.

This entry describes the upstream workflow; it does not bundle its commands or measurement implementation. Verify the installed revision, supported models and actual routing behavior before relying on a report. A user's workload and billing plan determine whether routing reduces paid usage.

When to use

• Cutting Claude Code token spend without sacrificing output quality
• Validating whether Haiku/Sonnet is "good enough" for a specific task class before trusting auto-routing
• Auditing where Opus tokens are actually being burned
• Logging per-session cost data for finance or chargeback

Subcommands