10 ms·
So you want to use OpenRouter?
- Krisso 2mo agoWish this had more insights on 'cost' - I found OpenRouter credits to burn up fast.
- abuds 2mo ago[dead]
- anik200 2mo agoGood job
- hadeer626 2mo agoYes
- rima_667 2mo ago[flagged]
- bsaul 2mo agoThat looks absolutely horrifying. What are the alternatives ??
- john01dav 2mo agoI've had opencode go + opencode work reliably, though I'm skeptical of how robust their data security claims are in practice because they suddenly blocked accessing Deepseek unless you were okay with the data going to China where true data privacy for something like that is illegal, which makes me wonder where it went before, which weakens my trust. It's also a lot less useful now that Deepseek is so much more expensive.
- james-bcn 2mo agoVercel AI Gateway is one I've used: https://vercel.com/ai-gateway/models https://vercel.com/ai-gateway/models
- maxcoding 2mo agoVercel AI Gateway also route to other providers, so the same issues can occur there as well.
- bakugo 2mo agoThere are none, this isn't a problem specific to OR as much as it is a problem with serving LLMs in general. If you use any other meta-provider that routes your requests to third party providers, you'll likely face the same issues. If you try using any of those providers directly, you'll likely face some of the same issues as well, except you won't have the option of quickly swapping to a different one and taking your credits with you. Extreme variance in quality and feature support per provider is probably the biggest obstacle holding back adoption of open weights models.
- TZubiri 2mo agoJust use a single vendor. Literally nothing wrong with that, and you avoid the complexity of both n-1 of the vendors (leaving you with the highest quality vendor) as well as the issues with the aggregating layer. Not sure why people are drawn to this particular blunder. The promise of vendor neutrality maybe? I'll take working product over vendor-neutral slop anyways.
- bbor 2mo ago> vendor-neutral slop Never before have I heard this sentiment, NGL. Vendor-neutrality has been an OS(/FLOSS) darling for, well, the whole time. RE:"single vendor", if this post is to believed then you might have picked one that has 100x the tool calling errors for the next SoTA model, if your single vendor serves the next SoTA in the first place. It also completely erases the notion of competition driving down prices -- that would only hurt you in the short term, but obviously would ruin the whole ecosystem long term. I feel like I must be missing something?
- mrngld 2mo agoHow does it erase the notion of competition driving down prices? Endpoints are largely compatible, so the code change required to switch from one to another is trivial. Don't load 6 months' worth of credit in an account, keep it tight. There's fairly little lock-in. The most significant lock-in to me isn't even something you mentioned, but rather it's model related; I personally put a little time into trying to optimize my prompts every time I change models, as they all have their own unique... flavor. As for tool calling errors, it seems like first party providers are among the best, I got the feeling that's what he was suggesting, though of course that's why you test. You can also go directly to Together.ai or whoever else you please. Like others have said I think Openrouter seems neat for testing, but even just as a hobbyist I've been drawn to go direct to particular providers due to irritating little issues that I now see just weren't me.
- TZubiri 2mo ago>Endpoints are largely compatible, so the code change required to switch from one to another is trivial. Wrapping a specific implementation in a neutral function is something you learn to do in year 1 of programming. This specific issue and argument I see in lots of different aggregator dependencies, Terraform, LiteLLM/OpenRouter. They promise to save some hypothetical work in the future if your boss asks to change vendors, and it turns out to be very trivial work that is just a regular part of our programming job, changing a couple of lines in order to change vendor. It's worth noting that there exists a similar set of technologies with a reasonable tradeoff, using a framework that targets different user-platforms makes sense, write-once and deploy at iOS and Android is a reasonable tradeoff, but because you are deploying to those providers simultaneously and it's a user-choice so you don't get to pick one or the other (without losing clients), there's still arguments to chosing just one and losing market share, or doubling the workload and building native for both, but this is a true engineering choice. I feel like stuff like OpenRouter and TerraForm take elements of these frontend abstraction technologies and wastefully apply them to backend tech. A particularly egregious case is when there's an aggregation layer for aggregation layers, say, a tool that generates TerraForm or Chef configs, or a tool that generates Docker and Podman containers, or a tool that generates LiteLLM/OpenRouter configs. Sounds dumb, but it happens when there's a market share for it. Can even get to 3 layers deep. At the foundation might be an aversion to making an irreversible choice, which is an innate emergent psychological phenomenon, but is supported by the Bezos Amazon policy of reversible and irreversible doors. But again, even if you want to be light, using some of these aggregating tools isn't necessary, you can just build on top of a tech, and switch later. The only thing you get with an aggregating layer is that the API ends up being the common denominator so you lose out on the competitive advantages of each choice, or are forced to use even more complex API logic like LLM(commonParam1, commonParam2, vendorParams= {"vendor1"=:{"vendorParam1":"blabla"}} or worse, use hard-coded aggregator provided mappings between the aggregator API and the vendor API that may be incomplete and relies on updates from the aggregator dev. Less is more.
- lukasbm 2mo agoIf you only care about open source models, cline and opencode provide usage based access and subscriptions for general API access
- maeln 2mo agoOpenrouter is useful for quickly testing various models with just one API. In development, it's useful. I would not run it in production tho' for all the caveat mentioned. Go to the first party provider directly, it's cheaper usually. And the cost to rewrite to use their API is usually noting (you can even have both and a feature flag), especially if you just vibe code it.
- danvdb 2mo agoI've used Requesty (https://www.requesty.ai https://www.requesty.ai), let's you pin down providers and build your own routing policy so you at least somewhat know what to expect.
- nacs 2mo agoOpenrouter lets you pin or blacklist providers or specify provider per-request as well.
- vinhnx 2mo agoI've been using Merge AI Gateway and it's been useful so far. They tend to add new models quickly, and support has been responsive. https://gateway.merge.dev/ https://gateway.merge.dev/
- matt_merge 2mo agoGlad you’ve been enjoying Gateway! We also have some huge discounts on open models like GLM 5.3 Flash.
- vinhnx 2mo agoHi Matt, awesome you're here. I've been using GLM-5.3 Flash since it came out and really enjoy using with via Merge AI Gateway.
- JaceComix 2mo agoFireworks hosts the available models themselves which probably solves the problem consistency problem that OP had to deal with. It's been a few months since I looked around at this topic, but Fireworks and Openrouter were the two options I (briefly) tried.
- dools 2mo agoI was looking for an LLM gateway and saw that the most popular one had just had a massive supply chain attack, so I wrote my own. Took about 2 weeks and initially I wrote it as a provider for pi coding agent. I connect to moonshot, qwen, Gemini, zhipu, anthropic, deepseek and OpenAI. I use models.dev to load model and pricing info. Adding new providers is pretty easy because I have a standard internal format and each provider has an adapter that translates between my standard format and that required by the provider.
- jwrallie 2mo agoI noticed some strange behavior when I was setting it up to avoid providers that collect data, hence blocking default providers. Definitely it is worth filtering well tested providers, which is a feature OpenRouter provides.
- jeremyjh 2mo agoThe article that I read addressed this point specifically. "Trusted" providers do not maintain consistent performance, and do not have the same performance across different models.
- joelthelion 2mo agoExcellent post, thanks for the article. This is very relevant for anyone using openrouter and similar services seriously. I feel there is still a lot of progress to be made before we can really trust LLM providers.
- xienze 2mo agoIt's good to quantify the extent to which a lot of the stuff on there is just vibe-hosted. But I think it was always pretty apparent that this was the case. You've got numerous providers all running the gamut of: * Hardware availability * Competency * Scruples
- kinard 2mo agogreat post, I just put $100 in credits on open router to try different models, I think maybe using the "real" provider is the way forward once I've spent my credits and decided which one I want (for now).
- irthomasthomas 2mo ago[dead]
- philipp-gayret 2mo agoBe sure to spend them! Another great feature of OpenRouter is that they will take your credits after a year. They just delete them. A ToS-legalized theft if you ask me. (Even if you are still actively using those credits.)
- bakugo 2mo agoAs of right now, they only expire credits if you don't use the account at all for a year. This is different from, say, OpenAI, where your credits expire unconditionally. That said, they do deserve the right to expire them regardless, so this could change in the future. https://app.answerhq.co/openrouter-ai/articles/credits/credits-expire-after-about-a-year-of-account-inactivity https://app.answerhq.co/openrouter-ai/articles/credits/credi...
- alexcz 2mo agocould not agree more one pet peeve of mine is that using strict json output also does not work on all the endpoints of the models so I have to go through them one by one try it out and then only whitelist them.
- _ink_ 2mo agoWow, that explains a lot. I was using OpenClaw with open router, but stopped because how inconsistent the results were over the same prompt. I thought OC is at fault, never would have guessed that there are differences between providers.
- quietsegfault 2mo agoThe way that OpenRouter frames it with having calls routed to whatever provider is handy encourages you to think that they’re all the same in basic functionality. Really sours me on OpenRouter.
- EDEdDNEdDYFaN 2mo agoI wouldn’t blame openrouter, blame the providers that have lower quality of service than they should
- SomeonesAccount 2mo agoexactly. all of these people complaining are using it wrong. you cant just expect a layer of abstraction to perfectly fix all the layers below it! plus, open router does a great job of handling a lot of the provider problems, but it literally cannot fix the output of the provider
- dnugget 2mo ago[dead]
- CubsFan1060 2mo agoAnother thing to be aware of -- apparently their billing limits don't work. Somehow someone was able to use my key from Singapore. It had a $10 daily limit and they were able to spend $100. Not only that, it got me blocked from all models for the frontier labs. On top of that, near as I can tell, there are no protections for your API key. No restrictions by country, IP, etc...
- nhecker 2mo agoJust chiming in that I've never had this experience with them. I set, hit, and depend on those limits regularly. I would be wildly interested in reading what their support analysis had to say about this situation, if such a postmortem was done.
- CubsFan1060 2mo agoSo far it was just "investigating". From the logs, my best guess is they sent all the requests at approximately the same time, and whatever limiting they do doesn't react fast enough. I get it, the API key was my responsibility, but, setting the dollar limit is exactly the guard they suggest against that.
- numlocked 2mo agoWe do now indeed have IP restrictions for API keys
- CubsFan1060 2mo agoI think that's only on the enterprise plans? So no real protection for those of us using open router personally? Or did I miss other protections somewhere?
- npn 2mo agoAs expected vibecoding bros cannot even read the manual properly. It is pretty trivial to pin a single provider for a model. Better yet, instead of calling the model directly, use presets instead. You can easily change the setting on openrouter without having to update your app every time.
- ptsneves 2mo agoThe article mentioned they pinned the provider and model and the result was bad as well with their own shenanigans. That part was in the end of the article so maybe you missed it.
- deleted 2mo ago[deleted]
- joshstrange 2mo agoThis squares with my, much much, smaller OpenRouter usage. It’s just incredibly unreliable and you are forced to pin providers and even then it can be a crapshoot as the author found. OpenRouter sells the idea of swapping being commodity providers but it couldn’t be further from the truth. Provider A is often not swappable for B or C (again, as this author found). It can be crazy-making as you sit there thinking “OpenRouter has no clothes right?! Am I the one that’s wrong?”. I love the _idea_ of OpenRouter and maybe Stripe can improve this situation but the only sane way I’ve found to use it is to tightly pin providers to the point I wonder if I should just use the providers directly. Without pinning you are in for a world of hurt and unreliability (varying model capabilities, speed, etc).
- fc417fc802 2mo ago> to the point I wonder if I should just use the providers directly. How many account credentials, balances, and tokens do you want to maintain? Even without automatic failover services such as openrouter are still incredibly useful. Personally I pin a single vetted provider in the interest of minimizing risk.
- embedding-shape 2mo ago> just incredibly unreliable and you are forced to pin providers and even then it can be a crapshoot as the author found. But that's the intention right? Even the name implies they just send stuff around for you, and if you want to control the routing, you'd lock down providers. I don't see how they could build what they wanted to build, and not have it end up unreliable if you freely round-robin between providers, it's bound to work exactly like this. > I love the _idea_ of OpenRouter and maybe Stripe can improve this situation but the only sane way I’ve found to use it is to tightly pin providers to the point I wonder if I should just use the providers directly. This is quite literally the point of OpenRouter. A unified interface, so you can easily switch providers without changing a ton of code which using providers directly would most likely mean, as there are slight differences between them. And the providers all run different weights, so of course quality/performance will differ among them. I guess OpenRouter is a bit like Amazon, in that they're just routing stuff around for you, but to actually find the good and usable stuff, you need to focus in on what providers/manufacturers you know are good, and stick with those. Still, the unified interface helps you to shop around and try different ones when you want to.
- rpjt 2mo agoI never tested this but always suspected it. When I learned that providers differentiate themselves on how they optimize and host the model (otherwise, why would you choose one over another?), I figured some were less "give me the best possible experience" than others.
- ofisboy 2mo agoI use Fireworks for a production app. Much lower volumes though. My only gripe is their serverless offering for reranking has only 1 model which is Qwen 8b and it's quite expensive.
- Macha 2mo agoI do use OpenRouter for my personal use and this matches with my experience. I still use it because of it's top up model providing a way to not get surprised by out of control costs and being able to switch models with one account, but it's very noticeable at times. The models I've mainly been using recently are GLM 5.3 Flash and GLM 5.3. While obviously all these models have some variability, GLM 5.3 Flash feels like it oscillates between "I can't believe it's not Sonnet", but it costs a fraction of that and "This feels like I'm back using GPT-4, why am I even bothering with an LLM?".
- copperx 2mo agoUsing the same provider?
- SomeonesAccount 2mo agoexactly. you can specify a provider in your request to openrouter, or, better yet, use the :exacto endpoint to make open router automatically choose one that is good at tool calls.
- mesmertech 2mo agoYea I can believe all these. I've personally have been having issues on these points: "200 OK, no answer" - insane that openrouter's main feature is literally a fallback and streaming doesn't support 200 no content to fallback to another provider or smth. "rate-limit by IP"... now it kinda makes sense why deepseek v4.1 flash rate limits me on prod but never seems to happen on local. Makes you have to basically pin Deepseek as provider, since I've never had 429 error on them
- bbor 2mo agoWait WTF?! I thought performance was, well, performance, not efficacy! OpenRouter's UI in this section is remarkably broken and unclear at the same time, and I have no idea where the author got those clean charts. "AutoExacto" numbers (completely meaningless name) are available for 6 providers, two of which are the same provider, and none of which are even in the top half throughput-wise. When you click "+28 more providers", it just shows a clearly broken modal. And the the next two graphs are even worse. Really all of these graphs are pretty and completely 100% useless. I feel like it's absolutely insane that some providers serve the same model with much less efficacy. That doesn't make sense to me. What's going on?! I'm suddenly feeling intense shame for having routed all my non-subscription usage through them so far, and honestly some white hot anger that they would blatantly lie about something so important. What am I missing? Is this really true?
- numlocked 2mo agoWe run benchmarks against all of our endpoints, in production. That first chart that the author shows is in fact our live benchmarking data. If providers underperform, we kick them out of the routing pool. That is why we run those benchmarks. Performance And errrr...yeah...that auto-exacto performance chart is both 100% useless, and totally unclear. We will get that fixed. But under the covers it is doing a lot of valuable work! https://openrouter.ai/docs/guides/routing/auto-exacto https://openrouter.ai/docs/guides/routing/auto-exacto
- bbor 2mo agoOh wow someone from the team! I'm really heartened by this response -- as you can tell, I've been something of a fan, so I felt kinda betrayed by the idea that this was a risk. Thanks for clarifying, and for taking my frustrated hyperbole in stride. Submitting an application to your product role now. "All of the models are at least okay" is heartening, but there's a whole bunch of fun places to take this. ¡Viva La OpenRouter! (again)
- ghm2199 2mo ago> The tool call is in the text Noob question: do good harnesses automatically optimize for bad tool calling behavior automatically?
- vova_hn2 2mo ago> The same model will benchmark very differently Providers probably serve quantized versions without disclosing it. Which is a real shame, because for certain tasks I would be perfectly willing to trade accuracy for cost. But, unfortunately, it is impossible to explicitly choose how quantized do you want your model to be, unless you are running it yourself on your own (or rented) hardware. BTW, does anyone knows if LLM Gateway suffers from the same issues? Currently looking at trying it, but haven't got to it yet.
- desterothx 2mo agoI mean that is addressed as well later, even when they do declare the quantization, doesn't mean you'll get better performance than the lower quantized one. I'm guessing they're doing something similar to what stadia was doing, saying you are playing games in 4k, because you're getting a 4k stream, but the game itself is running in 1080p
- kadoban 2mo agoI think it's not even that sophisticated here, the providers are just lying.
- joelthelion 2mo ago> Providers probably serve quantized versions without disclosing it It should be OpenRouter's responsibility to protect you against it, by regularly benchmarking providers and giving you the control to avoid bad providers. In fact, that's a big opportunity for them, since it justifies their place as a middleman between users and inference providers.
- ActivePattern 2mo ago100% agree. The key issue is that users think they are getting results from a specific model configuration and they are clearly not, which is fraudulent. If OpenRouter wants to succeed as a business, they need to be auditing the providers they connect to (i.e. benchmarking) and removing fraudulent ones from their service.
- srcreigh 2mo agoWithout pinning providers, you pay let’s say 2x more for agentic coding, since that many input tokens aren’t cached as you bounce between providers.
- hqm_ 2mo agoI believe OpenRouter addresses this with sticky routing and keeps a conversation on the same provider and falls back if that provider becomes unavailable via an explicit session_id to keep requests together. You’re right though that upon a failure cache is not portable and incurs additional costs.
- seanieb 2mo agoI keep trying to sign up but they ban my account before I can use the service, and their support team doesn’t respond to my emails.
- dangoodmanUT 2mo ago> Reasoning models sometimes put everything in the reasoning field and hand back content: null, finish_reason: "stop". 345 completion tokens, HTTP 200, nothing to show the user. This is actually expected behavior. No content and no tool call is the same as content-only: the agent decided it's done. Anthropic has done this for a while.
- fl0id 2mo agoGod that was painful to read.
- eitally 2mo agoThis is why it's not recommended to use providers below the Silver level in Semianalysis' rating index. https://newsletter.semianalysis.com/p/clustermax-20-the-industry-standard https://newsletter.semianalysis.com/p/clustermax-20-the-indu...
- neya 2mo agoThe best part about OpenRouter is 200 OK is probably hardcoded into their responses. I used to get content: "" all the time and I used to triple check my code to see if I was doing something wrong until I realized most AI providers in general have vibe coded their infrastructure as well and it is just a futile attempt to even fight it.
- sandinmyjoints 2mo agoI was just thinking that this kind of behavior is a glimpse of the future!
- ltononro 2mo agoLooks like someone could make some dollars re-creating openrouter from scratch and proving reliability across evals/models/providers/configs
- anonzzzies 2mo agoYeah, it is actually very bad now. And somehow keeps leaking keys.
- ggdG 2mo agoWould model values like 'openrouter/pareto-code' or 'openrouter/auto' be of any help?
- polski-g 2mo agoOpenrouter should obviously lock providers off who are lying.
- bambax 2mo agoVery informative article, but I'd say all of this is in favor of OpenRouter, not against it. It gives you full flexibility, not just of models, but of providers. That's the offer!
- bradfa 2mo agoAs long as you are constantly diligent in staying on top of what each provider is doing that may impact you. It reads to me an argument for self hosting, maybe a less capable model to deal with smaller compute resources, but when starting to use that model and inference software to build a benchmark you can easily rerun when you change things to observe the impact of the change. Maybe that’s a similar level of diligence but they feel different to me.
- grim_io 2mo agoMy limited impression is, that all the 3rd party inference providers are absolute garbage. I was so disappointed that I won't consider any of them for at least a few years.
- deleted 2mo ago[deleted]
- rolfus 2mo agoThis is very useful information and comes at a perfect time! I use Openrouter for my newly released running tracker (I use it for live coaching and post-run debriefs). I've benchmarked a bunch of models over time to evaluate their aptitude for this specific task, and have noticed that sometimes a model can underperform for seemingly no reason. I'll be sure to include model providers in my benchmarking suite going forward!
- aembleton 2mo agoWhats the tracker called? I'd like to try it.
- bko 2mo agoIt's in the parents profile Android app called "AudioRun" https://play.google.com/store/apps/details?id=com.audiorun.app https://play.google.com/store/apps/details?id=com.audiorun.a... https://apkpure.com/audiorun/com.audiorun.app https://apkpure.com/audiorun/com.audiorun.app
- aranaur 2mo ago> That's enough volume to hit every edge case at least once. Is it, though?
- Semaphor 2mo agoUnder privacy, ignored, I put providers that always suck. Digital Ocean, OpenInference, DeepInfra, AtlasCloud, and Alibaba (that one is different, it doesn’t suck in the same way as the others with a dumb model, but instead it’s heavily censored and doesn’t like being used as RP model in Skyrim).
- numlocked 2mo agoCo-founder and COO of OpenRouter here. Thanks everyone for the feedback here. Some of this we are aware of, some of it we aren't. Some we can fix, some of it is inherent to inference (and we in fact improve the situation dramatically). Philosophically, at OpenRouter we are trying to do two different things, that are sometimes at odds with one another: 1. Let you use a lot of capacity across a lot of providers, in a way that "just works" and you don't need to worry about it. 2. Have a huge variety of inference available so you can pick radically different price/performance tradeoffs, data policy decisions, geographic destinations, inventive hardware, etc. These are inherently odd bedfellows, and we are still very much improving how we can make both of them true at the same time. Some quick thoughts on the article itself: 1. Benchmarks: YES! Providers benchmark differently. We run benchmarks on the live endpoints continuously, monitor the median performance, and kick providers out of the default routing pool if they vary by more than a standard deviation. We work hard (and continue to invest) to make sure that providers serving sub-par inference can't game the system, and that our routing actively avoids them. So the chart is accurate (it's our chart) and it actively influences our routing decisions! 2. That is bad and we will fix it. Sorry. 3. When we on-board providers we run essentially the same test as the author did to verify that the param is working as expected. If it isn't, we don't launch the provider. However this is not one we are running constantly in production. We are working on making this more robust in general and I do believe is fundamentally solvable in a way where it will "just work". 4. We 100% agree that users should not filter by quantization. It's a bit of a legacy concept in general; there is a huge amount of code between "model weights" and "inference API" and in almost all cases quality degrades in that part of the stack, NOT in the model weights themselves. 5. Hmm...we will dig in here. We monitor tool calls in real time and route around providers that are regularly mis-parsing tool calls. So you should get a very low rate of these in general. Another area we have invested a lot in: https://openrouter.ai/docs/guides/routing/auto-exacto https://openrouter.ai/docs/guides/routing/auto-exacto 6. We will dig in here as well. I'm surprised this is happening frequently enough to be noticeable. We eat the cost when the finish reason is an error, but not when it is "stop". Perhaps we can expand our "insurance" program: https://openrouter.ai/docs/guides/features/zero-completion-insurance https://openrouter.ai/docs/guides/features/zero-completion-i... 7. Will investigate. 8. We attempt to heal these, but obviously missed some. Will fix. 9. We do not rate limit by IP. Would love some more information here, as that is very surprising. 10. Ugh. That sucks. I'm sorry. We are introducing QoS tiers for production apps, which will address a lot of this.
- epistasis 2mo agoLLM ops is not trivial. The systems for running inference are very complex, and running across multiple GPUs and nodes adds tons more complexity. And when LLMs are run incorrectly, they still work, just not at optimal performance. Even noticing that something is wrong is not trivial, and finding the problem is far far harder. So I guess I shouldn't be surprised at all to see these benchmarks, but still I am! There are such huge economies of scale with batched inference that it's clear this sort of service will continue, but it has a lot of growing up to do. Even AWS Bedrock has a Claude that feels different to me, but I haven't had a chance to do actual benchmarks that would show that.
- dannyw 2mo agoBedrock Claude is absolutely not identical to 1P Claude. They’re close enough to not matter though.
- FranklinMaillot 2mo agoI've had the same experience in my personal use. Unreliable output, thinking token leaking into the conversation... Time to first token and tk/s also vary wildly per provider. The worst case of hallucination I had, was DS v4 flash switching to Italian mid-conversation and impersonating a podcast host for no reason.
- sinuhe69 2mo ago"OpenRouter runs per-provider benchmarks on the same model: GPQA Diamond and TAU-Bench Airline (a tool-calling task)." why I haven't never seen it? Click on the link brings nothing! Benchmark is only for the model. Per provider is a performance matrix (latency, throughput) What did I miss? -- Update: oh, that is the AutoExacto Benchmarks! Now I see it.
- nojs 2mo agoThis is an issue self hosting as well. There’s a lot of footguns that give you slightly bad results. I wonder what tricks one could use to ensure the model is actually performing on par with the reference api, like matching seeds or running exact benchmarks.
- memoryleakgame 2mo ago<Rant> I have been working on a product for months and for 1 of the specific models have become the number 3 user and very likely soon the number 2. Its a google model. The edge cases are crazy to deal with and have taken a long time to find. I am also finding that since it has no fallbacks but no published rate limit I am single handedly taking the model down on what I thought were a reasonable amount of request. There is no other fallback that isn't google. I'm worried that with sustained usage from my users on launch in a few days. Clearly google can't be making that much money on it it im like 10% of the usage and the top 2-3 user of it spending several hundred a month in pre launch testing. So why would they care to help a small time start up? I will have to jump to a cost effective different model and find the footguns all over again at somepoint. Not sure where im going with this but just wanted to let others know </rant>
- voakbasda 2mo agoBuilding a product that depends on a Google product seems like folly at this point. They are notoriously unreliable about keeping products alive. I hope you don’t get burned.
- memoryleakgame 2mo agoMe too, im a bit nervous because I also have evals proving that flash models are actually getting worse at specific task on newer versions and one of my prime use cases peak around flash 3 and tanks in 3.8. So it would be very very horrible for me if they kill old flash models on open router. Yay google, love living in fear of a vendor that they will rug pull me at any point because they can.
- jwxz 2mo agoFor a Google model you might be better off directly using their API, which is unfortunately far more painful than using OpenRouter, but it might at least be more reliable for your product. I think the rate limit issue happens because of OpenRouter sending so many requests to Google.
- danielmarkbruce 2mo ago
- lluisantoni 2mo ago[dead]
- claudeIsDown 2mo agoI couldn't agree more. This articles describes how frustrated has been OpenRouter experience. At the end of the day, I ended up configuring to use the owner provider of each model I needed to use.
- jwxz 2mo agoI also believe some providers fallback to another model entirely. I was recently using Kimi K3 and saw that some requests had no reasoning trace whatsoever. Unsurprisingly, those requests were routed to the less reputable providers (Sail Research).
- neilmovva 2mo agohi, I'm one of the founders of Sail. I'm very sorry that you had a bad experience with us! We are serious about serving models correctly, and always publish a link to the exact HF checkpoint we're using for each model in our docs. If you ever have an issue like this again, please send a note to support@sailresearch.com and we'll make it right with a detailed postmortem.
- jwxz 2mo agoHey, thanks for reaching out. Just wanted to share my experience. I really thought there was an issue in your API. I had quite a few Kimi K3 requests served by Sail. Most of these were fine and had the reasoning traces (I like reading them), however I noticed that some requests were being generated unusually quick and had no reasoning trace, which led me to believe another fallback model was being used, since Kimi K3 always emits reasoning tokens.
- binarymax 2mo agoPretty damning. We're using OpenRouter for some research tasks and it's making me question everything. I suspect lots of the model providers are running into issues like these: https://forum.level1techs.com/t/why-your-local-llm-feels-dumber-than-it-is/253917 https://forum.level1techs.com/t/why-your-local-llm-feels-dum... (HN discussion: https://news.ycombinator.com/item?id=49402232 https://news.ycombinator.com/item?id=49402232)
- ndr_ 2mo agoIf you require consistency for research, I wouldn't recommend relying on hosted inference without validating the provider/inference stack very carefully. For my contribution to OpenAI's gpt-oss red-teaming competition (published as arXiv:2510.01259), I initially used OpenRouter with DeepInfra and Together AI. The results were much too noisy to draw reliable conclusions from, and markedly different behavior through AWS Bedrock was the last straw. I ended up renting GPUs through vast.ai and running the model myself with vLLM.
- jmward01 2mo agoYes to all this but more. The thing that made me leave and go to a single provider was token caching. I have to keep blocking providers that don't properly cache. I see performance tank and then I look in the logs and a new provider has been rotated in and every call to them is uncached because they are clearly broken. This has happened a few times now and essentially destroys cost savings (these providers also often have terrible quality). Don't they monitor for simple things like this? Their own logs show how clear this pattern is for some providers. Simple cache % stats would allow them to block providers nearly instantly.
- numlocked 2mo agoWe have made MASSIVE improvements here, and network-wide caching rates have been improving relentlessly. We do publish the cache rates for each endpoint; see the "performance" area of our model pages. E.g. https://openrouter.ai/deepseek/deepseek-v4-flash-0731#performance https://openrouter.ai/deepseek/deepseek-v4-flash-0731#perfor... Open to feedback on how to make this better.
- stavros 2mo agoCan I block endpoints whose cache rates are below a certain percentage?
- ElectricalUnion 2mo agoCan I block providers (for model, not in general) that have sightly cheaper input/output tokens but have more that 10x the average cache cost? Can I block providers (for a model, not in general) that set up cache write cost when the mode is free cache writes?
- randomblock1 2mo agoYou know how there's a router mode to use the cheapest provider? That only takes into account uncached rates, last I checked. Make another one that takes into account effective rates (the ones that include cache).
- jmward01 2mo ago
- ketzu 2mo agoUntil yesterday I used openrouter mostly as a portal to the big providers: google, anthropic, openai, without having to maintain keys and accounts and credits for all of them separately. Yesterday I wanted to do a bit of benchmarking a prompt across multiple models. Small requests. Outside the big providers, the experience became awful. This explains that experience.
- fzysingularity 2mo agoThe author’s comments on vision providers is especially interesting. We saw that most providers don’t provide native video url support, have high-variability in vision performance (likely due to the fact that they’re serving different quantization levels behind the same model id). If you’re building vision-native apps, there are so many footguns in vLLM/SGLang serving configurations, let alone the routing/orchestration in providers like OR, that leave the user more confused about the model’s capabilities.
- msp26 2mo agoDo you have any advice on this front? I use vllm for a project but only for text tasks at the moment.
- fzysingularity 2mo agotext is mostly beaten to death, so you can expect good defaults to work for vllm. VLMs specifically are quite sensitive to quantization, especially if you want it to do fine-grained localization (time or spatial), and the vllm default params can be way off for your use-case. For example, most vision models don't need 256K context length for modes like Qwen3.8-27B when all you care about is single-image captioning, so you can technically save on KV cache. Video reasoning does require that context length, so it's a different set of deployment parameters that need to be enabled. All of this to say that the providers that offer these models, are simply using vLLM / SGLang, and mostly cater to the text inference use-case (coding, etc). Vision always seems to be a bit of an afterthought.
- msp26 2mo agoGot it, I'll test more deployment params when I benchmark models for vision tasks. Do you have any tips for Gemma 4 31B in particular? I quite like the model but I feel like I'm underutilizing my rented GPU hard due to skill issues. Throughput should be way higher than this, right? --- Gemma 4 31B NVFP4, vLLM 0.29, single B200 (modal), FlashInfer, fp8 KV, prefix caching, 32k ctx Workload: ~6k-token shared prefix (~98% cache hit) + short input, ~250 tokens out, ~250 seqs running. Get ~5-6k output tok/s, flat from 128 to 384 concurrency. Spec decode (DFlash, n-gram) didn't give a good boost which is annoying because I feel like this task should be easy for a draft model to predict. Individual request latency doesn't matter I just need as much throughput as possible. Its only active for a few hours when I need it.
- cesarvarela 2mo agoI noticed this with DeepSeek Flash and DigitalOcean. They are doing something seriously wrong when serving that model; we need something like an SLA, but for intelligence; it's almost fraudulent behavior.
- SXX 2mo agoOpen router have one more annoying disadvantage: credits you buy expire in around 1 year +/- ~30 days. They do sent warning email 30 days in advance, but then just make them disappear. If you for some reason had unusee balance and forget about it; its just gone.
- radicality 2mo agoOh, interesting, I feel like a year so ago I read something posted from openrouter team that they write that credits expire, but that they in actuality don’t expire them. But maybe I’m misremembering, or perhaps that’s changed for the worse in last few months :S
- numlocked 2mo agoWe started actually expiring the credits a ~month ago. If you make any kind of API request, it resets the clock. We try to make it a very generous policy, but we can't keep a monotonically increasing liability on the books. We end up owing (a lot) of taxes on it, but can't actually recognize revenue. We would much rather you spend the credits! Hence the reminder emails, and generous "clock reset" policy.
- wren6991 2mo ago> but can't actually recognize revenue Hmm? You have the revenue already. I know it's awkward from an accounting point of view, but you already took my money. "Letting" me keep the balance in the account is not generous. Edit: on re-reading this came out more combative than I intended, sorry. I think what you're doing is reasonable.
- SXX 2mo agoI kind a get their reasoning. They cant recognize balance topup as revenue because then they'll owe taxes on full amount. At the same time majority of money we pay them usually just gonna be an expense paid to actual inference providers. Then they pay taxes on their fee aka actual profits. Its understandable, but it dont make 1 year expiration any good.
- benjbrooks 2mo agoI'm happy with OpenRouter. They're good at routing requests & spend tracking/management. You should just expect to directly own your relationship with the downstream model provider. Source: Enterprise customer doing $XXM annual run rate of inference spend on their platform
- lellow 2mo ago[dead]
- agcat 2mo agoThis is super insightful
- habosa 2mo agoWe're very happy with OpenRouter in production, although we use it in a pretty limited fashion. We have only ~10 providers allowlisted (based on their location and ZDR policies) and we use only a few models, often frontier models. Has been very reliable for us in production so far. It's generally been great for us to be able to have a single place to manage spend, policies, view logs, etc. Also really nice in code to have a single-line change for switching models. OpenRouter's console is so much better than what you get from the actual frontier labs, and it's nice not to have to translate numbers and concepts across providers.
- bluepeter 2mo agoZDR is the main reason to use OpenRouter as it's difficult (impossible?) to get from OpenAI/Anthropic as an individual or small business.
- MattyRad 2mo agoI agree that OpenRouter kinda sucks, but it took about 15 seconds to see that a few sentences got reverse-compressed into what is now this article, and it's slop.
- owenshen24 2mo ago> For an agent TAU is the score that matters and a 20 point swing is not noise. +1, stuff like this is a big turnoff for reading
- teaearlgraycold 2mo agoNever had any issues using it for personal small scale development. I think the premise of OpenRouter as a magical way to fall back on error or select providers based on price/tok-per-sec/uptime isn’t delivered upon. But it’s an excellent way to simplify the experience of hopping between model providers with a single unified billing system. I mostly only use first party model hosts. Theoretically there are alternatives with higher throughput or lower prices, but it’s simplest to not worry about that optimization.
- user- 2mo agoGreat write up. This aligns with what I've experienced using openrouter. Are there competitors that handle these same issues better?
- joelsol 2mo ago[dead]
- MallocVoidstar 2mo ago> Reasoning models sometimes put everything in the reasoning field and hand back content: null, finish_reason: "stop". 345 completion tokens, HTTP 200, nothing to show the user. This isn't necessarily an OpenRouter issue, Google's Gemini will sometimes do it on their own API. Since they summarize reasoning this means you pay the whole cost and can't get anything out of it.
- system2 2mo agoI still don't get the appeal of OpenRouter. Why not just generate API keys from the providers you want to use, which should not exceed 3-4, I assume, and integrate them into your apps to call them? Are people so lazy, or am I missing something?
- dvdkon 2mo agoIf you're making a commercial SaaS, that's probably the way to go. For individual users like me, with a coding harness and some extra BYOK tools, OpenRouter is convenient and the few extra percent don't hurt much. I appreciate being able to try out any new model with just an ID swap, same with inference providers when they prices change. I know I wouldn't enjoy managing 5+ accounts, each with their own balance, in 3+ tools, so this is one thing I'm happy to outsource.
- system2 2mo agoI have multiple commercial products using multiple LLM APIs. My concern is adding an extra 3rd party dependency and markup on top of the API usage. It just freaks me out to build entire apps on 3rd party single-point dependency.
- Havoc 2mo agoGreat post. I had realized there is variation, but the charts are much worse than expected
- deleted 2mo ago[deleted]
- johnsmith1840 2mo agoSame experience. I migrated over and am happy but that intro was brutal. My basics are I have a test suite that: 1. Finds newest models of my versions 2. Inferences every single model and a few providers for each with a short problem 3. Analyze latency and if a model failed the stupid simple questions drop it and the provider 4. Run larger context haystack kinds of problems. It's cheap and fast less than 5$ so I can do this daily, hourly, whatever depending on how much I care. If it's mission critical I would say you need a two day study running once an hour to know the STD of model variance. Then lock a top 3 contenders via latency dropping routing. Is this easy? No. Is it cheap? Also no. Is it better than just using a trusted labs api? Also not really. But it does give you exponentially more flexibility. Being able to run 10 unique models at the flick of a switch on a problem for pareto front analysis is amazing. And giving a dropdown for customers for multiple model options is powerful.
- mmoustafa 2mo agoYes, you hit it on the head. It's worth it, but you have to do your own evaluation and promotion. Example I forgot to mention: `:nitro` ranking is not the fastest, I do a round robin sampling with representative payloads to find out the fastest providers and reorder my list on the fly.
- johnsmith1840 2mo agoYour doing that sampling/promotion automatically? I considered an automatic promotion path but decided against it I want to actually review the data myself first. What's your model churn rate like? I was worried about customer experience by same day maybe same work getting a totally different model response (also caching is worse)
- anguishe 2mo agoI haven't dove into OpenRouter yet but I see it everywhere now. I'll have to take this into consideration when I finally get around to trying it or something similar.
- deleted 2mo ago[deleted]
- wren6991 2mo agoYeah, this is pretty accurate. Some providers are basically scams too. I encountered one provider for GLM-5.2 which ran at 200 tps (absurdly high), and was so broken that it would issue 20 full reads of the same file in one turn and quickly jump up to 300~400k context and charge me for the prefill. Went straight on my deny-list, but they got a few dollars out of me first. Another common annoyance is having a request go to a provider that dribbles out ~1 tps (even for small models like DeepSeek V4 Flash). If you cancel the request, you still get charged for the prefill and the handful of generated tokens. If you don't cancel the request, you might be waiting 10 minutes for the turn to finish. The overall experience is pretty good, and it's the best way to try new models, but they don't appear to do any real vetting or apply any quality standards to their providers, and occasionally it bites you.
- probabletrain 2mo agoprovider fallbacks are also expensive since you lost the prompt cache. openrouter have a 'session' concept to help with this, but we ended up going direct to providers for higher rate limits and writing our own fallback logic.
- celrod 2mo agoI was just trying deepseek v4.1 flash on OpenRouter. After running reasonably well for a while, I return to the window and see that my scrollback is nothing but this repeated over and over again: ``` OK. Let me write. Let me go. OK. Let me write the script. Let me go. ``` I'm not sure to what extant this is a model problem, vs some providers being fairly broken. If I chose a single provider, I could know how to blame and to avoid them. With OpenRouter, I don't know which provider I was on when this happened.
- plandis 2mo ago> The same model will benchmark very differently This is surprising to me. Does anyone have a definitive answer that accounts for this difference between providers? Do the benchmarks that Open Router runs not account for the stochastic nature of the models? Do the providers lie about quantization or context window sizing? Does Open Router not take into account variations for a given model? I could understand latency/cost benchmarks varying but not the actual generated token responses of the models given the exact same model parameters.
- sheo 2mo agoAs said in the article, all of the providers run different runtimes with proprietary, sometimes untested and weird optimisations There are multiple types of quantisation: weights and KV Cache. Quantizing kv cache can drastically hurt performance
- kristianp 2mo agoThat first diagram is striking: that deepseek's own inference is at least 5% higher on tool calling (TAU Bench) than most other providers. I wonder if they make sure their responses are valid json at the token generation level using a grammar, similar to the feature in llama.cpp. As a regular user of openrouter I didn't know this info was available. Will have to check it out. I've definitely noticed that a high level of deepseek flash responses were looping endlessly before the 0731 release. Edit: looks like the diagrams data is from the "Auto Exacto Benchmarks" section of the performance. Looks like they haven't run the benchmarks of deepseek flash 4.1 on the deepseek provider yet: https://openrouter.ai/deepseek/deepseek-v4.1-flash#performance https://openrouter.ai/deepseek/deepseek-v4.1-flash#performan...
- SpyCoder77 2mo agoBeen using Olly for a while now. Very useful when you only have your Apple Watch. Didn't realize the maker had a blog.
- aftbit 2mo agoThe big advantage of OpenRouter IMO is that you don't have to manage keys, URLs, and subscriptions with 10+ providers. You definitely should still pick providers and pin them, at least if you care about repeatable results.
- polytely 2mo agoI've just been using openrouter to be able to quickly switch models and keep tight control over how much i spend and for that it's great. i also love their chat thing on the site where you can ask multiple models simultaneously , very good for brainstorming
- try-working 2mo agoif you'd rather have your router running on your own machine, check out the router i'm building: https://role-model.dev/ https://role-model.dev/
- ozborn 2mo agoFormer Openrouter user, unhappy to report that Openrouter will expire your tokens with very little warning with absolutely no business justification other than they can. If they were a bank and tokens money, their return is -100% interest after a year. Don't expect your tokens to be there for you after a year of no use....
- creativeSlumber 2mo ago> 6. 200 OK, no answer Reasoning models sometimes put everything in the reasoning field and hand back content: null, finish_reason: "stop". 345 completion tokens, HTTP 200, nothing to show the user. A 200 tells you the request was served, not that there's an answer in it. No content and no tool call is a failure, throw and retry. I ran into this so much I had to modify my harness to handle this.
- 0x12sjhbfsdbf 2mo ago[flagged]
- freeourdays 2mo ago[dead]
- kristianp 2mo agoMeanwhile, openrouter still haven't benchmarked the deepseek provider on their "AutoExacto" benchmark at https://openrouter.ai/deepseek/deepseek-v4.1-flash#performance https://openrouter.ai/deepseek/deepseek-v4.1-flash#performan... .
- kbottner 2mo ago[flagged]