You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,11 +60,11 @@ npm run preview
60
60
3. The app will parse the report and compare request-based and AI Credits-based billing signals
61
61
4. Explore the visualizations and data views to preview how future bills may look after the AI Credits transition
62
62
63
-
Sample reports are available in the `examples/` directory. Older examples without `aiu_quantity` still load, but AI Credits will remain `0` for those rows.
63
+
Sample reports are available in the `examples/` directory. Older examples without `aic_quantity` still load, but AI Credits will remain `0` for those rows.
64
64
65
65
## CSV Report Format
66
66
67
-
The application expects CSV files with the following primary columns:
67
+
The application expects CSV files with the following required columns:
68
68
69
69
-`date` - ISO date (YYYY-MM-DD)
70
70
-`username` - GitHub username
@@ -81,9 +81,13 @@ The application expects CSV files with the following primary columns:
81
81
-`total_monthly_quota` - Monthly quota amount
82
82
-`organization` - Organization slug
83
83
-`cost_center_name` - Optional cost center identifier
84
-
-`aiu_quantity` - AI Credits for the same usage row
85
84
86
-
The viewer now supports both billing units. On `requests` rows, `quantity` and `applied_cost_per_quantity` drive PRU-based calculations, while `aiu_quantity` and `aiu_gross_amount` remain comparison values and stay `0` when those AI Credit fields are absent. On `ai-units` rows, Premium Requests and generic PRU gross/discount/net totals are counted as `0`; AI Credits are counted from the AI-specific credit fields (`aiu_quantity`, falling back to `quantity` only when the AI field is absent) and AI Credit gross cost comes from `aiu_gross_amount` (falling back to `gross_amount` only when the AI field is absent). Legacy token columns may still appear in older exports, but they are no longer used by the app.
85
+
Newer exports may also include these AI Credit columns:
86
+
87
+
-`aic_quantity` - AI Credits for the same usage row
88
+
-`aic_gross_amount` - AI Credit gross cost for the same usage row
89
+
90
+
The viewer now supports both billing units. On `requests` rows, `quantity` and `applied_cost_per_quantity` drive PRU-based calculations, while `aic_quantity` and `aic_gross_amount` remain comparison values and stay `0` when those AI Credit fields are absent. On `ai-units` rows, Premium Requests and generic PRU gross/discount/net totals are counted as `0`; AI Credits are counted from the AI-specific credit fields (`aic_quantity`, falling back to `quantity` only when the AI field is absent) and AI Credit gross cost comes from `aic_gross_amount` (falling back to `gross_amount` only when the AI field is absent).
87
91
88
92
See [docs/report-format.md](docs/report-format.md) for detailed format specifications.
Copy file name to clipboardExpand all lines: docs/report-format.md
+7-8Lines changed: 7 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
Source examples: files in `examples/`. Some existing sample exports still use the older token-oriented schema.
4
4
5
-
## Primary columns used by the app
5
+
## Required columns used by the app
6
6
7
7
| Column | Type | Description |
8
8
| --- | --- | --- |
@@ -21,21 +21,20 @@ Source examples: files in `examples/`. Some existing sample exports still use th
21
21
|`total_monthly_quota`| number | Monthly quota for the user or plan applicable to the row. |
22
22
|`organization`| string | Organization slug associated with the usage. |
23
23
|`cost_center_name`| string | Optional cost center or tagging field. |
24
-
|`aiu_quantity`| number | Same usage converted to AI Credits. |
25
-
26
-
## Additional columns
24
+
## Optional AI Credit columns
27
25
28
26
| Column | Status | Notes |
29
27
| --- | --- | --- |
30
-
|`aiu_gross_amount`| Present in newer previews | Used for AI Credit gross cost when present. |
28
+
|`aic_quantity`| Present in newer previews | Same usage converted to AI Credits. |
29
+
|`aic_gross_amount`| Present in newer previews | Used for AI Credit gross cost when present. |
31
30
|`total_input_tokens`| Legacy / optional | Older token-oriented export field; ignored by the app. |
32
31
|`total_output_tokens`| Legacy / optional | Older token-oriented export field; ignored by the app. |
33
32
|`total_cache_creation_tokens`| Legacy / optional | Older token-oriented export field; ignored by the app. |
34
33
|`total_cache_read_tokens`| Legacy / optional | Older token-oriented export field; ignored by the app. |
35
34
36
35
## Notes
37
36
- Header row is single-lined; subsequent rows are usage records. Values are comma-separated, double-quoted where needed.
38
-
- Monetary fields are decimals. `aiu_quantity` may also be fractional.
37
+
- Monetary fields are decimals. `aic_quantity` may also be fractional.
39
38
- The app streams the file, treats the first row as the header, and counts subsequent data rows without loading the entire file into memory.
40
-
- Current calculations support both row types: on `requests` rows, `quantity` and `applied_cost_per_quantity` describe PRU usage while `aiu_quantity` and `aiu_gross_amount` remain reference/comparison values and stay `0` when the AI Credit fields are absent; on `ai-units` rows, Premium Requests and generic PRU gross/discount/net totals are counted as `0`, while AI Credits and AI Credit gross cost are taken from the AI-specific fields (`aiu_quantity` / `aiu_gross_amount`, with fallback to `quantity` / `gross_amount` only when those AI-specific fields are absent).
41
-
- Reports without `aiu_quantity` still load, but AI Credit summaries will display `0`.
39
+
- Current calculations support both row types: on `requests` rows, `quantity` and `applied_cost_per_quantity` describe PRU usage while `aic_quantity` and `aic_gross_amount` remain reference/comparison values and stay `0` when those AI Credit fields are absent; on `ai-units` rows, Premium Requests and generic PRU gross/discount/net totals are counted as `0`, while AI Credits and AI Credit gross cost are taken from the AI-specific fields (`aic_quantity` / `aic_gross_amount`, with fallback to `quantity` / `gross_amount` only when those AI-specific fields are absent).
40
+
- Reports without `aic_quantity` still load, but AI Credit summaries will display `0`.
<h2className="context-banner__title">GitHub Copilot is moving to token-based billing</h2>
394
382
<pclassName="context-banner__body">
395
-
Starting May 1, 2026, Copilot usage will be measured in AI Credits (AICs) instead of Premium Requests (PRUs). <strongclassName="aiu-callout">1 AIC = $0.01.</strong> This preview shows what your usage would look like under the new pricing.
383
+
Starting May 1, 2026, Copilot usage will be measured in AI Credits (AICs) instead of Premium Requests (PRUs). <strongclassName="aic-callout">1 AIC = $0.01.</strong> This preview shows what your usage would look like under the new pricing.
0 commit comments