API Usage Export
Export detailed API key usage data to CSV format for cost analysis, monitoring, and billing reconciliation.
API Usage Export
Export detailed API key usage data to CSV format for cost analysis, monitoring, and billing reconciliation.
API usage exports are available to workspace administrators and provide detailed cost breakdowns for each API key over your selected time period.
- Open API Settings — View analytics and export usage data for your API keys.
Accessing API Usage Export
Navigate to your API settings page to view analytics and export detailed usage data for your API keys.
Go to **Settings > API** in your workspace settings
Review the API key analytics displayed on the page
Choose your desired time frame from the timeframe selector (default: last 30 days)
Click the **Export** button to download a CSV file with detailed API usage data
Time Period Selection
The export includes all API calls made within the selected timeframe:
- Default period: Last 30 days
- Custom ranges: Select any timeframe using the timeframe selector
- Data is filtered based on the date/timestamp of each API call
The same timeframe selection applies to both the analytics visualization and the CSV export.
Aggregated API Key Usage Export
The export from the API settings page is a detailed, per-call CSV export. Use it when you need to reconcile individual API requests, inspect model prices, or analyze latency.
If you need a summarized report instead, export API keys from the workspace analytics export dialog, or use the API key usage export in the Usage Export API. It returns one row per API key for the selected period and can also be subgrouped by model.
Export Data Structure
The CSV export contains one row per API call with detailed cost and performance information.
Column Definitions
| Column | Description |
|---|---|
| Date | Date and timestamp of the API call (UTC) |
| API Key ID | Unique identifier of the API key used |
| API Key Name | Human-readable name of the API key |
| Provider | AI provider used for the request |
| Model | Specific model name |
| Input Tokens | Number of tokens in the request prompt |
| Output Tokens | Number of tokens in the model's response |
| Completion Time (ms) | Time taken to complete the request in milliseconds |
| Input Token Price (USD/1M tokens) | Cost per 1 million input tokens |
| Output Token Price (USD/1M tokens) | Cost per 1 million output tokens |
| Gross Cost (USD) | Customer-facing cost for the API call in USD |
| Billed Amount (EUR) | Amount billed for the API call in EUR |
The export includes both completion and embedding API calls. For embedding calls, the Output Tokens column will be empty.
Calculating Costs
What is a token? A token is a piece of text (roughly a word or word fragment) that the model processes. On average, 1 token equals about 4 characters. API call pricing is based on the number of tokens processed.
To calculate the cost of an individual API call, use the following formula:
Total Cost = (input_tokens × input_token_price_per_1m / 1,000,000) +
(output_tokens × output_token_price_per_1m / 1,000,000)
Example Calculation
For an API call with:
- 500 input tokens
- 1,200 output tokens
- Input price: $2.50 per 1M tokens
- Output price: $10.00 per 1M tokens
Input Cost = 500 × $2.50 / 1,000,000 = $0.00125
Output Cost = 1,200 × $10.00 / 1,000,000 = $0.01200
Total Cost = $0.01325
To calculate the total cost for an API key, sum the individual costs across all rows for that key in your spreadsheet application.
Use Cases
Cost Monitoring
Track spending across different API keys to identify high-usage keys and optimize costs.
Billing Reconciliation
Reconcile API usage with invoices and verify charges from AI providers.
Performance Analysis
Analyze completion times across different models and providers to optimize response times.
Usage Patterns
Identify peak usage times and model preferences to inform capacity planning.
Export Limits
Exports are limited to 1,000,000 rows. If your export exceeds this limit, narrow your date range.
Data Privacy
- API key IDs and names are included for administrative visibility
- No end-user personal information is included in API usage exports
- Data reflects actual API calls made through your workspace