> ## Documentation Index
> Fetch the complete documentation index at: https://docs.llmgrid.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Tag Management

> Create and manage tags to control model access, apply budgets, and support routing and cost attribution.

## Overview

The **Tag Management** page allows administrators to define and manage tags that can be attached to requests. Tags enable fine‑grained governance by restricting model access, applying budget controls, and supporting routing and cost attribution across the platform.

Tags are evaluated dynamically at request time and can be used independently or in combination with virtual keys, budgets, and routing rules.

***

## Tags List

The main Tags page displays all configured tags for the tenant.

### Primary Actions

* **Create New Tag**\
  Opens the tag creation dialog.

***

### Tags Table

Each row represents a configured tag.

**Columns include:**

* **Tag Name**\
  Unique identifier of the tag. Clicking the name opens tag details.
* **Description**\
  Human‑readable description of the tag’s purpose.
* **Allowed Models**\
  Models that requests with this tag are permitted to access.
* **Created**\
  Date the tag was created.
* **Actions**\
  Edit or delete the tag.

If no tags exist, the table will appear empty until a tag is created.

***

## Create New Tag

Select **Create New Tag** to define a new tag.

### Required Fields

#### Tag Name

A required identifier used in requests to reference the tag.

Tag names should be concise and descriptive, as they may be passed dynamically in client requests.

***

### Optional Fields

#### Description

A description explaining the purpose of the tag, such as:

* Client classification
* Request context
* User‑agent or integration metadata

***

### Allowed Models

Select which models are allowed when this tag is present on a request.

If no models are selected, the tag does not restrict model access.

This allows tags to act as **model allowlists** for specific traffic types.

***

## Budget & Rate Limits (Optional)

Tags can optionally enforce usage limits.

### Max Budget

Defines a maximum usage budget associated with the tag.

This is useful for:

* Limiting spend for tagged workloads
* Segmenting usage patterns

### Reset Budget

Controls whether and when the budget resets.

If not set, the budget does not reset automatically.

***

### Rate Limits Note

TPM (tokens per minute) and RPM (requests per minute) limits are **not currently supported** for tags.

If this capability is required, the UI provides a link to request the feature.

***

## Create Tag Action

Select **Create Tag** to save the tag.

Once created, the tag becomes immediately available for use in requests and routing logic.

***

## How Tags Are Used

Tags can be applied dynamically in requests to:

* Restrict which models can be used
* Enforce budget limits
* Support tag‑based routing
* Attribute usage and cost
* Identify traffic sources or request context

Tags do not directly control authentication and are typically used in combination with virtual keys and budgets.

***

## Common Use Cases

* Segment traffic by client, integration, or environment
* Restrict expensive models for specific workloads
* Track and limit usage by request context
* Support cost attribution and reporting
* Enable tag‑based routing strategies

***

## Best Practices

* Use clear, consistent naming conventions
* Keep tag purpose narrowly scoped
* Apply model restrictions when needed for governance
* Use budgets on tags for coarse‑grained spend control
* Combine tags with virtual keys for layered enforcement
* Review and clean up unused tags periodically

***

## Related Sections

* **Router Settings** – Configure tag‑based routing
* **Budgets** – Enforce usage limits
* **Usage** – Analyze usage by tag
* **Cost Tracking** – Attribute cost using tags
* **Virtual Keys** – Control authentication and access
*