Dynamic Tags Per Request
Leverage dynamic tags for reporting, billing, or feature tracking with custom tags sent per request.
The request_tags
parameter lets you add custom tags to each request, enabling dynamic tracking at the individual request level. It supports both flat and hierarchical formats, making it easy to organize usage data for reporting, cost allocation, team billing, feature usage, or environment segmentation. These tags are available in the dashboard as a filter and also in the meta data of the activity logs.
Parameter Type:
request_tags: [string]
What You Can Do with Tags:
Group and filter requests by project, team, environment, or feature
Organize usage reports using nested tag paths (e.g.,
team/feature/test
)Track granular usage without needing to manage multiple API keys
Tag Formats Supported
Flat Tag
["asia", "production"]
Simple, one-level tags
Hierarchical
["USA/NYC", "org/team/project"]
Path-style, nested classification
Mixed
[ "Asia", "UAE/Dubai" ]
Combine both types in the same request
Example Request
curl --location 'https://go.fastrouter.ai/api/v1/chat/completions' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer API-KEY' \
--data '{
"model": "openai/gpt-4o-mini",
"stream": false,
"messages": [
{
"role": "user",
"content": "What are some famous tourist attractions in London?"
}
],
"temperature": 0.0,
"request_tags": ["UK/London", "Europe"]
}'
Why Use Tags?
Team-level visibility: e.g.,
marketing/email-gen
Feature usage breakdown: e.g.,
feature/summary-widget
Cost attribution: e.g.,
customer/acme
,env/staging
Geo-based tracking: e.g.,
US/California/SF
,India/Mumbai
Last updated