AI Launch Profile

GitHub Copilot AI Credits Usage Metrics API

GitHub added the ai_credits_used field to enterprise and organization Copilot usage-metrics API reports, exposing an overall per-user total in the one-day and 28-day user endpoints.

Read official source

At a glance

Launch Snapshot

Company: GitHub
Launch date: June 19, 2026
Launch type: Not classified
Category: AI Developer Tools, AI Infrastructure, AI Productivity Tools
Audience: Data Analysts, Engineering Teams, Enterprise IT, Enterprises, Finance Teams
Pricing: The metrics field is not separately priced. Copilot plan allowances and additional AI-credit charges vary by plan and model, and the reported value is a usage signal rather than an invoice total.
Free plan: No
API: Yes
Open weights/source: No

Launch Context

Use these links to move from this record into the broader Launch Intelligence database.

Launch Intelligence hub Today's launches This week's launches More: AI Developer Tools More: AI Infrastructure More: AI Productivity Tools More: Data Analysts More: Engineering Teams More: Enterprise IT More: Enterprises More: Finance Teams

Verification & Sources

Evidence state: Recheck due
Source links: 5
Freshness: Needs recheck: checked July 28, 2026
Last updated: July 28, 2026

What this evidence state means

Definition: The claim was previously checked, but its review window expired or a material change may have invalidated it.
Required provenance: The prior evidence and check date are retained, together with the expiry or change signal that triggered recheck.
Owner: Kingy freshness queue owner and assigned editorial reviewer
Freshness rule: This is already outside its freshness rule. It must not be presented as current until reviewed against current evidence.
Disputes and corrections: Use “Suggest a correction” on the record. Kingy editorial reviews the cited evidence, records material corrections, and changes or removes the state when it is not supported.

Key source checks

Official site Official docs Pricing Source 3 Source 4

Suggest a correction

Kingy AI Take

Per-user AI-credit totals give administrators a practical way to spot consumption concentration and build internal reporting. The field is deliberately coarse: GitHub says it is an overall user total, is not broken down by feature, model or surface and should not be treated as billed usage. Kingy did not query a tenant, so teams should reconcile it with billing exports, identity changes and endpoint timing before using it for chargeback or budget enforcement.

Who it is for

Enterprise IT, engineering leadership, finance, FinOps and data teams that administer Copilot and reconcile adoption with AI-credit consumption.

What feels promising

A stable per-user field in one-day and 28-day reports can connect Copilot adoption analysis with emerging AI-credit exposure without screen scraping.

What feels unproven

Kingy did not test permissions, pagination, late data, identity changes, endpoint consistency, rate limits, billing reconciliation or the accuracy of organization and enterprise rollups.

Source list

Sources

Official site github.blog Source docs.github.com Source docs.github.com Source docs.github.com Source docs.github.com