# Getting 429 Error for sentence-transformers/all-mpnet-base-v2

**URL:** <https://discuss.huggingface.co/t/getting-429-error-for-sentence-transformers-all-mpnet-base-v2/107670>\
**Category:** Beginners\
**Created:** [September 21, 2024, 9:20pm UTC](https://discuss.huggingface.co/t/getting-429-error-for-sentence-transformers-all-mpnet-base-v2/107670 "2024-09-21T21:20:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shashank47](https://avatars.discourse-cdn.com/v4/letter/s/9fc348/32.png) [@Shashank47](https://discuss.huggingface.co/u/Shashank47)\
**Post date:** [September 21, 2024, 9:20pm UTC](https://discuss.huggingface.co/t/getting-429-error-for-sentence-transformers-all-mpnet-base-v2/107670/1 "2024-09-21T21:20:54Z")

</div>

Hi Everyone,

I faced this rate limit error for the first time for sentence-transformers.  
429 Client Error: Too Many Requests for url: [https://api-inference.huggingface.co/pipeline/feature-extraction/sentence-transformers/all-mpnet-base-v2](https://api-inference.huggingface.co/pipeline/feature-extraction/sentence-transformers/all-mpnet-base-v2)

Anyone else faced this? How we can avoid this error?

---

<div class="post-metadata">

**Author:** ![meganariley](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/meganariley/32/56966_2.png) [@meganariley](https://discuss.huggingface.co/u/meganariley)\
**Post date:** [September 23, 2024, 8:40pm UTC](https://discuss.huggingface.co/t/getting-429-error-for-sentence-transformers-all-mpnet-base-v2/107670/2 "2024-09-23T20:40:49Z")

</div>

Hi @Shashank47 Rate limits for the Inference API (serverless) reset periodically. [PRO](https://huggingface.co/subscribe/pro) / [Enterprise](https://huggingface.co/enterprise) organization accounts receive higher rate limits for our serverless inference.

The free Inference API is a solution to easily explore and evaluate models, and [Inference Endpoints](https://huggingface.co/docs/inference-endpoints/index) is our paid inference solution for production use cases. For larger volumes of requests, or if you need guaranteed latency/performance, we recommend using Inference Endpoints instead to easily deploy your models on dedicated, fully-managed infrastructure. Inference Endpoints will give you the flexibility to quickly create endpoints on CPU or GPU resources, and is billed by compute uptime vs character usage. Further pricing information can be found [here](https://huggingface.co/docs/inference-endpoints/pricing).
