From 2674c492838f3dc7c0ff90dfb6e217fb1dcd9676 Mon Sep 17 00:00:00 2001 From: mubashir1osmani Date: Sat, 6 Sep 2025 21:59:45 -0400 Subject: [PATCH] added spend tags --- docs/my-website/docs/proxy/tag_routing.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/my-website/docs/proxy/tag_routing.md b/docs/my-website/docs/proxy/tag_routing.md index 23715e77f81..838b2a09d76 100644 --- a/docs/my-website/docs/proxy/tag_routing.md +++ b/docs/my-website/docs/proxy/tag_routing.md @@ -5,6 +5,12 @@ This is useful for - Implementing free / paid tiers for users - Controlling model access per team, example Team A can access gpt-4 deployment A, Team B can access gpt-4 deployment B (LLM Access Control For Teams ) +:::info +## See here for spend tags +- [Track spend per tag](cost_tracking#-custom-tags) +- [Setup Budgets per Virtual Key, Team](users) +::: + ## Quick Start ### 1. Define tags on config.yaml @@ -324,7 +330,4 @@ Here's how to set up and use team-based tag routing using curl commands: By following these steps and using these curl commands, you can implement and test team-based tag routing in your LiteLLM Proxy setup, ensuring that different teams are routed to the appropriate models or deployments based on their assigned tags. -## Other Tag Based Features -- [Track spend per tag](cost_tracking#-custom-tags) -- [Setup Budgets per Virtual Key, Team](users)