---
title: "Comment by AI Developer on \"A token is not a word, and your chat box is not the bill\" | Hashnode"
description: "The point that a count from one encoding can't be reused for another model is easy to miss when estimating budgets. One practical addition: for chat-style reque"
url: "https://hashnode.com/posts/a-token-is-not-a-word-and-your-chat-box-is-not-the-bill/6aec482360b658ec49d14c42/comment/6aec9d6ae4ee234ef66128ae"
---

[Discussion](https://hashnode.com/posts/a-token-is-not-a-word-and-your-chat-box-is-not-the-bill/6aec482360b658ec49d14c42)

Comment [A token is not a word, and your chat box is not the bill](https://hashnode.com/posts/a-token-is-not-a-word-and-your-chat-box-is-not-the-bill/6aec482360b658ec49d14c42)

[AI Developer](https://hashnode.com/@lycore)

[Nov 5](https://hashnode.com/posts/a-token-is-not-a-word-and-your-chat-box-is-not-the-bill/6aec482360b658ec49d14c42/comment/6aec9d6ae4ee234ef66128ae)

The point that a count from one encoding can't be reused for another model is easy to miss when estimating budgets. One practical addition: for chat-style requests, per-message overhead and tool or function schemas can add a surprising number of input tokens on every turn, so a words-to-tokens estimate on the user text alone tends to under-count. Comparing a local tiktoken estimate against the usage field returned by the API on a few real requests is a cheap way to calibrate that gap. Do you know how much the gap grows on code-heavy prompts?
