Qwen/Qwen2.5-72B-Instruct
Served by Hugging Face through this free, OpenAI-compatible gateway. Pin it by name, or let the router pick it.
Model id to send
huggingface/Qwen/Qwen2.5-72B-Instruct
Sending the bare name Qwen/Qwen2.5-72B-Instruct
works too, and lets the router use any provider that serves it. The
huggingface/ prefix pins this one.
Too little traffic through this pairing in the last 30 days to publish a median that would mean anything. Figures appear here once it has served enough requests to be worth quoting.
Call it
curl https://dreamprompting.com/api/v1/chat/completions \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "huggingface/Qwen/Qwen2.5-72B-Instruct",
"messages": [{"role":"user","content":"Hello!"}]
}'from openai import OpenAI
client = OpenAI(base_url="https://dreamprompting.com/api/v1",
api_key="YOUR_API_KEY")
r = client.chat.completions.create(
model="huggingface/Qwen/Qwen2.5-72B-Instruct",
messages=[{"role": "user", "content": "Hello!"}],
)
print(r.choices[0].message.content)Get a free key, or try it with no account in the playground. Full parameters are in the API docs.
What happens when it is busy
Free tiers run out. When Hugging Face rate limits this model, the router moves to the
next provider in the chain and the request still answers, from a different model.
Send "allow_fallback": false to refuse the
substitution and get an error instead, which is what you want if your application announces which model it
is using.
If you would rather not share the allowance at all, add your own Hugging Face key: requests then run on your account, with no daily quota. See pricing.
Same model, other providers
The same weights are reachable through more than one upstream here, at different speeds and different limits. This is exactly what the router chooses between.