token count mismatch error provider bill differs from logs fails

Not specified by the original author.

TL;DR: Your request logs say 2k tokens but the bill says 9k. The gap is tokens you never see: hidden reasoning tokens, image tokens, and cache writes. Confirm the cause Check the usage breakdown on a real response: 1. On reasoning models, usage.outputtokensdetails.reasoning_tokens counts internal thinking: billed as output, never returned in the response.

The fix

TL;DR: Your request logs say 2k tokens but the bill says 9k. The gap is tokens you never see: hidden reasoning tokens, image tokens, and cache writes. Confirm the cause Check the usage breakdown on a real response: 1. On reasoning models, usage.outputtokensdetails.reasoning_tokens counts internal thinking: billed as output, never returned in the response.

The symptom

Billed tokens consistently exceed what your prompt plus visible response suggest. The usage object has fields your logging ignores.

Confirm the cause

Check the usage breakdown on a real response:

1. Hidden reasoning tokens. On reasoning models, usage.output_tokens_details.reasoning_tokens counts internal thinking: billed as output, never returned in the response. A "short" answer can carry thousands of reasoning tokens. This is the biggest surprise on o-series and GPT-5.
2. Image tokens. Vision inputs are tokenized by size and detail level and land in input tokens. A few high-detail images can outweigh a long text prompt.
3. Tool and schema tokens. Tool definitions and structured output schemas count as input tokens on every call.
4. Cache write tokens. On GPT-5.6 and later, prompt_tokens_details.cache_write_tokens reports prompt tokens written to cache, billed at 1.25x the uncached input rate. Cache writes are not free on newer models.
5. Retries and streams. Every retried request rebills its prompt tokens. Every retried stream rebills them too.

The fix

• Log the full usage object, not just prompt and completion totals. Break down reasoningtokens, cachedtokens, and cachewritetokens per call.
• Budget reasoning models with reasoning in mind: lower reasoning_effort when deep thinking is not needed, and size max_completion_tokens for reasoning plus visible output.
• Right-size image detail. low instead of high when the task allows it.
• Fix retry storms and loops first; they multiply every hidden cost above.

Verify the fix

Compare your logged token totals against the billed totals for a day. After the fix they should reconcile within a few percent. Any remaining gap has a named field in the usage object; find it before it finds your budget.

When to use this

• This covers exactly what the title says: OpenAI billed more tokens than your logs show.
• You are setting this up for the first time, or auditing an existing setup.
• You want the key gotchas in one place before you start.

When not to use this

• You are doing a different workflow with OpenAI; these steps are specific to the title above.
• You need the full reference docs; this is the short path, not the manual.

Compatibility

• Mentions 5.6 in the original; behavior may differ on much older or newer releases.

OpenAI's reasoning guide documents reasoningtokens under usage outputtokensdetails: internal reasoning billed as output but never returned. The prompt caching guide documents cachewrite_tokens on GPT-5.6 and later, billed at 1.25x the uncached input rate, and confirms images, tools, and schemas count as input tokens (https://platform.openai.com/docs/guides/reasoning, https://platform.openai.com/docs/guides/prompt-caching).

Not specified by the original author.

TL;DR

Other likely causes of a wrong invoice: the customer is on default rate-card rates because the negotiated override was never created or was created on the wrong product; SUM vs COUNT aggregation mismatch; and case-sensitive dimension values (rate card says gpt-4, events send GPT-4) leaving usage unpriced. Pass 10000 for $100.00.

Fix

1. Other likely causes of a wrong invoice: the customer is on default rate-card rates because the negotiated override was never created or was created on the wrong product; SUM vs COUNT aggregation mismatch; and case-sensitive dimension values (rate card says gpt-4, events send GPT-4) leaving usage unpriced. Expected: You get the expected result; the problem is gone.

When to use

• You are setting up or using this Metronome feature.
• The symptom matches: invoice is 100x too high - cents vs dollars.

When NOT to use

• Unrelated Metronome issues (different feature, different failure).
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against Metronome (mentions 1.00, 100.00). Source: https://github.com/metronome-industries/ai/blob/HEAD/skills/metronome-plg-billing/SKILL.md.

Variant phrasings

invoice is 100x too high - cents vs dollars

Why it happens

A Metronome invoice comes out 100x too high or 100x too low. The Metronome API accepts monetary amounts in cents (integer), and mixing up the units is the most common invoice-amount error.

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• Behavior can change between releases; the linked source reflects the versions above.
• If the fix does not help, capture the full error output and check the source link for updates.

Source

https://github.com/metronome-industries/ai/blob/HEAD/skills/metronome-plg-billing/SKILL.md

Source: A Metronome invoice comes out 100x too high or 100x too low. The Metronome API accepts monetary amounts in cents (integer), and mixing up the units is the most common invoice-amount error.

Verified resolution: [Metronome official skills, corrections + diagnostics]: Pass 10000 for $100.00. If you pass 100 meaning $100, the API treats it as $1.00 and the invoice comes out 100x low; the reverse produces 100x high. Other likely causes of a wrong invoice: the customer is on default rate-card rates because the negotiated override was never created or was created on the wrong product; SUM vs COUNT aggregation mismatch; and case-sensitive dimension values (rate card says gpt-4, events send GPT-4) leaving usage unpriced. For the units bug specifically, annotate every amount at the boundary.

Source URL: https://github.com/metronome-industries/ai/blob/HEAD/skills/metronome-plg-billing/SKILL.md

Not specified by the original author.

TL;DR

For budgets above 32k, use batch processing: long thinking runs hit network timeouts on live requests. Compare thinking\_tokens before and after the change on the same task.

Steps

1. Read usage.output_tokens_details.thinking_tokens on the response. That field reports how many of the billed output tokens were internal reasoning. The budget is a target, not a cap: actual usage varies, and max_tokens is the hard ceiling on total output. A 16k budget on a task the model could solve in 2k of thinking is pure overspend.
2. Start near the 1024-token minimum for simple tasks and raise incrementally; start around 16k only for genuinely complex ones.
3. On adaptive-thinking models, lower effort settings let the model skip thinking entirely on easy inputs.
4. For budgets above 32k, use batch processing: long thinking runs hit network timeouts on live requests.
5. Compare thinking_tokens before and after the change on the same task. Quality holding steady while thinking tokens drop is the win; if quality drops, you found the floor.

When to use

You are seeing this: Costs jump after enabling thinking, well beyond what the visible answer length would suggest. Use this skill when you run into "Anthropic bill is higher than expected with thinking on: reasoning tokens are billed as output tokens".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

Read usage.output\tokens\details.thinking\_tokens on the response.

Thinking tokens billed as output, the thinking_tokens usage field, the budget target-not-cap rule, and the 32k batch guidance are documented on the extended thinking page. Verified live at https://docs.anthropic.com/en/docs/build-with-claude/extended-thinking.