Hugging Face now routes its LLM calls through OpenRouter
SummaryHugging Face switched Inference Providers from its own router to OpenRouter's. Same token, same API, a provider picked per request, and retries when one fails. One breaking change: your own provider keys no longer work for chat models. Not tested by MODEL.
· MODEL Editors · 2 min read
Some links may be affiliate links. Disclosure

What changed. On Nov. 16, Hugging Face said (opens in a new tab) it is switching Inference Providers from its own custom router to OpenRouter's. Requests to language models now go through OpenRouter, which picks a provider for each call based on live price, speed and reliability, and retries on another provider if the first one fails. Hugging Face says your code stays the same.
How you use it. You keep your Hugging Face token and the same endpoint. The router supports OpenAI's Chat Completions and Responses APIs and Anthropic's Messages API for every chat model, and Hugging Face posted setup guides for Claude Code, Codex, OpenCode, Pi and Hermes Agent. You can still steer routing with a suffix on the model id: :fastest, :cheapest, or a provider name such as :novita. Routing is cache-aware, so a conversation stays on the provider holding its prompt cache; you can make that explicit with an X-HF-Session-Id header.
What you can see. Model pages get two new tabs. Providers lists every provider OpenRouter can route a model to, with input and output price, speed and 24-hour uptime. Metrics shows the best price, throughput, time to first token, context length and uptime among them. Your usage page breaks spend down by provider, and you can switch off any provider you don't want, for yourself or for an organization.
Price. Hugging Face says pricing doesn't change: you pay the provider's price on your Hugging Face bill with no Hugging Face markup. PRO users get $2 of credits a month; Team and Enterprise organizations get $2 per seat.
Who it's for. Developers and coding-agent users who run open-weight models and want one token and one API across many hosts, with automatic failover.
The catch. It is a breaking change for anyone who brought their own provider key. Language-model requests are now billed to your Hugging Face account, so you can no longer use your own API key for a provider with these models. Custom keys for image and video providers keep working, and image, video and audio generation do not go through OpenRouter. Hugging Face calls this the first step; connecting an OpenRouter account to Hugging Face is listed as coming next.
The MODEL take. Automatic retries across providers fix a real annoyance of the old setup, which returned the error if the one chosen provider failed. If you relied on your own provider key for chat models, check your setup today.
Not tested by MODEL. Not sponsored. No affiliate links.
Get three tested tools every Friday
Free, weekly. Unsubscribe anytime.
Sources
Keep reading

Hot take
Google caught a fully automated AI attack. It didn't need a zero-day. It read the patch.
Google's latest AI Threat Tracker describes exploit_agent, a multi-agent system that diffs web software before and after each patch, drafts an exploit and runs it with no human in the loop. The same report counts hundreds of AI-written exploits that don't work. Our take: sloppy AI code now hits defenders from both sides.
· MODEL Editors

Builder tip
Amazon caught AI agents hunting exposed LLM gateways for API keys. Lock yours down.
Amazon's decoy sensors captured attacker AI agents' own campaign records: they scanned for exposed LiteLLM, One API, Dify and similar apps, pulled the provider keys inside, and used stolen keys to pay for more hunting. Every technique was old. Here's the checklist.
· MODEL Editors

xeet
xeet renders X posts to PNG without a browser
Guillermo Rauch's new open-source tool rebuilds X's post layout in Rust and WebAssembly, so apps, agents and CI jobs can preview a post as an image in milliseconds instead of screenshotting headless Chrome. Not tested by MODEL.
· MODEL Editors

The test
Modern Web Guidance 1.0, tested: Google's legacy-code scanner caught 1 of 4 old patterns
We ran the free legacy-scan from Chrome's Modern Web Guidance on our own Next.js site and on a small file of old-school front-end code we wrote on purpose. It is fast, offline and costs no tokens. It also misses most of what a human reviewer would flag, which Google says up front.
· MODEL Editors
FREE · EVERY WEEK
The top AI tools this week, tested.
Every week MODEL's editors pick the AI tools worth your time, try them hands-on, and tell you what's good, what's not, and who it's for. Free, in your inbox.
Free. Unsubscribe anytime. Our picks are editorial and can't be bought.