Hugging Face and OpenRouter partner to route open-weight models
Hugging Face and OpenRouter are teaming up to make open-weight models easy to run. Every major open-weight release is published on the Hugging Face Hub, and OpenRouter serves those models at scale, routing each request across 80+ providers based on live measurements of each one. Together, every open-weight model on the Hub that a provider serves can be called with a Hugging Face token, through the same API, with the best provider picked for each request.
Today, Hugging Face is switching Inference Providers from its own custom router to OpenRouter's. Requests made to language models now go through OpenRouter, which picks the best provider for each call based on live price, speed and reliability, and retries on another provider if the first one fails. User code stays the same.
The router supports OpenAI's Chat Completions and Responses APIs and Anthropic's Messages API for every chat model, whatever the provider behind it. Setup guides are available for Claude Code, Codex, OpenCode, Pi and Hermes Agent.
The same Hugging Face token also gives users storage with Storage Buckets, compute with Jobs and dedicated inference with Inference Endpoints. PRO, Team and Enterprise plans include monthly credits for compute and inference.
On OpenRouter, open-weight models went from 26.8% of the tokens served in October 2025 to 71.7% at the end of September 2026, after peaking at 77.5% in July, according to OpenRouter in October 2026. Over the same period, weekly open-weight volume grew more than 60-fold, against almost tenfold for closed models. This week, the most used model on OpenRouter is an open-weight one, DeepSeek V4.1 Flash 1017, with 59.2 trillion tokens.
OpenRouter serves more than 800 trillion tokens a month to over 10 million users, across 600+ models from 80+ providers. Its routing is based on live measurements of every provider across that traffic.
OpenRouter recently rebuilt its provider routing: instead of only looking at the lowest list price, it sends each request to the provider with the best mix of price, speed and reliability. When a provider slows down or starts failing, traffic moves away from it until it recovers, and a failed try is retried on the next best provider inside the same call. In OpenRouter's measurements, the new routing cut capacity errors by 46% and improved time to first token by 16.9% and throughput by 16.3%.
Before, Inference Providers picked one provider for a request and returned its error if it failed. Now, the request is retried on another provider. Users can still choose a policy or a provider with a suffix on the model id:
zai-org/GLM-5.3 # default: best mix of price, speed and reliability zai-org/GLM-5.3:fastest # highest throughput zai-org/GLM-5.3:cheapest # lowest price zai-org/GLM-5.3:novita # only Novita
Routing is also cache-aware: a conversation stays on the provider that holds its prompt cache. To make it explicit, users can send a stable UUID per conversation in the X-HF-Session-Id header.
Pricing doesn't change: users pay the provider's price on their Hugging Face bill, and Hugging Face doesn't add a markup on top of it. PRO users get $2 of credits every month, and Team and Enterprise organizations get $2 per seat.
Image, video and audio generation continue to work exactly as before, directly through Hugging Face Inference Providers without going through OpenRouter. Users can keep using the same token and API, and access tens of thousands of LoRAs.
On model pages, users can chat with the model right away in the widget. Two new tabs show what's behind it: Providers lists every provider OpenRouter can route the model to, with its input and output price, speed and uptime over the last 24 hours, and Metrics shows the best price, throughput, time to first token, context length and uptime among them. A usage overview breaks spend down by the provider each request went to.
In settings, users can turn off any provider they don't want: the router never sends requests there. Organizations have the same settings, and they apply to every request billed to the organization.
Requests to language models now go through OpenRouter and are billed to the user's Hugging Face account or organization, so users can no longer use their own API key for a provider with these models. Users can still pick a provider with a suffix on the model id or turn providers off in settings, and code stays the same. Custom keys for image and video providers keep working.
This is the first step of the partnership with OpenRouter. Next: connect an OpenRouter account to Hugging Face, and route more tasks through OpenRouter.
Sources
This article was drafted with AI assistance and checked against the sources above. Company claims are reported as claims. Cover image is AI-generated.


