OpenRouter Hosts Produce 20-Point Tool-Calling Gaps for the Same Model
- The author reports that DeepSeek V4 Flash 0731 scored 90.2% on GPQA Diamond and 81.3% on TAU-Bench Airline at first-party DeepSeek, versus 75.3% and 58.4% at DigitalOcean, despite the hosts serving the same model weights.
- Across OpenRouter hosts for DeepSeek V4 Flash 0731, most providers were 5 to 7 points below first-party DeepSeek on the TAU-Bench tool-calling test, while a July Fireworks result reportedly reached a 30-point gap.
- In image tests, DeepInfra's Qwen3.5 122B endpoint misread a K as R, called red blue, and failed to read a word that four other hosts recognized; Venice and Together returned 200 OK while saying no MiniMax M3 image was provided.
- The reasoning.effort setting was accepted by every tested provider for DeepSeek V4 Flash 0731, but the author's three-call tests found that some hosts, including DigitalOcean, GMI Cloud, Mancer, and Venice, did not change reasoning-token output across low, high, and max.
- A month of provider data led the author to conclude that OpenRouter's declared quantization filter, such as FP8 instead of FP4, did not reliably predict GPQA quality across hosts.
Hacker News opinions
I've used opencode go and opencode work reliably, but I do not trust their data-security claims much. They suddenly blocked DeepSeek unless I accepted China-bound data, which made me wonder where it had gone before.
I've used Vercel AI Gateway, and it is another option for model routing:
I do not think there is a real alternative. Any gateway that routes to third-party hosts has this problem, and direct providers can have it too. The large variation in quality and feature support is a major obstacle for open-weight models.
I would use one vendor and avoid the aggregation layer. Vendor neutrality is not worth a product that behaves inconsistently.
I use OpenRouter to test models behind one API during development, then move production traffic to the first-party provider. It is usually cheaper, and switching APIs is not much work if I keep a feature flag.
I've used Requesty because I can pin providers and write my own routing policy. That at least makes behavior more predictable.
I found OpenRouter credits burn much faster than I expected. I wanted more analysis of actual cost.
I tried blocking providers that collect data and saw odd behavior after filtering the defaults. I now think I need to whitelist providers I have tested.
Filtering to OpenRouter's "trusted" providers does not solve the problem. Their performance still varies by model and is not consistent over time.
I think the post puts numbers on what looked like a lot of lightly managed hosting. Providers differ in hardware availability, operational competence, and scruples.
I put $100 into OpenRouter to try models, but I will probably use the original provider after I decide which one I want.
I would spend those credits before they expire. OpenRouter deletes credits after a year even if I am still using the account.
I have found that strict JSON output also fails on some endpoints. I have to test hosts one by one and whitelist the ones that actually follow the format.
I stopped using OpenClaw with OpenRouter because identical prompts produced inconsistent results. I had blamed OpenClaw, not differences between providers.
I have seen reports that a leaked API key bypassed a $10 daily limit and spent $100 from Singapore. I also do not see enough API-key controls such as country or IP restrictions.
I have never had that billing-limit problem. I set and hit OpenRouter's limits regularly, and I would want to see support's postmortem before drawing conclusions.
I use pinned providers or presets, so I can change routing in OpenRouter without updating my app. Pinning is straightforward.
I think that misses the article's point: the author pinned both model and provider, and still found bad behavior from some hosts.
I pin one vetted provider, but I still find a gateway useful because I do not want to manage credentials, balances, and tokens across many vendors.