ClaudeHow
What should I use, and what will it cost? — practical answers for building on Claude.
Every calculator computes from your real usage, not a vendor's example. Every fact renders from a dated, sourced module — never typed by hand into a page.
Eight tools, computed from your numbers
Subscription vs API cost calculator
Model your actual Claude usage both ways — flat subscription and metered API — and see the break-even point, not a vendor's marketing comparison.
Token & cost estimator
Paste text to see its real Claude token count and cost across every current model — and why a tiktoken-based estimate undercounts it.
Prompt-caching savings calculator
Enter your prefix size and request pattern to see whether the 5-minute or 1-hour cache TTL wins, and what it saves per month.
Model picker
Task shape, budget ceiling, latency tolerance and context size in — a recommended model and effort level out, with the reasoning shown.
Context-window planner
See how much of a 1M-token window your codebase or document set consumes, what's left for output, and where compaction starts paying for itself.
Usage tracker
Log your own usage or paste API usage blocks to see burn rate, projected month-end spend and a cache-hit-ratio read. Nothing leaves your browser.
Batch vs realtime calculator
The Batch API runs at half the standard price with a turnaround measured in hours. Given your volume and deadline, is batching worth it?
Effort & thinking cost estimator
Effort runs low through max and is the main lever on both spend and quality. See the cost curve and where each level is the right call.
What should I use, and what will it cost?
Anthropic's own documentation is thorough about what the API does. It is deliberately silent on the question every working developer actually has: given how I use Claude, should I be on a flat subscription or metered API, which model, and what will next month's bill look like? No vendor publishes that comparison, because the honest answer is "it depends on your usage" and a vendor has no incentive to build you a calculator that might recommend a cheaper plan.
ClaudeHow exists to answer that question with your numbers, not a marketing example. Every tool here takes your actual usage as input — messages per day, typical prompt and output length, how much context you re-send, your request pattern — and computes an answer instead of asserting one.
Why the numbers can be trusted
Every price, context window, cache minimum and effort level published on this site comes from a single facts module with a recorded verification date and source, never from prose typed by hand. A script fails this site's own build if any figure goes stale, so a page here cannot quietly drift out of date the way a blog post or a cached search result can — and where the underlying source doesn't fully answer a question, this site says so on the page rather than filling the gap with a guess. See the about page for the full detail behind that discipline.
What you will not find here
No subscription plan price appears anywhere on this site — see why this site never publishes a subscription price for the full reasoning. The subscription-vs-API calculator asks what you actually pay instead and computes from there, which stays correct regardless of your plan, region or how pricing changes after this was published. You also will not find a restatement of Anthropic's own docs: every page here computes something, compares something measurable, or catalogues a specific mistake with the one-line fix, because a page that repeats the documentation earns nothing a reader couldn't get faster from the source.
Start with the calculator that started this site
The subscription vs API cost calculator models your actual workload both ways and names the break-even point in plain language. If you only use one tool on this site, that is the one worth your time.