Curriculum

Cluster 6 ¡ Lesson 2 1 min read

Reading Token Usage

Understanding costs per node and per flow, and optimizing for budget.

Understanding the cost of AI is not an accounting exercise; it is a fundamental design constraint. When you build workflows, you are making decisions about resource allocation. Tokens—the fragments of words that models read and generate—are the currency of this ecosystem. If you do not understand how they are counted and billed, you cannot design efficient systems. You will either overspend on simple tasks or under-resource complex ones.

This lesson strips away the abstraction of "AI usage" and grounds it in practical economics. We will examine the difference between input and output costs, how to track expenditure across individual nodes and entire flows, and the strategies you can use to optimize your budget. The goal is not to minimize spending at all costs, but to spend deliberately. Experimentation has a price, but stagnation costs more.

Assignment

Review one of your existing flows or prompts. Calculate the approximate token count for the input. Then, rewrite the prompt to reduce its length by at least 20% without losing its core instruction. Test both versions and compare the results and estimated costs.

Learning Objectives

  • Understand the concept of tokens and how they translate to costs.
  • Differentiate between input and output tokens and their respective pricing.
  • Apply optimization strategies to manage budget without sacrificing necessary quality.

Tokens

The fundamental unit of data processed by language models, roughly equivalent to four characters or three-quarters of a word in English.

Input vs. Output Costs

The distinction in pricing between the text you send to a model (input) and the text the model generates (output), with output typically costing more.

The binding constraint on AI adoption is not technical skill, but the ability to see your own work clearly enough to redesign it.