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.Open Analytics
Go to your workspace analytics page in workspace settings.
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
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
- Users
- Agents
- API Keys
- Projects
- Models
The Users export provides individual user activity across the selected period.
Column Definitions
| Column | Description |
|---|---|
period_start | Start date of the report (YYYY-MM-DD, UTC) |
period_end | End date of the report (YYYY-MM-DD, UTC) |
org_id | ID of the workspace |
user_id | ID of the user |
name | Name of the user |
email | Email of the user |
role | User role at the time of export |
joined_at | Date the user joined the workspace |
department | User department |
company_name | User company name |
license_type | Current user license tier |
payg_limit_current | Current extra-usage limit |
payg_consumption_in_period | Extra-usage consumption in the selected period |
payg_utilization_pct_current | payg_consumption_in_period / payg_limit_current |
messages_total | Total messages sent by the user |
messages_total_rank | Rank by total messages |
messages_chat | Messages sent in regular chats |
messages_chat_rank | Rank by chat messages |
messages_assistants | Messages sent to agents |
messages_assistants_rank | Rank by agent messages |
assistants_messaged | Number of distinct agents messaged |
assistants_to_messages | JSON mapping agent ID to message count |
messages_projects | Messages sent to projects |
messages_projects_rank | Rank by project messages |
projects_messaged | Number of distinct projects messaged |
projects_to_messages | JSON mapping project ID to message count |
model_to_messages_total | JSON mapping model name to message count |
action_messages | Messages generated by actions |
action_messaged | Number of distinct actions triggered |
action_to_messages | JSON mapping action name to message count |
Additional Columns for BYOK Workspaces
| Column | Description |
|---|---|
total_input_tokens | Total input tokens consumed by the user |
total_output_tokens | Total output tokens generated for the user |
cached_prompt_tokens | Cache-read input tokens |
cache_creation_tokens | Cache-write input tokens |
no_cache_tokens | Input tokens that were not served from cache |
total_cost_usd | Estimated 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 isprojects_messaged.Actions Referenced in User Export
The following actions may appear in theaction_to_messages column of the Users export:
Canvas
Canvas
Used to edit documents and code in a structured interface. Messages represent user prompts that trigger Canvas interactions (creation, querying, deletion).
Web Search
Web Search
Used to search external web sources for real-time information. Messages represent user prompts that trigger web search functionality.
File Analysis
File Analysis
Used to analyze uploaded documents, spreadsheets, and other file types. Messages represent user prompts that trigger file processing and analysis.
Code Execution
Code Execution
Used to run and test code in various programming languages. Messages represent user prompts that trigger code execution requests.
Integration Actions
Integration Actions
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
0or 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