If you're using an AI API platform, you've probably stared at a pricing page wondering: do I really need the expensive model for this?
Picking the wrong tier either wastes money (using a reasoning model for a quick lookup) or wastes time (using a lightweight model for a complex task and getting garbage output).
Most multi-tier platforms — including our own workspace Mycel — follow the same three-tier pattern, so this guide applies broadly. Here's how I think about it.
The Three Tiers
- flash — lightweight and fast. Built for quick Q&A, simple instructions, and basic lookups. Cheapest per call.
- turbo — the balanced tier. Good quality with reasonable latency. Handles mid-complexity tasks: longer text polishing, code snippet generation, multi-turn conversations.
- plus — deep reasoning tier. Uses significantly more compute. For complex logic, domain analysis, and long-document processing.
A Simple Decision Table
| Your task | Pick | Why |
|---|---|---|
| Daily Q&A, simple commands, fact lookups | flash | Fastest, lowest cost |
| Text polishing, code generation, multi-turn chat | turbo | Quality/cost balance |
| Complex reasoning, professional analysis, long docs | plus | Much stronger comprehension and generation |
Do the Math
Take a typical token-credit platform (1 unit ≈ 100 credits, like Mycel's system):
-
flash: 1 credit/call → about $0.0014/call -
turbo: 2 credits/call → about $0.0028/call -
plus: 5 credits/call → about $0.007/call
Now imagine 200 calls a day:
- All on
plus: 1,000 credits/day - Right-tier routing (say 70% flash, 25% turbo, 5% plus): ~185 credits/day
That's an 80% cost reduction just by not lazily defaulting to the biggest model. No code changes. No infra work. Just routing discipline.
Practical Rules of Thumb
- Default to flash. Only escalate when the output isn't good enough.
- Escalate on failure, not on fear. If flash returns fine for your summarization task, you didn't need turbo.
- Reserve plus for actual reasoning: multi-step analysis, nuanced tradeoffs, or documents over ~50 pages.
- If you bring your own API key (BYOK), many platforms only charge a small channel fee — worth checking before you commit to their bundled models.
One Caveat
Tiers change as models get updated. Whatever platform you use, check the live docs before building a cost model on top of my numbers — treat the pattern (light/balanced/deep) as stable, not the exact prices.
If you're curious what this looks like in practice, Mycel (where I work) runs exactly this three-tier model with per-call pricing. But the tier-routing logic above works on any platform with a similar setup.
Top comments (0)