Skip to main content
Usage exports are available to workspace administrators and provide up to 12 months of historical data across users, agents, API keys, projects, and models.

Accessing Usage Exports

You can export usage in the Langdock UI or programmatically with the Usage Export API. To export from the UI, navigate to your workspace analytics page and click the Export button in the top right corner.
1

Open Analytics

Go to your workspace analytics page in workspace settings.
2

Click Export

Select the Export button located in the top right corner
3

Configure Export

Choose your data type and date range in the export dialog
4

Generate CSV

Click Generate CSV to create and download your export file

Export Configuration

Data Types

Select which type of usage data to export:
  • Users - Individual user activity, message counts, and feature usage across the selected time period
  • Agents - Agent usage statistics, interaction counts, and performance metrics
  • API keys - API usage and cost grouped by API key
  • Projects - Project-level usage data
  • Models - Model usage statistics, request counts, and BYOK token consumption data

Date Range Options

Choose from predefined ranges or select a custom period:
  • This month (e.g., July 2025)
  • Last month (e.g., June 2025)
  • This week (e.g., July 30 - August 2)
  • Last week (e.g., July 20 - July 26)
  • Choose custom range - Select specific start and end dates
Historical data is limited to 12 months. You cannot export data older than 12 months from the current date.

Export Data Structure

Each export generates a CSV file with one row per entity for the selected time period.
Some columns are only available for workspaces using Bring Your Own Key (BYOK). These are marked as BYOK workspaces only.

Usage Exports

The Users export provides individual user activity across the selected period.
For workspaces with user-level data disabled, certain identifying columns (like user email and name) are excluded from exports to maintain privacy compliance.

Column Definitions

ColumnDescription
period_startStart date of the report (YYYY-MM-DD, UTC)
period_endEnd date of the report (YYYY-MM-DD, UTC)
org_idID of the workspace
user_idID of the user
nameName of the user
emailEmail of the user
roleUser role at the time of export
joined_atDate the user joined the workspace
departmentUser department
company_nameUser company name
license_typeCurrent user license tier
payg_limit_currentCurrent extra-usage limit
payg_consumption_in_periodExtra-usage consumption in the selected period
payg_utilization_pct_currentpayg_consumption_in_period / payg_limit_current
messages_totalTotal messages sent by the user
messages_total_rankRank by total messages
messages_chatMessages sent in regular chats
messages_chat_rankRank by chat messages
messages_assistantsMessages sent to agents
messages_assistants_rankRank by agent messages
assistants_messagedNumber of distinct agents messaged
assistants_to_messagesJSON mapping agent ID to message count
messages_projectsMessages sent to projects
messages_projects_rankRank by project messages
projects_messagedNumber of distinct projects messaged
projects_to_messagesJSON mapping project ID to message count
model_to_messages_totalJSON mapping model name to message count
action_messagesMessages generated by actions
action_messagedNumber of distinct actions triggered
action_to_messagesJSON mapping action name to message count

Additional Columns for BYOK Workspaces

ColumnDescription
total_input_tokensTotal input tokens consumed by the user
total_output_tokensTotal output tokens generated for the user
cached_prompt_tokensCache-read input tokens
cache_creation_tokensCache-write input tokens
no_cache_tokensInput tokens that were not served from cache
total_cost_usdEstimated provider cost in USD

Subgroup Rows

In the export dialog, use Subgroup rows to split each user into one row per model they used. Choose No grouping to keep one row per user.When subgrouped by Model, ranking, JSON breakdown, and action columns are omitted, as is projects_messaged.

Actions Referenced in User Export

The following actions may appear in the action_to_messages column of the Users export:
Used to edit documents and code in a structured interface. Messages represent user prompts that trigger Canvas interactions (creation, querying, deletion).
Used to analyze uploaded documents, spreadsheets, and other file types. Messages represent user prompts that trigger file processing and analysis.
Used to run and test code in various programming languages. Messages represent user prompts that trigger code execution requests.
Actions from connected integrations (e.g., Hubspot_create_contact, Slack_send_message). Messages represent user prompts that trigger API calls to external services through Langdock integrations.

Data Handling and Privacy

Null Values

Empty or unavailable data fields are handled as follows:
  • Numeric fields: Display as 0 or empty
  • Text fields: Display as empty strings
  • JSON objects: Display as empty objects {}

Data Retention

  • Historical data is available for up to 12 months
  • Export data reflects the state at the time of export
  • User roles, names, and other attributes show values as of the period end date