Because context pricing stopped being linear this year, and the habit everyone taught you, which is paste in everything and let the model sort it out, now has a price tag attached to it.
Here are two numbers that should annoy you.
Sixty-four cents. One dollar and twenty-four cents.
Same task. Same model. Same output length. The only difference is three thousand extra tokens of input, which is roughly four pages of text you probably did not need to include.
The direct answer to the headline question is this. Your bill went up because somewhere in the last year the pricing model for long inputs changed shape, and almost nobody sent a memo. OpenAI's GPT-6.1 Sol advertises a context window of roughly 1,050,000 tokens. But cross 272,000 input tokens on a single request and you pay double the input and cache rate plus 1.5 times the output rate on the entire request, not just the part above the line.
So a job at 270,000 tokens runs about 64 cents. The identical job at 273,000 tokens runs about $1.24.
That is a cliff, not a slope. And if you run anything at volume, you are standing near it right now without knowing where it is.
Key Takeaways
- Context window pricing is no longer linear, and crossing a threshold can reprice an entire request rather than just the portion above the line.
- The pattern repeats across vendors, with expanded context windows shipping while rate cards stay where they were.
- Most of what people paste into a prompt is not influencing the output, which means it is cost without benefit.
- A short, well-built brief usually outperforms a long document dump on both cost and quality, because burying instructions in bulk is how instructions get ignored.
- Open-weight releases signaled for this month will likely move the cost floor again, which rewards anyone who has already done this cleanup.
The Problem: An Expensive Habit Nobody Called Out
Let me describe the habit, because I had it too.
You have a long document. Brand guidelines, a transcript, a contract, a spreadsheet export, six months of notes. You need AI to do something with it. So you paste the whole thing in, because why not, the context window is enormous now, and the model is good at finding what it needs.
That advice was correct for about two years. Context was cheap, windows were growing, and the cost of being thorough was close to zero.
It is not correct anymore, and the change happened quietly.
Here is what I mean by quietly. Nobody sends an email saying your habits are now expensive. The vendor ships a bigger context window and markets it as a capability upgrade, which it genuinely is. The pricing detail sits in documentation you were never going to read. And your bill drifts upward while your usage, from your point of view, has not changed at all.
Candidly, this is my least favorite kind of problem. Not because anyone is being deceptive, but because the information you need to make a good decision is technically available and practically invisible.
And there is a second cost, which nobody talks about and which I think is actually the larger one.
Long prompts make worse output.
When you paste forty pages into a prompt and bury your actual instruction somewhere in the middle, the model's attention is divided across all of it. Then you get an output that ignores your third requirement and you blame the model.
That was not a model failure. That was you hiding the instruction.
So the expensive habit is costing you twice. Once on the invoice and once on the quality.
But what if the discipline that fixes the bill is the same discipline that fixes the output?
The Evidence: What Is Actually Happening To Pricing
Let me put real data behind this.
Data point one. GPT-6.1 Sol has a 1,050,000 token context window. Prompts above 272,000 input tokens incur double the input and cache rates plus 1.5 times the output rate for the full request. At 270,000 input tokens with 10,000 output tokens held constant and no caching, the cost is approximately $0.64. At 273,000 input tokens, the same configuration costs approximately $1.242. That is a 94 percent cost increase for a 1.1 percent increase in input.
Data point two, and this is the one that shows it is a pattern rather than a quirk. On October 1, a provider called Unbiased released Pareto 26.10 Preview, expanding its context window from 262,144 tokens to 1,048,576 tokens. The routed price decreased. But on Unbiased's own platform the rate card did not move, and customers were still charged the original $2.50 per million input and $7.50 per million output for the preview model.
Bigger window, same bill. Two different vendors, same shape of story.
Data point three. Over on r/LocalLLaMA, discussions from late September show practitioners working to extend local models like Qwen3.8 27B past 262,144 tokens of context. That effort tells you something. The people running models on their own hardware are grinding on context limits specifically because context is where both the capability and the cost concentrate.
Data point four. Several open-weight labs have October releases signaled: DeepSeek with v4.1-pro, Qwen with Qwen4, Moonshot with Kimi K3.x, MiniMax with M3-a and M3.1-flash-preview, and Zhipu with GLM 5.4 and 5.5. Kimi reopened subscriptions on September 18 with its next model reportedly in post-training. Historically each of these waves has pushed the cost floor down.
That matters for timing. A business that has already cut its input bulk in half benefits twice when the floor drops. A business that has not just pays less for the same waste.
Data point five, for scale. Goldman Sachs found 76 percent of small businesses report using AI while only 14 percent say it is fully embedded in core operations. The 14 percent are the ones running volume. If you are in that group, a habit that nearly doubles the cost of a frequent task is not a rounding error. It is a margin decision you have been making by accident.
So the conventional story, which is that AI keeps getting cheaper, is true in the aggregate and misleading in the particular. Per-token prices keep falling. Per-task costs are rising for anyone whose inputs are growing faster than prices are dropping.
The Shift: Decide What The Model Does Not Need To See
Here is the reframe, and it is the whole post in one line.
Everyone is learning to write better instructions. Almost nobody is learning what to leave out. That gap is where your margin is sitting.
Let me frame this as a system, because that is how it actually works.
Think of every AI task as having three kinds of input.
Load-bearing input. Remove it and the answer changes. This is the actual material the task operates on, plus the constraints that steer it.
Decorative input. Remove it and the answer is identical. This is the background you include because it feels responsible. Company history in a task about one email. The whole transcript when the decision lives in six sentences. The full brand guide when the task needs three rules from it.
Harmful input. Remove it and the answer gets better. This is the bulk that dilutes attention and buries your real instruction.
Most people's prompts are maybe 20 percent load-bearing. I have audited plenty, including my own, and the number is consistently embarrassing.
The system that fixes it has three parts.
Part one is the compressed context block. Write once, reuse forever. Everything an AI genuinely needs to know about your business in under 350 words. Who you serve, what you sell, how you sound, what you refuse to say. Not your history. Not your values statement. Only the things that change an output. I re-explained my business in every new session for longer than I want to admit, and I paid for it every single time.
Part two is the brief that replaces the dump. For every long document you paste repeatedly, build a short brief that carries the same decision-relevant meaning. A 400-word brief distilled from a 40-page document pays you back on every single run, forever. This is the highest return work in the whole system and it is a one-time build.
Part three is the reference library instead of the paste habit. Organize your material so you pull the relevant piece into each task rather than including everything in case. A library is a one-time build. A paste habit is a recurring bill.
Notice that all three parts are things you build once and benefit from repeatedly. That is what makes this worth an afternoon rather than a project.
The Seven Steps
One: find your highest-volume task first. Improvement compounds by run count, so fixing something you do forty times a week beats fixing something you do twice a year. List your AI tasks with rough frequencies and start at the top. This takes ten minutes and determines whether the rest of the work is worth anything.
Two: measure cost per completed task, not cost per subscription. A flat monthly fee hides which workflow is eating the budget. Divide what you spend by what you actually produced, task by task. The expensive one is almost never the one you would have guessed.
Three: audit one prompt for load-bearing input. Take your highest-volume prompt and find out what is actually driving the output. Here is the prompt I use for this.
[The Job]
Analyze the prompt below and tell me which parts are actually determining the output.
This is for: me, cutting input cost without hurting quality.
It matters because: I cannot cut safely until I know what is load-bearing.
[The Background]
Here is the prompt I currently use: [PASTE YOUR PROMPT].
Here is a typical output it produces: [PASTE AN OUTPUT].
Here is what I need the output to do: [DESCRIBE THE REQUIREMENT].
Do not use: generic prompting advice. Analyze only what I pasted.
[The Deliverable]
Return: a ranked list of input elements by how much each one influences the output, under 400 words.
Must include: anything in my input that appears to do nothing, and anything you believe cannot be cut safely.
Optimize for: diagnostic precision.
[The Questions]
Ask me any questions you have.
Four: build the compressed context block. Under 350 words covering who you serve, what you sell, how you sound, and what you will not say. Test it by running a task with the block instead of your usual background material and comparing outputs side by side. Keep the version that wins.
Five: convert one long document into a brief. Pick the document you paste most often. Distill it to under 500 words of decision-relevant content, then note what you dropped and why, so you can put something back if quality slips. Run five tasks against the brief before you retire the original.
Six: match the model to the job. Sort your tasks by what quality bar they actually need. You are almost certainly paying flagship rates for work a cheaper model handles identically. Assign the expensive model to the one or two tasks where the difference is visible to a customer, and move the rest down. This is usually the single largest line-item saving available, and it requires no prompt changes at all.
Seven: give your team three rules instead of a pricing lecture. Nobody on your team is going to read a rate card, but they will follow three short rules. Write them in plain language, under twenty-five words each, and make one of them about what to do with long documents. Then put a fifteen-minute cost review on the calendar monthly, because costs drift upward quietly and only a routine catches it.
Frequently Asked Questions
How do I know if I am hitting a context pricing threshold?
Check your provider's documentation for a per-request input threshold, then estimate your typical prompt size at roughly 750 words per thousand tokens. If your largest recurring prompts land anywhere near the threshold, you are at risk of repricing an entire request over a few pages of text. Measure your biggest prompt first, since that is where the exposure concentrates.
Does cutting my prompt length hurt output quality?
Usually it improves it. Long prompts divide the model's attention and bury your actual instructions, which is a common cause of outputs that ignore a requirement you clearly stated. Run a side-by-side test on ten outputs before you commit, and keep whichever version genuinely wins rather than assuming either direction.
What is the fastest way to cut my AI costs this week?
Move your lower-stakes high-volume tasks to a cheaper model. It requires no prompt rewriting, no new tools, and no team retraining, and for most businesses it is the single largest available saving. Reserve the flagship model for the one or two tasks where a customer would notice the difference.
Should I wait for the cheaper open models before optimizing?
No, because the two things multiply rather than substitute. If you cut your input bulk in half and then the cost floor drops, you capture both. If you wait, you simply pay a lower rate for the same waste. The cleanup is also what makes moving to a new model easy when you decide to.
How much can a small business realistically save doing this?
It depends entirely on your volume and how bloated your current inputs are, so I will not quote a percentage I cannot source. What I will say is that the arithmetic is visible to you within an hour: measure cost per task before, make the changes, measure after. That comparison is worth more than any benchmark figure I could give you.
What This Comes Down To
Sixty-four cents and a dollar twenty-four.
That gap is the whole post. Four pages of text you did not need, multiplied by every time you run that task this quarter.
I do not think anyone set out to build a trap here. Bigger context windows are a real capability improvement and the labs deserve credit for them. The pricing just stopped being simple, and nothing in the marketing prepares you for that.
But here is what I keep coming back to. The discipline that fixes your bill is the same discipline that fixes your output. Tightening a prompt is not a cost-cutting chore, it is a thinking exercise. You cannot decide what the model does not need to see until you have decided what the task actually is.
That is why I like this work. It pays twice.
So go find your most-run prompt. Not your fanciest one, your most-run one. Cut it in half on purpose, run it five times, and look hard at whether the output actually got worse.
My bet is that it got better, and your bill got smaller, and you learned something about your own process in the process.
The most profitable AI skill of the next year is not prompting. It is knowing what to leave out.
P.S. If you cut a prompt in half and the output clearly degrades, you have not failed. You have just located your load-bearing input precisely, which is information most people never get. Write it down and stop touching it.
About the author
Jonathan Mast is the founder and CEO of White Beard Strategies LLC, where he teaches non-technical business owners how to use AI to amplify the skill and experience they already have. He runs a Facebook community of roughly 500,000 members, the AI Insiders membership, and live training programs built around the Perfect Prompt Framework. He built a seven-figure agency, lost it, and rebuilt it, which is why he treats a 94 percent cost increase as a business problem rather than a technical footnote.
Draft note for review: the Anti-AI Writing Style Guide referenced in the task is not present as a file in this workspace and the linked Google Doc was not retrievable in an automated run, so this draft was written against SELFSCRIBE-3.1.md plus the hard formatting rules in JONATHAN-CONTEXT.md section 5. No savings percentage is claimed because none could be sourced. All pricing figures are sourced in AI_Influencer_Report_2026-10-02.md.
