Routing cuts OpenClaw Max usage cost by 85%: $200/mo to $30/mo with API routing

One OpenClaw Max user ran the numbers and discovered that only about 15% of their daily token usage actually required a frontier model like Opus. The rest—file reads, git status, project context scanning, test generation, scaffolding, formatting, renaming, simple refactors—could be handled by cheaper models like Sonnet or even cheaper alternatives.

Token usage breakdown

• ~40% — file reads, git status, project context scanning: don't need Opus
• ~25% — test generation, scaffolding, boilerplate: Sonnet handles identically
• ~20% — formatting, renaming, simple refactors: any model works
• ~15% — actual hard reasoning, cross-file architecture: the only part that needs Opus

By switching from the $200/month Max subscription to the API with routing rules, the user configured Sonnet for routine tasks and Opus only for cross-file reasoning. The monthly bill dropped to approximately $30—an 85% reduction—with no perceived change in output quality because the hard tasks still get Opus.

The user notes that the subscription model deliberately obscures this inefficiency: no token breakdown, no per-task cost visibility, just a quota that mysteriously shrinks.

For teams or individuals paying for premium plans, routing via API can yield significant savings without sacrificing performance on the tasks that actually need top-tier models.