Background
Methodology

Where the numbers come from.

TokenScale checks prices against provider sources every night. This page explains what each check reproduced, what had to be carried forward, and how those two states stay distinct in the historical record.

The short version

What "verified" means

Verified means a human-readable price was reproduced from the provider's official source for that observation and matched against what TokenScale shows. It does not mean copied from a third-party aggregator or estimated. When a check cannot complete, that observation is carried forward from the last verified price, drawn in grey and kept grey permanently. When two official sources disagree, the conflict is recorded rather than resolved by silently picking one.

A grey day stays grey. This page used to say that once the next verification landed, grey days turned solid. That sentence contradicted the append-only rule above it, and on 4 August 2026 we removed it and fixed the record to match. A successful check on Tuesday confirms Tuesday; it cannot reach back and confirm a Monday we missed, because between the two a price could have moved and moved back without us seeing it. So carried-forward days are now flagged permanently in the data and drawn grey forever. The gap is part of the record. Every missed night, with the reason, is listed on the reliability page.

How a price gets on the page

Provider source
The authority for the provider's current published pricing, per million tokens, input and output.
→
Nightly check
Each source is checked and dated. A successful observation is verified; one that cannot be reproduced is carried forward and shown grey.
→
History
That night's datapoint is appended to the record. Nothing is rewritten.
→
Live site
The site is rebuilt and versioned. BUILD.txt says which build is live.

Words to tokens

TokenScale expresses sizes in content you recognise. The word counts behind the landmarks are real: The Hobbit is 95,356 words, verified against the Project Gutenberg text. Tokens are estimated from words at roughly 1.33 tokens per word, the ratio that holds for typical English prose. Different tokenizers vary a little either side of that; the price differences between providers are far larger than the tokenizer differences.

Promotions and intro pricing

Limited-time promotional rates are shown as an overlay on the live price, clearly labelled. They never enter the price history, so the historical record reflects standard published rates only.

Time-window pricing

Some providers publish different standard on-demand prices at different times of day. TokenScale records the highest published standard rate as the comparison figure, labels it as a peak rate and shows the exact lower schedule beside it. This gives a conservative planning number without pretending the peak applies all day. We do not average the windows because a provider has not published that average and each customer's traffic pattern is different.

For DeepSeek, peak hours are 01:00–04:00 and 06:00–10:00 UTC, Monday through Friday. Weekends and all other hours are off-peak and cost 50% less.

When we get it wrong

Corrections are published, not buried. The first one set the tone: on launch week the headline figure said writing The Hobbit cost $0.04, which was the input cost only. The correct total was $0.06. The fix, and why it happened, went straight into the changelog. That distinction between input and output pricing is exactly what this site exists to make visible.

If a number here doesn't match the provider's page, we want to know within the day.

Spotted an error? Use the "Report a pricing error" link in the calculator's footer, or email projectsbilton@gmail.com. Confirmed same-model corrections are applied and logged; anything ambiguous is flagged on the site rather than guessed at.

Check it yourself

Last updated: 27 August 2026. If the process changes, this page changes with it.

← Back to TokenScale

© 2026 Bilton Projects · built in public TokenScale · Privacy · Journal