Request to Serverless Inference API failed with 400 status code

Cyfutureai
Mon, 28 Jul 2025 09:58:51 +0000

LinYouyIFAD:

I’m consistently encountering issues with the HuggingFace Serverless API, specifically with the hf-inference provider. When running the sample code on the HuggingFace serverless deployment page, I receive the following error:

openai.BadRequestError: Error code: 400 - {'error': 'Not allowed to request v1/chat/completions for provider hf-inference'}

I tried following models, all with the same status code:

meta-llama/Llama-3.3-70B-Instruct

deepseek-ai/DeepSeek-R1-Distill-Qwen-32B

deepseek-ai/DeepSeek-R1-Distill-Llama-70B

Does anyone have any ideas or suggestions on how to resolve this issue?

You’re not alone—this seems to be a common issue when using the HuggingFace Serverless API via the hf-inference provider. The error:

javascript

CopyEdit

openai.BadRequestError: Error code: 400 - {'error': 'Not allowed to request v1/chat/completions for provider hf-inference'}

usually indicates a mismatch between the API endpoint you’re hitting (v1/chat/completions, which is typically used with OpenAI-compatible providers) and the capabilities or expected format for the hf-inference provider.

The hf-inference provider doesn’t support the OpenAI-compatible chat endpoint (v1/chat/completions) directly. Instead, it expects payloads specific to Hugging Face’s inference API. You’ll need to adapt your code to match Hugging Face’s format or use an OpenAI-compatible provider that supports the /v1/chat/completions endpoint properly.

If you’re looking for a smooth, OpenAI-compatible experience with models like LLaMA or DeepSeek, you might want to try Cyfuture AI. They offer OpenAI-compatible APIs for several high-performing open-source models (like LLaMA 3 and DeepSeek) and can be a great drop-in alternative if you’re running into provider limitations with Hugging Face.

Let me know if you need help modifying your code for Hugging Face or switching providers—happy to share examples.