DATUM

OpenRouter's single endpoint can route to providers with different behaviour

single source · 1 articles · capability · confidence: medium · first seen 2026-09-11 22:49 UTC

Developers using OpenRouter's single API endpoint may unknowingly receive different model behaviour depending on which backend provider serves the request. OpenRouter advertises automatic fallbacks and cost-effective routing, but providers run different serving software, optimisations and settings. As a result, the same model ID can behave inconsistently: some providers lack vision capability for vision models, and processing of reasoning effort varies. Users can force a specific provider with the `provider.only` option, and the `/endpoints` method lists available providers for a model ID. The issue affects anyone relying on OpenRouter's default routing for consistent model outputs. Mohamed Moustafa outlined these issues.

What this means for you

If you use OpenRouter for model inference, do not rely on default routing when consistency matters. Use `provider.only` to pin a provider, and check `/endpoints` to see which providers are available for your model.

Key facts

  • ·OpenRouter automatically routes requests to the most cost-effective provider with fallbacks. source
  • ·Different providers run different serving software, optimizations and settings, causing different behaviour for the same model endpoint. source
  • ·Some providers lack vision capability for vision models. source
  • ·Reasoning effort option processing can differ across providers. source
  • ·Users can force provider routing with the provider.only option. source
  • ·The /endpoints method returns the list of available providers for a specific model ID. source

What the sources say

  • Simon Willison (press) — Highlights Mohamed Moustafa's list of pitfalls from OpenRouter's automatic provider routing, with workarounds.

Sources

The original reporting. Follow these — they did the work.

← the wire