On 1 June 2026, GitHub switched Copilot to token-based usage billing. The plan prices look the same on paper — Copilot Pro is still $10/month, Pro+ is still $39/month, Business $19/user, Enterprise $39/user — but the meter underneath has changed. Once you exhaust the included monthly allowance, every model call you make is billed in GitHub AI Credits (1 credit = $0.01 USD), at per-token rates that depend on which model you used and how big your context was.
Within 48 hours, Reddit, X, and GitHub's own community discussion thread were full of developers comparing 10x to 50x cost increases. One Redditor reported a jump from $29 to $750 a month. Another from $50 to $3,000. Some users with more measured workflows reported essentially no change. The variance is the story: the bill is now a function of how each individual developer actually uses the tool, and most developers had no idea what their usage profile looked like under the hood.
This site's recent coverage has been, in some sense, about what happens when machines end up on the receiving end of a similar meter — AWS AgentCore paying x402 endpoints, Circle's Agent Stack settling micropayments, Base MCP wiring LLMs into DeFi. The Copilot change is the human-facing rehearsal of the same shift, and it is teaching every payment developer something specific about how this economy is going to feel when it lands.
The Real Story Is Not the Price, It's the Variance
Look past the "GitHub raised prices" framing. The headline plans did not change. What changed is that per-developer billing variance just exploded by an order of magnitude. Under a flat subscription, the worst customer and the best customer both paid $10. Under per-token usage, the worst customer can easily pay 70x what the best one does — and neither of them can predict next month's bill from this month's, because their bill is a function of how much they happen to call premium models like GPT-5 or Claude 4.5 Opus inside the tool.
This is exactly the financial profile that payment developers have been building infrastructure for. Everything in the Keyrock report — sub-cent average transaction sizes, settlement variance across protocols, regulatory framework gaps — is the same shape of problem expressed at machine scale rather than human scale.
The interesting question is no longer "is consumption-based billing coming." It is here. The interesting question is what infrastructure makes it survivable for the people on the wrong end of the meter.
Read the full article on tomcn.uk →
About the Author
I'm Tom Wang, an AI Developer & Fintech Developer — building AI agents, crypto payment infrastructure, and cross-border payout systems with Rust, Go, and TypeScript. Based in London, UK.
Currently open to new opportunities in fintech, crypto payments, and AI agent engineering.
Top comments (0)