AI Launch Profile

GitHub Copilot AI Credits Usage Metrics API

GitHub added per-user AI credit consumption through the ai_credits_used field in Copilot usage metrics API reports.

Official launch image for GitHub Copilot AI Credits Usage Metrics API

At a glance

Launch Snapshot

Company
GitHub
Launch date
June 19, 2026
Launch type
Not classified
Category
Not classified
Audience
Enterprise administrators, organization owners, engineering leaders, and FinOps teams monitoring Copilot adoption and usage-based cost exposure.
Pricing
Not publicly confirmed
Free plan
Not publicly confirmed
API
Not publicly confirmed
Open weights/source
Not publicly confirmed

Verification & Sources

Status
Verified
Source links
3
Freshness
Verified July 9, 2026
Last verified
July 9, 2026
Last updated
July 9, 2026
Suggest a correction

Form submissions, correction notes, score details, URLs, and analytics events may be stored for editorial review, spam prevention, product improvement, and follow-up. Do not submit secrets, unreleased financials, private customer data, or regulated personal data through these forms.

Kingy Launch Score

6.6 / 10 · Mixed

One earned credibility score, computed from cited evidence — not a placeholder. How the Kingy Launch Score works

Why this score

  • Source & verification 8.0/10 — The changelog announcement, API documentation, and the plans page — dated first-party sources. github.blog
  • Product evidence 7.0/10 — A shipped API field documented in the usage-metrics reference. docs.github.com
  • Significance & novelty 5.0/10 — Per-user AI credit consumption reporting — a narrow FinOps improvement. github.blog
  • Traction signals not scored — insufficient sourced evidence
  • Offer clarity 6.0/10 — Access follows the documented Copilot plans. github.com

Evidence checked 2026-07-10

Kingy AI Take

GitHub added an ai_credits_used field to the Copilot usage metrics API, reporting per-user AI credit consumption, per the June 19, 2026 changelog (github.blog). Enterprise Administrators and FinOps Teams can line adoption up against usage-based cost exposure. It is an aggregate consumption signal rather than an invoice or feature-level breakdown, so pair it with billing data before making budget decisions.

Who it is for

Enterprise administrators, organization owners, engineering leaders, and FinOps teams monitoring Copilot adoption and usage-based cost exposure.