GitHub Copilot premium requests

Usage of Copilot is measured through a combination of licenses and monthly usage tracking. For more information about how license costs in Copilot work, see GitHub Copilot licenses.

What are premium requests?

Some Copilot features use premium requests. Premium requests give you access to advanced models and additional AI features.

Examples include:

• Using Copilot Chat with premium models
• Large context windows or advanced reasoning models
• Features like Copilot-Programmier-Agent
• Spark app creation

Each product's premium request usage is attributed to a premium request SKU:

• Copilot premium requests - Chat, CLI, Code Review, Extensions, and Spaces
• Spark premium requests - Spark app creation
• Copilot-Programmier-Agent premium requests - Copilot-Programmier-Agent sessions

See Anforderungen in GitHub Copilot for details on which models and features consume premium requests and their SKU attribution.

How usage of premium requests is measured

Usage of premium requests is tracked monthly and is based on the following factors.

Monthly allowance

• Each plan includes a fixed number of premium requests per user per month.
• Allowances vary by plan. See Pläne für GitHub Copilot.
• Allowances reset on the 1st of each month at 00:00:00 UTC.

Multiple licenses

If you receive licenses from multiple enterprises, you must choose which entity is billed for your premium requests. See Überwachen deines GitHub Copilot-Verbrauchs und deiner Berechtigungen.

Usage by premium models

• Each interaction that uses a premium model consumes from your allowance.
• Some models use multipliers, meaning a single interaction may count as multiple premium requests.
• For example, advanced reasoning models may consume 5× or 20× the standard rate.
• If you exceed your allowance and overages are enabled, extra usage is billed at the standard rate.

Usage by Copilot-Programmier-Agent

When you use Copilot-Programmier-Agent, including any Copilot custom agents, both GitHub Actions minutes and premium requests are consumed:

• GitHub Actions minutes come from your account’s monthly allowance of free minutes for GitHub-hosted runners. This allowance is shared with all GitHub Actions workflows. See Abrechnung für GitHub Actions.
• Premium requests come from the monthly allowance associated with your Copilot license. This allowance is shared with other features, such as Copilot Chat.

Each coding agent session consumes one premium request. A session begins when you:

• Ask Copilot to create or edit a pull request
• Assign Copilot to an issue

If you run out of free minutes or premium requests, and you have not set up billing, a message is displayed explaining why Copilot cannot work on the task.

Copilot-Programmier-Agent uses a dedicated Copilot-Programmier-Agent premium request SKU. This SKU still pulls from your monthly allowance of premium requests, but allows for more granular budget control and monitoring.

For more information about Copilot-Programmier-Agent and Copilot custom agents, see Info zum GitHub Copilot-Programmier-Agent and About custom agents.

Using more than your included premium requests

If you exceed your plan's included premium requests, there are options available depending on your account type.

Personal accounts

If you exceed your allowance, set a budget for additional premium requests or upgrade to a higher plan. See Einrichten von Budgets zum Kontrollieren der Ausgaben für Produkte mit verbrauchseinheitenbasierter Abrechnung.

Organizations and enterprises

• Admins can control whether members are allowed to exceed their premium request allowance across AI features using the Premium request paid usage policy.
• Separate policy options are available for Copilot, Spark, and Copilot-Programmier-Agent. See Verwalten des Kontingents an Premium-Anforderungen für deine Organisation oder dein Unternehmen.
• Premium request budgets can be set to either monitor or block overages, with options for bundled or individual SKU management.
• Enterprises can also upgrade frequent users to Copilot Enterprise for higher included allowances.

Paying for premium requests

Additional usage is charged to the payment method configured for your GitHub account.

If you are billed through Azure, premium request usage appears on your Azure invoice. See Herstellen einer Verbindung mit einem Azure-Abonnement.

Managing your budget for premium requests

To help manage your budget for premium requests, consider the following strategies.

Budget options for personal accounts

You can set a budget in your personal billing settings to receive alerts when you reach 75%, 90%, or 100% of your budget. Setting a premium request budget depends on the level of granularity you need:

• Bundled premium request budget - Combines all premium requests into a single budget (Recommended for most users)
• Individual SKU budgets - Set separate budgets for each AI product (Copilot, Spark, Copilot-Programmier-Agent)

Budget options for organizations and enterprises

You can set budgets at the organization, enterprise, or cost center level. If you enable stop usage when budget is reached, extra premium requests are blocked when the budget runs out.

For detailed setup instructions, see Einrichten von Budgets zum Kontrollieren der Ausgaben für Produkte mit verbrauchseinheitenbasierter Abrechnung.

Viele Konten verfügen über ein Standardbudget von 0 USD für Copilot-Premium-Anforderungen. Premium-Anforderungen über die zulässige Anzahl werden abgelehnt, es sei denn, dieses Budget wird bearbeitet oder gelöscht.

Monitoring usage

• Track your monthly usage in your IDE, in Copilot settings on GitHub, or by downloading a usage report.
• Usage reports show all premium requests, both within and beyond the allowance, and can be used to identify high-usage users.
• Premium request analytics display usage by dedicated SKUs, providing detailed insights into which AI products consume your allowance.

For more information about monitoring your usage, see Überwachen deines GitHub Copilot-Verbrauchs und deiner Berechtigungen.