Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.latitude.so/llms.txt

Use this file to discover all available pages before exploring further.

​
Token and cost tracking

Latitude aggregates token usage and estimated cost from each trace’s LLM spans. Use these fields to understand expensive interactions, compare models, and investigate behaviour that drives high usage.

​
What Latitude tracks

When the provider or framework instrumentation reports usage, Latitude shows:
  • input tokens
  • output tokens
  • total tokens
  • estimated cost
  • models used
  • providers used
Trace rows show aggregate token and cost values across their spans. Session rows aggregate usage across their traces.

​
Find expensive traces

Filter by token usage or cost to find:
  • high total cost
  • high input or output tokens
  • expensive traces for one model or provider
  • expensive traces within a tag, user, session, or metadata cohort
You can combine these filters with Search. For example, search for agent loops between tools and filter to traces above a cost threshold.

​
Where usage appears

Token and cost data appears in:
  • the Traces table
  • trace detail views
  • session aggregates
  • filters
  • search result rows
Cost values are estimates based on the usage and model/provider information available in telemetry.
  • Percentile cohorts: Compare cost and token usage against similar tagged traces
  • Traces: Trace-level usage and cost
  • Sessions: Session-level aggregation
  • Filters: Filter by cost and token usage
  • Search: Discover costly behaviours