Export model usage data
Usage Export API
Export Model Usage
API endpoint to export AI model usage data including request counts and BYOK token consumption
POST
Export model usage data
For details on prerequisites and rate limits, please refer to the main Usage Export API documentation.
Langdock intentionally blocks browser-origin requests to protect your API key and ensure your applications remain secure. For more information, please see our guide on API Key Best Practices.
Data Included
By default, the model export returns one row per normalized model name, provider, and BYOK state.| Column | Description |
|---|---|
period_start | Start date of the report |
period_end | End date of the report |
org_id | ID of the workspace |
name | Normalized model name |
provider | Model provider |
bring_your_keys | Whether usage came from a BYOK model |
requests | Number of requests |
Additional Columns for BYOK Workspaces
| Column | Description |
|---|---|
sum_prompt_tokens | Total input tokens |
sum_completion_tokens | Total output tokens |
sum_cached_prompt_tokens | Cache-read input tokens |
sum_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 |
Because BYOK workspaces supply their own model keys, Langdock can provide you with an export of your token consumption data.
Grouped Export
Usegroup_by=source to return one row per model and source, such as WEB or MOBILE.
BYOK workspaces can also use group_by=deployment to return one row per model and deployment.
Usage Analysis
With this export you can:- Calculate costs using your provider’s pricing
- Identify which models receive the most requests
- Track usage trends over time
- Optimize model selection for different use cases
Authorizations
API key as Bearer token. Format "Bearer YOUR_API_KEY"
Body
application/json