# Inference Providers billing issue - flat $0.01/request

**URL:** <https://discuss.huggingface.co/t/inference-providers-billing-issue-flat-0-01-request/178135>\
**Category:** Inference Endpoints on the Hub\
**Created:** [July 23, 2026, 3:14am UTC](https://discuss.huggingface.co/t/inference-providers-billing-issue-flat-0-01-request/178135 "2026-07-23T03:14:44Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![quangthien27](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/quangthien27/32/61858_2.png) [@quangthien27](https://discuss.huggingface.co/u/quangthien27)\
**Post date:** [July 23, 2026, 3:14am UTC](https://discuss.huggingface.co/t/inference-providers-billing-issue-flat-0-01-request/178135/1 "2026-07-23T03:14:44Z")

</div>

Hi, I think there’s a bug with Inference Providers billing. For the last 2 days, every request is being charged a flat $0.01, regardless of model or actual usage. Screenshots of the last 2 days attached showing the pattern. Anyone having same issue?

 ![image (4)](https://us1.discourse-cdn.com/hellohellohello/original/3X/6/c/6c66becf00217c5497392b92eeadc1c6149c5756.png)

 ![image (5)](https://us1.discourse-cdn.com/hellohellohello/original/3X/f/6/f620b1a5791116397b662e6120f3b75da86525ab.png)

 ![image (6)](https://us1.discourse-cdn.com/hellohellohello/original/3X/0/6/063beb851edce2dc19a2c550d075ce6d0ca9621d.png)

---

<div class="post-metadata">

**Author:** ![Jonezia](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@Jonezia](https://discuss.huggingface.co/u/Jonezia)\
**Post date:** [July 24, 2026, 2:44pm UTC](https://discuss.huggingface.co/t/inference-providers-billing-issue-flat-0-01-request/178135/2 "2026-07-24T14:44:51Z")

</div>

Think I’m also getting this bug.  
I just started using inference providers  
13 requests with Qwen2.5-Coder-32B-Instruct cost $0.09  
and 15 requests with Qwen2.5-Coder-7B-Instruct cost $0.10  
The requests are very simple  
I recorded the input/output tokens for all the requests  
e.g. for the last 32B API call I have 313 input tokens, 143 output tokens, calculated cost:  
(313/1e6)\*0.06 + (143/1e6)\*0.20 = $0.0000188 + $0.0000286 = $0.0000474  
and all of the requests are quite similar, so 15 requests shouldn’t be costing $0.10  
In particular the 7B model was running on the same dataset and same prompts, and should cost even less than the 32B model

---

<div class="post-metadata">

**Author:** ![Jonezia](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@Jonezia](https://discuss.huggingface.co/u/Jonezia)\
**Post date:** [July 24, 2026, 7:22pm UTC](https://discuss.huggingface.co/t/inference-providers-billing-issue-flat-0-01-request/178135/3 "2026-07-24T19:22:15Z")

</div>

A little strange - the prices seem to have corrected themselves on the billing page after a couple hours.  
But then I tried making more API calls, and the new batch of API calls costs $0.01 per request.  
And it seems like even if the billing page corrects itself after a while, the limits based on your budget are based on the $0.01 per request.

---

<div class="post-metadata">

**Author:** ![quangthien27](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/quangthien27/32/61858_2.png) [@quangthien27](https://discuss.huggingface.co/u/quangthien27)\
**Post date:** [July 24, 2026, 9:47pm UTC](https://discuss.huggingface.co/t/inference-providers-billing-issue-flat-0-01-request/178135/4 "2026-07-24T21:47:06Z")

</div>

Yea, that seems to be the case. It’s a bit frustrated though cause there’s no indication on the chart to explain the cost will correct itself, maybe a bit of UX improvements needed there.

Anw, here’s reply from support, I ll keep monitoring though:

“When you send a request, a placeholder price is charged instantly so usage shows up right away in your billing settings. Later, we’ll update the total charges with the real per-request cost from the provider, and we’ll also ensure unsuccessful calls aren’t billed.

The best metric to gauge your real-time inference billing is the number of remaining credits you have.”

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\
**Post date:** [July 25, 2026, 11:34pm UTC](https://discuss.huggingface.co/t/inference-providers-billing-issue-flat-0-01-request/178135/5 "2026-07-25T23:34:45Z")

</div>

Maybe or must be a bug…? @hysts @meganariley @michellehbn

---

<div class="post-metadata">

**Author:** ![hysts](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/hysts/32/32230_2.png) [@hysts](https://discuss.huggingface.co/u/hysts)\
**Post date:** [July 26, 2026, 2:18am UTC](https://discuss.huggingface.co/t/inference-providers-billing-issue-flat-0-01-request/178135/6 "2026-07-26T02:18:13Z")

</div>

Thanks for reporting this. I’ll check with the team internally.

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\
**Post date:** [July 26, 2026, 3:03am UTC](https://discuss.huggingface.co/t/inference-providers-billing-issue-flat-0-01-request/178135/7 "2026-07-26T03:03:18Z")

</div>

Thank you!

---

<div class="post-metadata">

**Author:** ![Jonezia](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@Jonezia](https://discuss.huggingface.co/u/Jonezia)\
**Post date:** [July 28, 2026, 3:48pm UTC](https://discuss.huggingface.co/t/inference-providers-billing-issue-flat-0-01-request/178135/8 "2026-07-28T15:48:47Z")

</div>

Just checked and this seems to be working okay now. You still get charged $0.01 per query, but it self-corrects to the actual price in under a minute, much faster than before.  
The problem before is that if you wanted to run say 10,000 cheap queries you would have to have $100 in credits, even if they would cost much less. But this seems to be an okay solution, as long as your queries aren’t going too fast you won’t hit the limit.  
Thanks!
