Understand the cost
Read gross usage value, included or discounted usage, and net billable cost separately. Follow model and user-level consumption when spending changes.
AI Usage & Cost Monitoring
Know what AI consumes. See where the spend goes.
Monitor AI costs for Claude, Codex, and GitHub Copilot. Review spending and available consumption signals alongside adoption and engineering outcomes.
AI usage and cost visibility
GitHub Copilot · July 2026AI Cost & Credits
Credit consumption, forecasts, and financial summary
Data sources
Gross usage value$18,804.04↓ 44.5%
Usage value decreased, while credit consumption exceeded the included pool.
Credit pool usage
July 2026Included credits consumed0% remaining
Included credit pool exceeded by 3,204.3 credits.
- AI credit pool value
- $18,772.00 ↓ 75%
- Total AI credits used
- 1,880,404.3 ↓ 44.3%
- Avg. daily burn rate
- 58,762.6 ↓ 44.3%
- Total users
- 988 Across the credit pool
- Remaining credits
- −3,204.3
- Forecasted month-end usage
- 1,880,404.3
- Forecasted overage
- 3,204.3
- Reporting period
- July 2026
Switch between the financial view and AI usage to inspect consumption in context.
From signals to decisions
Separate consumption, cost, and budget risk
Review the same scope and period so usage changes can be traced through the financial view.
Follow credit consumption
Monitor remaining credits, pool usage, and daily burn. Use the forecast to identify whether the available credit pool may be exceeded.
Review concentration and risk
Investigate high-consumption users and model cost patterns. Check the underlying usage before changing a budget or rollout plan.
What to look at
Follow the usage pattern before changing the budget
Move from the credit pool into the models, users, and source reports behind a change.
- Summary and credit-pool forecasts
- Model and user-level consumption
- Budget Recommendations and Risks & Insights
- Raw Report source detail
- Start with Summary and Pool & Forecast
- Read consumption and cost trends, then compare daily burn with the expected month-end usage and available credits.
- Investigate Models and Users
- Find the models and usage patterns behind a change. Review credit share, gross value, discounts, and user consumption.
- Review recommendations and source reports
- Use Budget Recommendations and Risks & Insights to focus follow-up. Check the Raw Report when you need the collected source detail.
Shared definitions
Read the financial signals consistently
Use the reported definitions and selected scope when discussing spending with engineering, platform, and finance teams.
Add code-origin context with Blamely →- AI Credits
- Provider-specific consumption units reported by the connected source. Credit definitions and availability vary by provider.
- Gross usage value
- Reported monetary value of consumption before included usage or discounts.
- Net billable cost
- Reported billable amount after included usage and discounts.
- Daily burn rate
- Average credit consumption per day over the selected reporting period.
- Forecasted overage
- Estimated consumption above the available credit pool, based on the reported usage pattern.
Common questions
AI usage and cost monitoring questions
Need to discuss your team or technical setup? Contact us.
Which assistants support AI Cost monitoring?
AI Cost monitoring supports Claude, Codex, and GitHub Copilot. Connect the relevant integration to review spending alongside usage and engineering outcomes. Available measures depend on the source and reporting scope.
What does AI Usage & Cost Monitoring track?
It brings together AI credit consumption, token usage signals, gross usage value, included or discounted usage, net billable cost, burn rate, and forecasts. Available measures depend on the connected source.
Which provider does the Cost & Credits preview show?
AI Cost supports Claude, Codex, and GitHub Copilot. This preview shows the GitHub Copilot Cost & Credits reporting view; provider-specific financial measures can differ. It separates credit-pool consumption from the financial summary so gross usage and net billable cost can be reviewed together.
Why can gross usage be high while net billable cost is zero?
Included usage and discounts can cover reported consumption. Review gross usage and credit-pool depletion as well as the net amount when assessing the pattern.
Can we see model and user-level consumption?
Yes. Models and Users views help investigate credit share, cost values, model usage, and projected consumption within the connected reporting scope.
Are forecasts guaranteed?
Forecasts estimate future consumption from reported usage patterns. Review the selected period, recent changes, and source coverage when using them to plan a budget.
How should we use budget recommendations?
Treat recommendations as inputs to a budget review. Check the usage pattern, team needs, and model mix before deciding whether to change a budget.
How does cost monitoring connect to AI Impact?
Cost gives the financial context for adoption and contribution. Review it with delivery, quality, and rework trends in AI Impact to evaluate the engineering outcomes alongside spending.
See Oobeya in practice
Review AI spending with the work it supports
Walk through credits, usage patterns, model costs, and forecasts alongside your team’s AI adoption and engineering outcomes.