Microsoft's GitHub shifts to metered AI billing amid cost crisis

2026-04-28 · Source: The Register: Enterprise Technology News and Analysis · Field: Technology & Digital — Artificial Intelligence & Machine Learning, Software Development & Engineering, Emerging Technologies & Innovation · Depth: Intermediate, medium

Summary

Microsoft's GitHub is transitioning its Copilot AI service from request-based to usage-based billing, effective June 1, 2026, to address unsustainable inference costs. Previously, all premium requests cost the same, regardless of complexity, leading GitHub to absorb significant expenses for resource-intensive prompts. The new model introduces "GitHub AI Credits," valued at $0.01 each, where usage is calculated based on token consumption (input, output, and cached tokens) at varying rates per model. Existing subscription tiers like Copilot Pro ($10/month) and Business ($19/user/month) will include a monthly allotment of these credits, with options to purchase more or cease usage upon depletion. This shift reflects a broader industry trend among AI providers like Anthropic, Google, and OpenAI, who are also adjusting pricing and usage limits due to surging demand and the high cost of AI inferencing.

Key takeaway

For engineering leaders managing AI development budgets, you should immediately assess your team's GitHub Copilot usage patterns and projected token consumption under the new metered billing. This change, effective June 1, 2026, means complex AI tasks will incur higher costs, potentially impacting project profitability. Plan for variable AI expenses by setting clear usage policies and exploring cost-optimization strategies for prompt engineering to avoid unexpected overages.

Key insights

GitHub Copilot is shifting to usage-based billing to manage escalating AI inference costs.

Principles

• AI service pricing must reflect actual resource consumption.
• Unlimited AI access models are financially unsustainable.

Method

GitHub will use a virtual currency, "GitHub AI Credits" ($0.01 each), to meter token consumption (input, output, cached) across different AI models, replacing fixed-request billing.

In practice

• Monitor token usage for AI agents.
• Set overflow budgets for AI credit consumption.

Topics

• GitHub Copilot
• Usage-Based Billing
• AI Inference Costs
• Token Consumption
• AI Pricing Models

Code references

• google-gemini/gemini-cli

Best for: CTO, VP of Engineering/Data, Machine Learning Engineer, AI Engineer, Software Engineer, Director of AI/ML

Related on AIssential

• GitHub will start charging Copilot users based on their actual AI usage — AI service providers are shifting to usage-based billing to manage escalating inference costs and ensure sustainability.
• ‘What a joke’: Github Copilot’s new token-based billing spurs consternation among devs — GitHub Copilot's new token-based billing model, effective June 1, significantly raises costs for many users, prompting debate over usage efficiency and Microsoft's role.
• The Subsidy Ended: What Tool-Using Agents Actually Cost — GitHub Copilot shifted to usage-based billing, linking costs directly to AI model and token consumption.
• AI costs how much? GitHub Copilot users react to new usage-based pricing system. — GitHub Copilot's shift to usage-based billing reveals significant AI inference costs previously absorbed by providers.
• Changes to GitHub Copilot Individual plans — Agentic AI workflows significantly increase compute demands, necessitating pricing model adjustments.
• Cobrança de tokens no GitHub Copilot aumentará custos em até 150 vezes — GitHub Copilot's new token charges will drastically increase costs, impacting user economics.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by The Register: Enterprise Technology News and Analysis.