Token Event Fields
| Field | Description |
|---|---|
model | Model identifier used for the call |
agentId | Agent that performed the work |
gatewayId | Gateway that routed the call |
inputTokens | Tokens sent to the model |
outputTokens | Tokens generated by the model |
cachedTokens | Tokens served from prompt cache |
costCents | Computed cost at capture time |
succeeded | Whether the call completed successfully |
timestamp | When the event was recorded |
Cost Aggregation
Token events roll up into hourly, daily, weekly, and monthly buckets. Filter by gateway, agent, model, workflow, or time range. Scheduled crons compute aggregates — hourly rollups run every hour, daily rollups every 24 hours, and a weekly compaction job consolidates older buckets.
Model Economics
Per-model cost comparison showing input vs output pricing, average cost per request, and volume distribution across models. The model registry stores per-1M-token rates for each model/gateway combination. Cost is computed at capture time and the pricing snapshot is stored on the event for audit.Token Attribution
Each event is attributed through two parallel hierarchies. The task chain traces cost through the execution hierarchy: token → task → workflow → project. The worker chain traces cost through the organizational hierarchy: token → worker → team → department. Both chains originate from the same token event record. See Budgets for the full hierarchy.
In Burgundy: Explore cost data in the analytics dashboard. →