GitHub lets admins track bring-your-own-key AI usage in Copilot

Who it's for: Enterprise admins
Where it works: Copilot usage metrics API

Key points

Tracks your own API key usage
Tracks local models like Ollama
Covers enterprise custom models
Breaks usage down by user
Admins can check BYOK policy
No change to existing totals

Where to use it

Software teamsReview which developers use their own keys
IT administrationCompare custom model use against Copilot totals
Budget planningSeparate billed provider costs from Copilot costs

What happened

GitHub added bring-your-own-key (BYOK) usage to the Copilot usage metrics API. Admins can now see requests sent to a developer's own provider key or to a local model such as Ollama, plus custom models set up for their company.

Why it matters

Companies can check who uses their own keys or local models against company policy. Spending becomes clearer, because costs billed by a provider are kept apart from Copilot's own.

What to do

Check the reports if your company has a BYOK policy
Note that local usage may be undercounted

Source

GitHub: BYOK and enterprise custom models in the Copilot usage API

Written with AI from the source above. If something looks off, the source is what counts.