I Spent an Hour on OpenRouter and Realized I’ve Been Paying Too Much






I Spent an Hour on OpenRouter and Realized I’ve Been Paying Too Much


I Spent an Hour on OpenRouter and Realized I’ve Been Paying Too Much

I signed up for OpenRouter on a Tuesday night because a Reddit comment finally pushed me over the edge. Someone in r/LocalLLaMA casually mentioned routing their summarization jobs through a Qwen variant for almost nothing, and I realized I had been quietly burning Claude tokens on tasks that did not need Claude at all.

An hour later my coffee was cold and I was staring at a pricing table that genuinely surprised me. Same prompt. Same output quality for my use case. One-tenth the cost.

The signup was almost suspiciously easy

I expected the usual dance: email verification, billing form, some kind of approval queue. OpenRouter just let me in. Google login, twenty dollars on a credit, and I had a single API key that pointed at hundreds of models from different providers.

That last part is what I underestimated. It is not a model. It is a router. One endpoint, one key, and suddenly I can call Claude, GPT, Gemini, Llama, Qwen, DeepSeek, Mistral from the same client. My Mac mini did not even notice the difference.

The pricing table is where my night stopped

I opened the models page and sorted by price. I had been mentally pricing everything in Claude Sonnet numbers because that is what I use in Claude Code every day. Seeing the spread laid out in one column was a small shock.

For one of my blog automation scripts that just rewrites a draft into cleaner Markdown, I had been spending real money on a top-tier model. The same task on a Qwen route costs roughly one-tenth. Not half. Not a third. One-tenth. I refreshed the page twice because I did not trust the decimal places.

Eben’s note: I had been treating “use the best model” as a default, when most of my home agent jobs are honestly closer to glorified string manipulation.

Swapping one call in one script

I did not refactor everything. I picked the smallest, dumbest job in my pipeline: the part of my Tistory automation that takes a rough draft and tightens up the spacing and headings before posting. It does not need taste. It needs obedience.

The change was almost insulting in how small it was. I kept my OpenAI-compatible client, swapped the base URL to https://openrouter.ai/api/v1, swapped the API key, and changed the model string to a Qwen route. That was the whole diff. Claude Code helped me clean up the env variable handling so I could flip between providers with one flag.

The first response came back. It looked fine. The second one looked fine. I ran it on ten old drafts and compared. For this specific task, I genuinely could not tell which output came from which model. That is the part I am still chewing on.

Where the cheap model is not enough

I want to be honest. I tried the same Qwen route on a harder job, the one where I ask the model to actually reason about the structure of a post and suggest a better angle. It was not the same. The output was technically correct and creatively flat. Claude still wins that one for me, easily.

So the lesson is not “switch everything.” The lesson is that I had been using one expensive hammer for every nail in the house, and OpenRouter made the cost of that habit suddenly visible. Some jobs deserve the expensive model. Most of mine do not.

The part nobody warns you about

The pricing table is a rabbit hole. I lost another twenty minutes reading model cards for things I had never heard of. There are providers I cannot pronounce hosting models I cannot evaluate, all sitting one model string away from my Mac mini. It is exciting and slightly overwhelming.

I also noticed the latency varies a lot between routes. A cheap model on a slow provider can feel worse than a pricier model on a fast one, even if the token cost looks great on paper. OpenRouter shows you throughput numbers, and I started caring about those almost as much as the price.

What I am taking from this

I am going to audit every API call in my home setup this weekend and ask one question per script: does this actually need Claude, or am I just being lazy. The ones that do, stay. The ones that do not, get a Qwen or DeepSeek route through OpenRouter.

If you are running any kind of home automation that hits a frontier model by default, spend an hour on the OpenRouter pricing page. Do not commit to anything. Just look. There is a real chance you are paying ten times what you need to for at least one job in your pipeline, and you will not know until you see the numbers next to each other.

Tags: #AIagents #ClaudeCode #OpenClaw #MacMini #OpenRouter #buildinginpublic #Eben


Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *