Cost optimization: tokens, caching, model selection
AI is metered · the operators who stay profitable measure what they spend and choose the model that fits the task.
::TL;DR · the whole lesson in three lines
- MOVEAI is metered · the operators who stay profitable measure what they spend and choose the model that fits the task.
- DRILLYou will audit your last month of AI spend, find the workflow eating the most, and run the same task on a cheaper model to feel where the quality line actually sits.
- WINYou know your top workflow by spend.
::concept · what's actually happening
AI usage is billed per token in and per token out, and the per-token prices vary by an order of magnitude across the model lineup. The cheapest models in a family cost ~5% of the most expensive · which means using the right model for the right task is not a rounding error, it is the entire margin.
read full concept · 4 more paragraphs →collapse concept ↑
The first cost lever is model selection · use Claude Haiku / GPT mini / Gemini Flash for the 80% of work that is summarization, classification, simple extraction, and conversational. Reserve Opus / GPT frontier / Gemini Pro for the hard reasoning, agentic, and creative work where capability genuinely matters.
The second lever is prompt caching · if you reuse the same long context across many calls (a codebase, a brand voice guide, a long doc you keep querying), caching cuts the input cost on cached portions to ~10% of normal. This is one of the largest free wins in the AI stack right now.
The third lever is request shape · batching where supported, async where you can wait, streaming when you want partial results faster. Each shapes the bill in different ways. Most operators leave money on the floor by sending one-by-one when the API offers batch endpoints at a discount.
The fourth lever is honest measurement · until you have a dashboard or a weekly export of your usage broken down by workflow, every cost discussion is vibes. Five minutes setting up usage tracking pays for itself the first month you see where your money actually goes.
::drill · do the thing
You will audit your last month of AI spend, find the workflow eating the most, and run the same task on a cheaper model to feel where the quality line actually sits.
::L44 drill · copy-paste into any AI chat
I want to audit and optimize my AI spend. Help me work through it: 1) walk me through how to pull my last month's usage from [WHICH PROVIDER · Anthropic / OpenAI / both / other], grouped by workflow if possible, 2) identify which one workflow is most likely eating my budget given my description: [BRIEFLY DESCRIBE YOUR USAGE · e.g. 'I run a 100-line prompt against Claude Sonnet maybe 30x per day for content review'], 3) for that workflow, recommend a cheaper model in the same family and predict where the quality might drop, 4) walk me through whether prompt caching applies to my pattern · if yes, the rough savings; if no, why not. End with three concrete actions I should take this week to cut my AI bill by 30%+ without dropping the work I actually need quality on.
::steps
- 01Pull your provider's billing or usage dashboard for the last month.
- 02Run the prompt with your real usage description.
- 03Take the biggest workflow and run a side-by-side comparison on a cheaper model.
- 04Honestly evaluate · is the quality drop acceptable? Often yes.
- 05If caching applies, enable it on your reused-long-context workflow.
- 06Set a calendar reminder to re-audit in 30 days.
::outcome · what should be true
- You know your top workflow by spend.
- You ran one workflow on both a frontier and a cheaper model and compared.
- You enabled at least one cost lever (model swap, caching, or batching).
- You set a recurring audit cadence rather than checking once and forgetting.
::trap · the most common failure
Operators run every task on the most expensive model out of habit · 'just in case I need the reasoning' · then watch their bill grow while 80% of the requests would have been fine on the cheap tier. Measure first. Switch on evidence.
::end of the curriculum
You're at Pilot level. There's no Level 6.
The next move is doing the work, not another lesson. If you want operator-grade infrastructure, that's /orangebox. If you want the lab's working journal, /founders-view. If you want to collaborate on the curriculum itself, the source is public on GitHub.
::other lessons at Operator level
Local AI · Ollama — privacy, offline, and the limit of free
At Operator level you need an honest opinion about local-only AI. Even if you don't use it daily, you should have run it once.
Model routing — switching between Claude, GPT, Gemini mid-task
Operators don't pick one AI. They route each task to the model that does it best. Knowing the strengths is the skill.
MCP servers — the plug socket that turned AI into a real tool
Model Context Protocol is the standard plug. Knowing what plugs in changes what your AI can actually touch — your files, your inbox, your calendar, your repos.
Agent mode — when AI takes action, not just answers
The frontier of useful AI is agents that DO things — browse, click, file, send. The actual skill is the safety pattern, not the magic.
Computer use — when AI takes the mouse and keyboard
Claude in Chrome, ChatGPT Atlas, computer-use beta — the frontier is AI that drives your browser like a human. Knowing the safety pattern is the actual skill.
What AI cannot replace — taste, judgment, relationships
The operators winning in 2026 are the ones who learned what AI is for and what is theirs. Knowing the line is more valuable than any prompt.
Agents 101: model plus tools plus loop
An agent is a model with tools running in a loop until done · know when you need one and when you don't.
MCP: structured tools for AI
Model Context Protocol is the USB-C of AI tooling · learn the shape before you wire anything.
Skill primers: teach a session your context in 30 seconds
A skill is a reusable file that primes a fresh AI session with your project, voice, and rules · stop re-explaining yourself.
Local models with Ollama
Run Llama, Qwen, or Mistral on your own laptop · no API, no logs, no monthly bill for the work that should stay home.
Vision models: when to use them
Vision lets the model see images · powerful for screenshots and diagrams · weak for precise spatial work · know the line.
Audio and Whisper transcription
Whisper turns audio into text · meetings, voice memos, interviews · the AI-era replacement for note-taking.
RAG vs long context: when to retrieve, when to dump
RAG fetches the right slice of your data at query time · long context stuffs everything in · know which problem you actually have.
Embeddings: meaning as numbers
An embedding is a list of numbers that captures the meaning of text · learn the shape and you unlock semantic search, deduplication, and clustering.
Fine-tuning vs prompt engineering
For individuals, fine-tuning is almost never worth it · know exactly when it actually is.
AI safety in personal use
PII, NDAs, financial data, and other people's secrets · know the rules of what you do not paste.
Multimodal prompting: combining text, image, audio
The strongest prompts use the medium that fits the question · sometimes you describe, sometimes you show, sometimes you do both.
Chain-of-thought: making the model show its work
Asking the model to reason step-by-step before answering raises accuracy on hard problems · know when it earns its cost.
Tool use and structured output
Function calling makes the model return JSON your code can use · know the contract before you build on it.
::part of the AtomEons /learn curriculum · 45 lessons · 5 levels · cc-by 4.0