this post was submitted on 24 May 2026
316 points (96.7% liked)
Technology
84881 readers
4817 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
My understanding is that tokens are basically words, and that when you ask a question it charges for all the tokens it consumes, produces, or processes. There's a lot of internal processing for each request, where the input text is summarized in different ways and combined with previous parts of the conversation, so it's not as straightforward as "word count of what you say plus what it says".
Worth noting that a token is not necessarily a word, though can be. One word could also take multiple tokens. It can also vary from LLM to LLM and their tokenization methods.
In other words obfuscation so they can charge whatever they want using some obscure formula that only they know.
Not really, there are ways to count tokens before running an inference. Some providers make tokenizers public, so they even work offline. APIs also usually return rolling costs per response and have budget limits - though some could have more fine-grained limits.
Users who are surprised by the bill are usually not paying attention to each call, or using autonomous subagents, or a setup where they have little or no control to what is sent to the provider.
So the problem isn't really the API provider, as much as it's the tooling around it, which makes it too easy to overspend.