Resolution criteria

This market resolves to YES if GitHub officially announces or implements a reversal of the usage-based token billing model (which utilizes GitHub AI Credits) introduced on June 1, 2026, and returns to a legacy model such as a request-based billing system (Premium Request Units) or a standard flat-rate billing system for active GitHub Copilot subscriptions.

This market resolves to NO if no such structural reversion is announced or implemented by December 31, 2026 (or another date specified by the market creator).

• Source of Truth: Official statements on the GitHub Blog or updates within the GitHub Copilot Documentation.

• Clarification: Adjustments to the amount of included monthly AI Credits, lowering token costs, or creating new pricing tiers within the token consumption framework will not trigger a YES resolution. The change must be a structural departure from billing strictly by input, output, and cached token consumption.

Background

On June 1, 2026, GitHub transitioned Copilot's billing structure away from its legacy request-based metrics (such as Premium Request Units, or PRUs) to a usage-based token model. Under this system, user interactions consume input, output, and cached tokens, which are deducted from a monthly allotment of "GitHub AI Credits". The transition has generated significant friction and discussion within the developer community due to rapid credit depletion, rate limits, and the added overhead of monitoring token usage during active coding sessions.

This description was generated by AI. Review and verify everything here yourself. You can edit, replace, or delete any part of this description, including the resolution criteria. You do not need to trust the AI output.