# Why an OpenRouter bill spikes when your code didn't change > An OpenRouter bill spike on flat traffic usually means a different upstream provider served your calls. Same model, about 10% more per token. URL: https://getculpa.com/openrouter-bill-spike Last reviewed: 2026-08-01 ## Answer An OpenRouter bill spike on flat traffic usually means a different upstream provider served your calls. The same model lists against several providers whose rates differ by about 10%, and routing follows availability rather than your intent. Culpa, a local-first LLM cost, margin, and forecast ledger, prices each call by the route that served it, so a rate change shows up as a named cause. ## Why this happens This one has a signature that separates it from every other cost increase, and the signature is the ratio. A prompt change moves tokens per call. A model upgrade moves the rate and usually the tokens too. An upstream route change moves the rate alone, by the exact percentage that separates two listed providers, while tokens per call stay identical to the decimal. So the question isn't how much the bill rose. It's whether the tokens moved with it, and if they didn't, the route is the only remaining explanation. ## What this usually looks like - Cost per call rose by a clean single-digit percentage with tokens per call unchanged. - No deploy went out anywhere near the day the step happened. - The increase applies across every feature using the routed model at once, rather than to one of them. - Nobody can name which upstream provider is serving your traffic, before or after. ## Common mistakes - Hunting for a prompt change when tokens per call never moved. Why it hurts: You spend days bisecting deploys for a cause that was never in your repository. Do instead: Check tokens per call first. Flat tokens with a higher rate rules the prompt out immediately. - Recording only the model on a routed call. Why it hurts: The model is identical either side of the change, so your own records can't tell the two apart. Do instead: Record the upstream provider alongside the model. Without it this incident has no evidence. - Accepting the new rate because the difference looks small. Why it hurts: A few percent on your highest-volume path compounds every month it goes unexamined. Do instead: Pin the provider you priced against, and treat an unpinned route as a floating cost you accepted. ## Self-check - Chart cost per call and tokens per call on the same axis for 60 days. Look for one moving alone. - Divide the new cost per call by the old one. A clean ratio near a listed premium names the cause. - Check your call records for an upstream provider field. If it doesn't exist, add it before the next incident. - List every provider serving your routed model and note the spread between cheapest and dearest. - Decide whether to pin, then reprice the month at the provider you pinned to confirm the fix landed. ## Two months, identical traffic, one changed ratio (illustrative) 300,000 calls a month on Claude Opus 4.7 through OpenRouter, each sending a 5,000-token repeated prompt at an 80% cache hit rate and returning 400 tokens. OpenRouter lists this model at $5.00, $25.00 and $0.50 on most upstream providers and at $5.50, $27.50 and $0.55 on others. Volumes are modelled. Month 1 on the standard provider: $5,100 across 300,000 calls = $0.0170 per call Month 2 on the premium provider: $5,610 across the same 300,000 calls = $0.0187 per call Tokens per call are identical in both months, so no prompt moved $0.0187 / $0.0170 = 1.10, matching the listed premium exactly A prompt change moves tokens. A route change moves the rate alone, and the ratio says which happened A clean 1.10 against flat tokens is a fingerprint, not a coincidence. It points at the upstream provider and rules out every change your team could have shipped. ## Cost figures Every figure carries its confidence and its source. No figure on this site is provider-reported. - $0.0170 to $0.0187 — modelled cost per call before and after an upstream route change, on identical traffic [estimated] Source: Both endpoints from the teardown arithmetic at rates read from OpenRouter's Claude Opus 4.7 page on 2026-08-01. A range because call volume and cache hit rate are modelled. - 10% — listed premium between upstream providers serving Claude Opus 4.7 on OpenRouter [calculated] Source: $5.50 against $5.00 input and $27.50 against $25.00 output, read from OpenRouter's Claude Opus 4.7 model page on 2026-08-01. ## FAQ Q: Why did my OpenRouter bill rise with no code change? A: Most often because a different upstream provider served your calls. The same model lists against several providers whose rates differ by about 10%, and routing follows availability unless you pin one explicitly. Q: How do I tell a route change from a prompt change? A: Look at tokens per call. A prompt change moves them. A route change leaves them identical and moves only the rate, so the ratio between your old and new cost per call lands on a clean number matching the listed premium. Q: Does OpenRouter drop the cached rate? A: No, and an earlier version of this page said otherwise. The Anthropic re-listings pass the cached read through at the direct rate, $0.50 per million on Opus 4.7, read from OpenRouter's own model page on 2026-08-01. Culpa's price book records no cached rate for those rows, which is a gap in the book rather than a fact about the platform. ## Sources - OpenRouter models: https://openrouter.ai/models - Anthropic pricing: https://platform.claude.com/docs/en/docs/about-claude/pricing Run the free Cost Leak Scan: https://app.getculpa.com/scan?source=pseo&slug=openrouter-bill-spike&cluster=problem Machine-readable index of every guide: https://getculpa.com/api/pages Human-readable index of every guide: https://getculpa.com/guides Site overview: https://app.getculpa.com/llms.txt Privacy: Culpa runs on your infrastructure. Your prompts and responses never leave it. Culpa counts calls to run your plan, and it fails open, so if it ever breaks your app keeps running.