Connector
GitHub Copilot: who uses it, what it costs.
Activity by developer and by day, assigned but unused seats, AI Credits consumption: your GitHub organization Copilot spend, measured through the official API.
Connection through the official admin API, read-only: optidome never modifies the configuration of your tools.
What optidome measures
The data collected, as is.
| Data | Detail |
|---|---|
| Adoption by developer | Copilot activity by user and by day (Metrics API). |
| Dormant seats | Assigned seats with no activity: the list to reassign or cancel. |
| AI Credits budgets | Credit consumption (Enhanced Billing), tracked against your budgets. |
Setup
What to prepare.
- Who, on your side
- An owner of the GitHub organization.
- Prerequisites
- A GitHub organization with Copilot licenses.
- What to provide
- A restricted personal access token (PAT) and the organization slug.
- Where to get it
- Settings → Developer settings → Fine-grained tokens; permissions "Organization copilot (read)" and "Organization administration (read)".
The token expires on the date chosen at creation: note the date and plan the rotation.
Frequently asked questions
Before you start.
- Does the token give access to our code?
- No. The two requested permissions are organizational and read-only: Copilot metrics and administration. No repository access.
- Which Copilot editions are covered?
- Licenses managed by a GitHub organization (Copilot Business and Enterprise). Individual developer subscriptions are not attached to the organization.
Private beta. Access is by application, and the setup of your first connector is assisted: shared screen, until the first data lands.