Most solo operators treat AI assistant pricing like a flat monthly subscription. You pay $20, you get unlimited ChatGPT Plus. Simple.
But the moment you move to API access—Claude, GPT-4, Gemini, or any other model billed per token—the math changes completely. You’re no longer paying for access. You’re paying for every word you send and every word the model returns.
If you’re building AI workflows, automating content generation, or running prompts at scale, understanding token pricing is the difference between a $15/month tool cost and a $400 surprise bill.
How token pricing actually works
Tokens aren’t words. They’re chunks of text—usually 3–4 characters, depending on the model’s tokenizer. The phrase “newsletter operators” is three tokens. A 500-word article might consume 650–750 tokens, depending on punctuation and structure.
Every API call bills you twice: once for input tokens (your prompt and any context you include), and once for output tokens (the model’s response). Input is almost always cheaper—sometimes 10× cheaper—than output.
As of October 2026, here’s what you’re paying per million tokens on the most common models:
- GPT-4o: $2.50 input / $10.00 output
- Claude 3.5 Sonnet: $3.00 input / $15.00 output
- GPT-4o mini: $0.15 input / $0.60 output
- Gemini 1.5 Flash: $0.075 input / $0.30 output
If you’re generating a 1,000-token article with a 200-token prompt using GPT-4o, that’s $0.005 for input and $0.01 for output—about 1.5 cents per article. Run that 1,000 times a month and you’re at $15. Add debugging, retries, and context bloat, and you’re closer to $40.
Where costs spike: context and retries
Token costs compound fast when you’re including context. If you’re feeding the model your brand voice guide, three example posts, and a style sheet every time you generate a headline, you might be sending 2,000+ tokens of input for a 50-token output.
That’s $0.005 in input and $0.0005 in output per request. The input is now 10× the cost of the result.
Retries make it worse. Most automation tools—Zapier, Make, n8n—will re-run a failed API call at least once. If your prompt is malformed or the model times out, you’ve just doubled your token spend for zero usable output.
The fix: strip unnecessary context. If you’re generating subject lines, you don’t need to include your entire content strategy doc. Summarize it into 100 tokens or cache it using the model’s context-caching feature (available in Claude and some OpenAI endpoints). Caching input tokens costs about 90% less on repeat calls.
Choosing the right model for the job
You don’t need GPT-4o or Claude 3.5 Sonnet for every task. If you’re summarizing reader replies, reformatting CSVs, or generating meta descriptions, a mini model works fine—and costs 10–20× less.
Here’s a rough decision tree:
- Use a flagship model (GPT-4o, Claude 3.5 Sonnet) for: long-form content generation, nuanced editing, complex reasoning, brand-voice matching.
- Use a mini/flash model for: summarization, reformatting, extracting structured data, generating simple variants (subject lines, CTAs).
- Use a local or open model (via Ollama, LM Studio) for: high-volume tasks where latency doesn’t matter and you want zero per-token cost.
If you’re running 10,000+ requests a month, split your workload. Route simple tasks to Gemini Flash or GPT-4o mini, and reserve the expensive models for work that actually needs them.
Track spend before it surprises you
Every major AI provider offers usage dashboards. Set a monthly spending cap in OpenAI’s settings or Anthropic’s console. Most platforms let you set a hard limit—$50, $100, whatever fits your budget—and they’ll stop processing requests once you hit it.
If you’re running prompts through Zapier or Make, add a step that logs token counts to a Google Sheet or Airtable. You’ll see exactly which automations are burning tokens and where to optimize.
One operator I know was spending $80/month on Claude API calls to generate social posts. After logging token usage, he realized 60% of the cost came from a 1,200-token brand-voice primer he was sending with every request. He cached it, cut his bill to $28, and the output quality didn’t change.
Want more breakdowns like this? Subscribe to One Two Three Send—we cover the tools, pricing, and workflows that actually matter for solo operators.
Heads up — some links in this article are affiliate links. If you sign up through them, we may earn a small commission at no extra cost to you. We only recommend tools we use ourselves.