Skip to content

Hugging Face Routes Inference Provider Requests Through OpenRouter

Hugging Face BlogFrom the source·· 1 day agoPicksHugging Face and OpenRouter join forces to make open-weight models easy to run
Original
Image: Hugging Face Blog
Who
Hugging Face
What
switched Inference Providers routing to OpenRouter for language model requests
Quote
Today, we are switching Inference Providers from our own custom router to OpenRouter's.

What happened

Hugging Face has switched Inference Providers’ language model requests to OpenRouter, which selects a provider based on live price, speed, and reliability measurements and retries with another provider if a request fails. Users can keep the same code and Hugging Face token, but can no longer use their own provider API keys for language models. Image, video, and audio generation continue to run directly through Hugging Face Inference Providers.

Why it matters

Language model requests can now retry through another provider when one fails, while users can still set routing preferences or disable providers. Users can no longer use their own provider API keys for these models.

Read next

See the full storyHugging Face Routes Language Model Requests Through OpenRouter

The story so far

Hugging Face has switched its Inference Providers' language model requests from its own custom router to OpenRouter, which selects a provider for each call based on live price, speed, and reliability measurements and retries with another provider if a request fails. Users can keep their existing code and Hugging Face token, though language model requests are now billed to their Hugging Face account or organization and can no longer use a user's own provider API keys. PRO users receive $2 in monthly credits, while Team and Enterprise organizations receive $2 per seat. Image, video, and audio generation continue to run directly through Hugging Face Inference Providers without going through OpenRouter.

This story is in 11/17 AI DailyRead the whole issue