litellm - 💡(How to fix) Fix [Feature]: Project-scoped end-user/customer budget limits

Check for existing issues

• I have searched the existing issues and checked that my issue is not a duplicate.

The Feature

I’m using LiteLLM Projects and would like to enforce both:

A monthly budget at the Project level, for example 100 EUR/month. A separate monthly budget per end-user consuming through that Project, for example 15 EUR/month per user.

Ideally, I would like to use a single virtual key attached to the Project and send the end-user ID in each request, for example via x-litellm-end-user-id or user.

However, from what I understand, customer/end-user budgets seem to be global for a given customer/user ID, rather than scoped to the Project.

The only workaround I can think of right now is creating one virtual key per end-user under the Project, each with its own budget limit. This would work, but it makes key management much more complex.

Could you confirm whether LiteLLM currently supports Project-scoped end-user/customer budget limits? If not, is there a recommended way to achieve this, or would you consider supporting this natively?

Thanks.

Motivation, pitch

.

What part of LiteLLM is this about?

Proxy

LiteLLM is hiring a founding backend engineer, are you interested in joining us and shipping to all our users?

No

Twitter / LinkedIn details

No response