About ClaudeHow

Independence

ClaudeHow is an independent resource. It is not affiliated with, endorsed by, or sponsored by Anthropic. "Claude" and "Anthropic" are trademarks of Anthropic PBC, used on this site only descriptively, to say what the site is about. Nowhere on this site does the design, the name, or the copy imply that this is an official Anthropic property, and no Anthropic logo or wordmark appears anywhere here. If anything on this site reads as though it speaks for Anthropic, that is a mistake and we want to hear about it — see contact.

Why this site exists

Anthropic's documentation explains what the API does. It does not — and has no reason to — tell you whether your specific usage pattern is cheaper on a subscription or metered, which model fits your task, or what a month of your actual traffic will cost. Those are the questions a working developer types into a search bar at 11pm, and nobody selling the product is incentivised to answer them precisely. This site's tools take your real numbers as input and compute an answer instead of asserting one.

Accuracy

Every price, context window, cache minimum, effort level and platform-availability fact published on this site lives in one module (src/data/facts/), and every entry in it carries a verification date and a named source. Pages render from that module directly — nothing is typed by hand into prose, so a fact can never quietly drift out of sync between where it's stated and where it's used. A script fails this site's own production build when any fact is older than 45 days, which means the site cannot silently go stale the way most reference content does.

Two things follow from that discipline that are worth stating plainly. First, we do not invent numbers. Where a figure could not be confirmed against a source we treat as authoritative, the relevant page says so directly — "we could not confirm X" — rather than publishing a plausible estimate. On a site about API pricing, a confidently wrong number is worse than an honest gap, and we have chosen the gap every time that trade-off has come up. Second, this site never publishes a subscription plan price. Consumer plan pricing is not published anywhere we treat as authoritative, and it varies by region, currency, tax treatment and billing period besides. The subscription-vs-API calculator asks what you actually pay each month and computes from there, which is correct for every reader regardless of plan, region or future price change — a fixed number we typed in six months ago would not be.

Maintenance

This site's subject changes under it. New model generations retire old ones, cache minimums shift generation to generation, and pricing changes on a schedule Anthropic sets, not us. We re-verify every fact in the module on a weekly cadence and re-run the freshness gate before any change ships. If that maintenance ever stops, the honest thing to do is take the site down rather than let a developer-tools resource quietly rot into a source of wrong numbers — so that is what will happen.

Corrections

Found a wrong figure, a broken calculator, or a model ID that's changed since we last checked? Contact us — corrections to a cost-reference site are exactly the kind of feedback we want, and we read every message ourselves.