GET /analytics/breakdown agent, tool, or tag
Query Parameters
Window start (RFC3339); defaults to 24h before until
Window end (RFC3339); defaults to now
Breakdown dimension (default model)
Value in
- "model"
- "provider"
- "status"
- "source"
- "app"
- "channel"
- "apiKey"
- "user"
- "agent"
- "tool"
- "eventType"
- "finishReason"
- "semanticKind"
- "service"
- "operation"
- "errorType"
- "tag"
Attribute key to group by when dimension=tag
Top-N entries (default 50, max 500)
int64Filter by event source (e.g. gateway)
Filter by request/response model
Filter by model provider
Filter by app id
Filter by channel id
Filter by environment id or slug
Filter by API key id
Filter by end-user id
Custom-dimension (attribute) key to filter on; pair with filterTagValue
Value for filterTagKey
Filter by service (resource service.name)
Filter by operation / span name
Filter by error type
Response Body
application/json
application/problem+json
curl -X GET "https://example.com/analytics/breakdown"{ "$schema": "https://example.com/schemas/BreakdownOutputBody.json", "dimension": "string", "rows": [ { "avgDurationMs": 0.1, "costUsd": 0.1, "errorCount": 0, "eventCount": 0, "inputTokens": 0, "key": "string", "outputTokens": 0, "totalTokens": 0 } ]}PATCH /v2/alerts/{alertRuleId} PATCH
Previous Page
GET /analytics/dimensions GET
Start here for custom-dimension analytics: this lists the business attribute keys your app has stamped on its telemetry (e.g. participant_role, tenant, plan). Feed a key into /analytics/breakdown?dimension=tag&tagKey=<key> to rank it, then into filterTagKey+filterTagValue on /analytics/timeseries and /analytics/latency to trend and get percentiles for one value.