Skip to content

docs: add per-tag rate limits documentation - #31855

Closed
devin-ai-integration[bot] wants to merge 1 commit into
litellm_internal_stagingfrom
litellm_per-tag-rate-limits-docs
Closed

docs: add per-tag rate limits documentation#31855
devin-ai-integration[bot] wants to merge 1 commit into
litellm_internal_stagingfrom
litellm_per-tag-rate-limits-docs

Conversation

@devin-ai-integration

Copy link
Copy Markdown
Contributor

Relevant issues

Documents the per-tag RPM limiting feature from #31502

Pre-Submission checklist

  • My PR passes all CI/CD checks (e.g., lint, format, unit tests)
  • My PR's scope is as isolated as possible; it only solves 1 specific problem

Screenshots / Proof of Fix

Screenshot of the Per-Tag Rate Limits editor in the key creation form, showing cell-1: 5 RPM and cell-2: 10 RPM:

per_tag_rate_limits_create_key

Type

📖 Documentation

Changes

Adds a documentation page (docs/proxy/per_tag_rate_limits.md) and UI screenshot for the per-tag RPM limiting feature introduced in #31502. The page covers:

  • Creating keys with tag_rpm_limit via /key/generate
  • Updating tag limits via /key/update
  • Sending tagged requests using x-litellm-tags header or request body metadata
  • Rate limit behavior (independent counters per tag, fallback to key-level limit)
  • UI walkthrough with screenshot of the tag rate limit editor

These files are intended for the litellm-docs repo (docs/proxy/ and img/ directories). The sidebars.js entry should be added under the "Budgets + Rate Limits" section, after proxy/tag_budgets

Link to Devin session: https://app.devin.ai/sessions/fafa21b563dc48adac7061db94aebcfc
Requested by: @yassin-berriai

Add documentation page explaining the per-tag RPM limiting feature
(PR #31502). Includes API examples for creating/updating keys with
tag_rpm_limit, UI screenshot of the tag rate limit editor, and usage
examples for sending tagged requests.

These files are intended for the litellm-docs repo (docs/proxy/ and
img/ directories)

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
@yassin-berriai yassin-berriai self-assigned this Jul 1, 2026
@devin-ai-integration

Copy link
Copy Markdown
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment, CI, and merge conflict monitoring

@greptile-apps

greptile-apps Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR adds a documentation page (docs/proxy/per_tag_rate_limits.md) and a UI screenshot (docs/img/per_tag_rate_limits_create_key.png) describing the per-tag RPM limiting feature introduced in #31502. The documentation content itself is clear and well-structured, but both files are committed to the wrong repository.

  • The PR description explicitly notes "These files are intended for the litellm-docs repo" — they need to be submitted there, not here.
  • The sidebars.js entry referenced in the PR description is also absent, though that addition would also belong in litellm-docs.

Confidence Score: 3/5

These are documentation-only files with no runtime risk, but both are being added to the wrong repository against the team's established policy.

The content cannot break any code, but the repo-placement policy is clear and the PR author is already aware of it (their own description says the files belong in litellm-docs). Merging as-is would leave stale docs files in this repo that could diverge from the canonical docs site.

Both docs/proxy/per_tag_rate_limits.md and docs/img/per_tag_rate_limits_create_key.png need to be removed from this repo and submitted to litellm-docs instead.

Important Files Changed

Filename Overview
docs/proxy/per_tag_rate_limits.md New documentation page for per-tag RPM limits — well-structured content but placed in the wrong repository; docs belong in litellm-docs, not this repo.
docs/img/per_tag_rate_limits_create_key.png Screenshot asset accompanying the new docs page — same wrong-repo placement issue as the markdown file.

Reviews (1): Last reviewed commit: "docs: add per-tag rate limits documentat..." | Re-trigger Greptile

Comment on lines +1 to +5
import Image from '@theme/IdealImage';
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';

# Per-Tag Rate Limits

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Documentation must live in the litellm-docs repo

This file (and docs/img/per_tag_rate_limits_create_key.png) should not be committed to this repo — documentation belongs in the separate litellm-docs repository. The PR description itself acknowledges this: "These files are intended for the litellm-docs repo." Please open a PR in litellm-docs instead and remove these files from this changeset.

Rule Used: Prevent documentation from being added - needs to ... (source)

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

@codecov

codecov Bot commented Jul 1, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@yassin-berriai

Copy link
Copy Markdown
Contributor

Closing in favor of BerriAI/litellm-docs#458, which moves this per-tag rate limits documentation into the litellm-docs repo where the docs site is built from. The page and screenshot have been ported there and wired into the Budgets + Rate Limits sidebar.

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants