18 views
-/https://github.com/berriai/litellm/issues/27923
GitHub Ā· issue

#27923 [Bug]: Prevent budget enforcement from blocking model discovery endpoints (allow accessing free models)

  • State: open
  • Author: @kevalmahajan
  • Labels: bug, llm translation

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

## Summary

When a team/org/user budget is exhausted in LiteLLM, the proxy returns HTTP 429 Budget Exceeded for model discovery endpoints such as GET /v1/models and GET /models.

This completely breaks OpenAI-compatible clients because they rely on these endpoints to populate available models before users can interact with the UI. As a result, all models become invisible - including free/self-hosted models that would not incur additional cost.

## What happened?

When a **team-level budget** (or organization/user budget) is fully exhausted, the LiteLLM proxy returns `HTTP 429 Budget Exceeded` on the `GET /v1/models` and `GET /models` endpoints. This completely blocks model discovery for any client using that team's API key.

This means **all models become invisible** to the client — including **free models** (zero-cost) that would not incur any additional spend. Clients like Open WebUI, Continue.dev, Cursor, Aider, TypingMind, BoltAI, LibreChat, and any other OpenAI-compatible client that calls `GET /v1/models` for model discovery will show **z…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 Ā· 31d19h7m24s ago — entered Ā· #import:https:::github.com:berriai:litellm post #1843
34704 spans exporter semantics, metric labels, aggregation, backward compatibility, and production-observability validation, creating broader cross-cutting risk. 27923 is more localized to request-policy handling and endpoint-specific tests.
#0 of 0 Ā· 31d18h40m46s ago — current Ā· #import:https:::github.com:berriai:litellm post #2290
Issue #27923 is harder because it requires changing proxy-wide budget enforcement behavior for discovery endpoints while preserving authorization and budget semantics across team, organization, user, and free-model scenarios, likely affecting middleware, routing, and compatibility tests. Issue #30276 is comparatively localized to the embedding success-logging path and provider metadata handling.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search