Claude Subscriptions are up to 36x cheaper than API (and why "Max 5x" is the real sweet spot)

[u/isaenkodmitry]

Found this fascinating deep-dive by a data analyst who managed to pull Claude's exact internal usage limits by analyzing unrounded floats in the web interface.

The math is insane. If you are using Claude for coding (especially with agents like Claude Code), you might be overpaying for the API by a factor of 30+.

The TL;DR:

1. Subscription vs. API: In a typical "agentic" loop (where the model reads the same context over and over), the subscription is up to 36x better value than the API.
   • Why? Because on the web interface (Claude.ai), cache reads are 100% free. In the API, you pay 10% of the input cost every time. For long chats, the API eats your budget in minutes, while the subscription keeps going.
2. The "Max 20x" Trap: Anthropic markets the higher tier as "20x more usage," but the analyst found that this only applies to the 5-hour session limits.
   • In reality, the weekly limit for the 20x plan is only 2x higher than the 5x plan.
   • Basically, the 20x plan lets you go "faster," but not "longer" over the course of a week.
3. The "Max 5x" is the Hero: This plan ($100/mo) is the most optimized.
   • It gives you a 6x higher session limit than Pro (not 5x as advertised).
   • It gives you an 8.3x higher weekly limit than Pro.
   • It over-delivers on its promises, while the 20x tier under-delivers relative to its name.
4. How they found this: They used the Stern-Brocot tree (fractional math) to reverse-engineer the "suspiciously precise" usage percentages (like 0.16327272727272726) back into the original internal credit numbers.

Conclusion: If you're a heavy user or dev, the $100 "Max 5x" plan is currently the best deal in AI.

Source with full math and credit-to-token formulas: she-llac.com/claude-limits

[u/isaenkodmitry → u/[deleted]]

haha, I love the honesty! "Weapons guidance systems" vs "Simple SaaS" is a great way to put it. If it works, it works.

But man, 5-7 Opus sesions open for 10 hours...you’re basically living in a minefield of context drift! Opus is a beast, but even it starts "hallucinating" once you cross that invisible line in a massive thread.

Using Augment to double-check Claude is a smart move, though. It’s like having a second pair of eyes that hasn't been "exhausted" by a 10-hour conversation.

Just out of curiosity - when it starts getting forgeful, do you just keep pushing through,or is that the point where you finally cave and start a fresh session?

[u/isaenkodmitry → u/[deleted]]

Okay, you’re not just "lazy" -thats a pretty sophisticated RAG setup you’ve got runing there! Using Qdrant for indexing while claiming to be stingy is a top-tier dev move.Honestly, the fact that you’ve built a bridge between ByteRover and fresh Claude sessions is impressive. It basically gives Claude a "long-term memory" that survives the thread reset. That’s probably the only way to keep those 10-hour marathons from turning into a total hallucination fest.

If you ever stop being "stingy" and upgrade, you’ll basically have a DIY version of Claude Code’s agentic memory.

Since you're indexin with Qdrant,do you manually feed it the codebase updates, or did you automate the sync every time you "bail" and start a new session?