Tokencost does not invent historical pricing changes. This changelog lists only verified updates made to the central pricing data file and explains why the change matters for calculators.
| Date | Change | Source | Affected pages |
|---|
| 2026-07-30 | Refreshed source-backed LLM pricing dataset from simonw/llm-prices and added official Kimi K3, K2.7 Code and K2.6 CNY rows from the Kimi platform. | Sources policy | Pricing research pages, comparison table and calculator fallback data |
What changed in the latest sync
The latest automated report checked 11 source files and normalized 122 model rows. Not every discovered model becomes a featured public recommendation; the research pages emphasize representative rows with visible source, currency and caveats.
When a new flagship model appears, the daily sync can refresh the dataset and rebuild the site content. The workflow is scheduled for 06:00 Malaysia time so overnight provider changes can be reviewed early in the day. If a provider changes a pricing page but the community dataset has not reflected it yet, the correction can be sent manually to hello@tokencost.live.
Why this page matters
Pricing pages can become stale quickly. A visible changelog helps users understand whether a calculator result came from current source-backed data or from an older manual assumption. It also gives AdSense and search crawlers a clearer signal that Tokencost maintains the publication rather than leaving thin calculator pages untouched.
Related calculators and research
Why this pricing updates page exists
Tokencost is built for people who need to make a practical money decision before they have perfect data. A developer might be deciding whether a chatbot can fit inside a $19/month subscription. A creator might be checking whether a short-video workflow can survive the cost of regenerated clips, voiceovers and music. A small SaaS team might need to know whether an AI feature should be free, metered, routed to a cheaper model or limited behind a paid plan.
Those decisions are difficult because AI pricing is fragmented. LLMs bill input, output and sometimes cached input. Video and music tools may use subscriptions, credits, region-specific plans or private enterprise rates. Voice tools may charge by characters, minutes or seats. Some providers publish clear API rates while others hide the practical unit cost behind plan limits. Tokencost keeps calculators flexible by allowing manual input when verified pricing is not available.
What makes a useful estimate
A useful estimate includes the whole workflow. For LLM products, that means request count, prompt size, output size, retries, cache ratio, hidden reasoning or agent loops and monthly active use. For creator workflows, it means finished output, rejected attempts, editing tools, revenue assumptions and break-even views. For SaaS businesses, it means revenue, payment fees, infrastructure, marketing, team cost and churn. A single provider price rarely answers the real business question.
How to read Tokencost pages
Use every result as a planning range. The calculators show how cost moves when assumptions change, while the research pages explain why those assumptions matter. The sources and methodology pages show where factual pricing came from and where users should verify. If a provider publishes a newer source, the site can be corrected through the contact email. This structure is intentionally conservative because publishing a transparent caveat is more valuable than showing a precise-looking but unverifiable number.
Editorial promise
Tokencost avoids copyrighted logos, keeps ads separate from calculator logic, removes thin duplicate pages from the sitemap and keeps legal/trust pages accessible without login. The goal is to be a durable reference for AI pricing, token cost calculation, creator cost planning and AI SaaS economics, not a temporary collection of search-keyword pages.
Related calculators and research