Technischer Leitfaden

Tokenzählung und LLM-API-Preisgestaltung

LLM APIs charge per token, a chunk of text that is roughly three-quarters of an English word.

Hören Sie sich diesen Leitfaden anKI-erzählt · ~3 min

Auf dieser Seite4 Minuten gelesen
  1. Übersicht
  2. Tiefer Einblick
  3. Reale Umsetzung
  4. The Future of Token Counting and LLM API Pricing
  5. In die Tat umsetzen
  6. Entdecken Sie weiter
  7. Häufig gestellte Fragen

Übersicht

Input tokens you send and output tokens the model generates have separate rates, and output usually costs several times more. To estimate cost, count tokens with the provider's tokenizer or counting endpoint and multiply each side by its per-million rate. Include hidden tokens such as system prompts, conversation history and reasoning.

Tiefer Einblick

Models do not read characters or words directly. A tokenizer splits text into tokens, which are common character sequences learned from training data. A common rule of thumb for English is about four characters, or three-quarters of a word, per token. That puts 1,000 words at roughly 1,300 to 1,400 tokens. Code, numbers, unusual names and many non-English languages use more tokens per word. Each model family has its own tokenizer, so the same text can produce different counts with different providers. Prices are usually quoted per million tokens, with separate input and output rates. Output tokens cost more because the model generates them one at a time, while it can process input tokens in parallel. Output is commonly priced at several times the input rate, often somewhere between four and eight times, though ratios vary by model. Here is a worked example with made-up prices: input at $3 per million tokens and output at $15 per million. A task sends 6,000 input tokens (system prompt, instructions and a document) and gets back 800 output tokens. - Input: 6,000 x $3 / 1,000,000 = $0.018 - Output: 800 x $15 / 1,000,000 = $0.012 - Total: $0.03 per task At 10,000 tasks a day, that comes to about $300 a day. Real bills often surprise people, for predictable reasons: - Chat applications resend the whole conversation on every turn, so input grows with each message. - Reasoning models generate internal thinking tokens that are billed as output, even when they are not shown in full. - Tool definitions, retrieved documents and images all count as input. - Retries and failed calls cost money too. Three misconceptions are common: that tokens equal words, that filling a model's context window is free, and that the model with the lowest per-token price is always cheapest per task. A stronger model that finishes in fewer attempts can cost less overall.

Reale Umsetzung

A developer uses OpenAI's open-source tiktoken library to count a 3,000-word support article before sending it. It comes to roughly 4,000 tokens, and she sets a budget alert to match.

A chatbot team finds that most of its bill comes from resending a 2,000-token system prompt and the full chat history on every turn. It cuts costs by summarizing older turns and using prompt caching.

A company processing 50,000 product descriptions overnight moves the job to a provider's batch API. The batch API charges less, and in return results arrive within hours instead of seconds.

A team translating content into Hindi and Japanese budgets more per page than for English. With common tokenizers, the same meaning often takes more tokens in those languages.

The Future of Token Counting and LLM API Pricing

Per-token prices for a given level of capability have fallen substantially over the past few years. Total spending often rises anyway, because applications use longer contexts, agents make many calls and reasoning models produce more output. Pricing is also getting more varied, with separate rates for cached input, long-context requests, batch jobs and reasoning. That makes it more important to measure actual usage per task than to compare headline prices. Cost tools such as budgets, per-feature cost tracking and automatic model routing are likely to become standard parts of LLM applications.

In die Tat umsetzen

Warum es wichtig ist

  • Kosten und Budget. Architekturentscheidungen beeinflussen über Jahre hinweg die Leistung und die Betriebskosten.
  • Klarere Entscheidungen. Technische Schulungen helfen Teams dabei, den richtigen Stack auszuwählen, nicht nur den neuesten.
  • Qualitätskontrolle. Bessere technische Entscheidungen reduzieren Zuverlässigkeitsvorfälle in der Produktion.

Achten Sie auf

  • Die Optimierung eines Benchmarks kann umfassendere Systemschwächen verbergen.
  • Infrastruktur- und Wartungskosten werden oft unterschätzt.
  • Sicherheits- und Beobachtbarkeitslücken können größer werden, wenn die Systeme komplexer werden.

Nächste Schritte

  1. Definieren Sie vor der Implementierung Latenz-, Qualitäts- und Kostenziele.
  2. Benchmark unter realistischen Last- und Datenbedingungen.
  3. Instrumentenüberwachung auf Fehler, Drift und Benutzereinflüsse.
  4. Bereiten Sie vor der Skalierung Rollback- und Incident-Response-Pfade vor.

Entdecken Sie weiter

Kostenloser Newsletter

Erhalten Sie die tägliche KI-Briefing

Drei verifizierte KI-Geschichten jeden Werktagmorgen, in einfachem Englisch geschrieben. Für immer kostenlos, keine Werbung.

Eine E‑Mail jeden Werktag. Abmelden mit einem Klick. Wir verkaufen oder teilen Ihre Adresse nie.

Testen Sie sich selbst

Take the Token Counting and LLM API Pricing quiz

Sofortiges Feedback zu jeder Antwort und ein teilbares Zertifikat mit verifizierbarer ID, sobald Sie einen Kurs bestanden haben.

Quiz starten

Unterstützen Sie kostenlose KI-Bildung. AI Understanding ist eine 501(c)(3) gemeinnützige Organisation – keine Werbung, keine Paywall, nie. Machen Sie eine Spende

Häufig gestellte Fragen

What is Token Counting and LLM API Pricing?

LLM APIs charge per token, a chunk of text that is roughly three-quarters of an English word. Input tokens you send and output tokens the model generates have separate rates, and output usually costs several times more. To estimate cost, count tokens with the provider's tokenizer or counting endpoint and multiply each side by its per-million rate. Include hidden tokens such as system prompts, conversation history and reasoning.

Was ist eine gängige Daumenregel für englischen Text und Token?

English averages about four characters or 0.75 words per token, so 1,000 words is roughly 1,300 to 1,400 tokens.

Warum sind Output-Token normalerweise teurer als Input-Token?

Generating tokens one by one takes more compute time than processing input tokens in parallel.

Was kostet ein Aufruf mit 6.000 Input- und 800 Output-Token bei künstlichen Preisen von 3 $ pro Million Input-Token und 15 $ pro Million Output-Token?

6,000 x 3 / 1,000,000 = $0.018 and 800 x 15 / 1,000,000 = $0.012, which adds up to $0.03.

Warum steigen die Kosten für Chatbots oft im Laufe einer Unterhaltung?

Each new message usually includes all the earlier turns, so input tokens pile up unless history is trimmed or summarized.

Wie werden die internen Denk-Token eines Reasoning-Modells typischerweise abgerechnet?

Thinking tokens are generated by the model, so they are billed as output even if you do not see all of them.