Setup GitHub Copilot

Revenium tracks GitHub Copilot Business and Enterprise usage by syncing data from the GitHub Copilot Metrics and Billing APIs. Setup is through the Revenium dashboard, where the backend handles syncing automatically.

Requirements

• GitHub Copilot Business or Enterprise active on your organization
• A GitHub personal access token owned by an organization owner:

  • Fine-grained (recommended) — organization permissions Organization Copilot metrics (read-only) and Administration (read-only). Generate at https://github.com/settings/personal-access-tokens; an organization owner must approve the token before it starts working.
  • Classic — the admin:org and manage_billing:copilot scopes. Generate at https://github.com/settings/tokens.
• "Copilot usage metrics" policy enabled in your GitHub organization settings (Settings > Copilot > Policies)
• Revenium account with access to the Providers page

Connect your provider first: see Connecting Providers.

1. Add GitHub Copilot as a provider

1. In the Revenium dashboard, go to Integrations > Providers.
2. Select GitHub Copilot from the list of available providers.
3. Enter your Organization — the GitHub organization slug that owns the Copilot seats, as it appears in the organization URL (for example acme, not Acme Corp).
4. For the recommended fine-grained-token path, select Create a pre-filled token on GitHub. GitHub opens with the organization as the resource owner and the required read-only permissions pre-selected. Generate the token, then return to Revenium.
5. Paste the token into Personal Access Token. You can also paste an existing fine-grained or classic GitHub token that meets the Requirements above.
6. Save the configuration.

Once saved, Revenium refreshes Copilot usage data automatically once daily. No CLI installation or local configuration is required.

If you start from the AI assistant setup instead, choose GitHub Copilot and select Connect GitHub Copilot. The provider form opens with GitHub Copilot already selected, and you continue from step 3.

One credential, per-developer detail. Copilot metering reads GitHub's Metrics and Billing APIs, so a single organization credential covers everyone and individual developers install nothing. Each developer's spend is an estimate: their daily AI-credit usage priced at the rate on that day's invoice, or at GitHub's published $0.01 per credit when the invoice does not show a single rate. Treat your GitHub invoice as the financial record. Spend GitHub does not attribute to a developer, and any organization discount, appear as separate organization-level lines. GitHub can restate a day for up to 30 days, so recent figures may change. Developers appear under their GitHub handle until a corporate email address is mapped to it.

2. Verify data is flowing

Saving the credential triggers an immediate historical import covering up to the last 90 days, depending on the data available for your organization. Current usage arrives on two delays that stack: GitHub aggregates Copilot metrics with an approximately 24-hour delay, and Revenium refreshes the Copilot provider once daily. Expect today's numbers tomorrow.

Check Intelligence > AI Assistants > Copilot in the dashboard to confirm usage data is appearing.

The Copilot page also shows Cost by Model for supported date ranges. The table lists Model Name, Total Cost, Credits applied, and % of Total from GitHub's Copilot billing. GitHub does not provide a per-model request count, so the table reports cost, applied credits, and each model's share of the invoiced total.

On the dashboard

Open Intelligence > AI Assistants > Copilot to see usage and costs from GitHub Copilot, including Cost by Model for supported date ranges. Current usage reflects GitHub's aggregation and Revenium's daily refresh.

Troubleshooting

No data appears after adding the provider

GitHub's own 24-hour aggregation delay plus a daily refresh means an empty first day is expected. If nothing shows after 24 hours:

1. Confirm the token carries the permissions listed under Requirements. A token missing either one cannot read the metrics API. Tokens cannot be inspected after saving: replace it in Integrations > Providers > GitHub Copilot by entering a new token and re-entering the organization slug.
2. Confirm the "Copilot usage metrics" policy is enabled for your organization under Settings > Copilot > Policies. With the policy off, GitHub returns no metrics even to a correctly-scoped token.
3. Confirm the organization slug is correct and that the org has Copilot Business or Enterprise active — usage metrics are not available on individual plans.

GitHub token rejected

• The token must start with ghp_ (classic) or github_pat_ (fine-grained).
• Regenerate it and update it in Integrations > Providers, entering the new token and the organization slug together. A blank organization is rejected.
• A token that has expired or had its organization access revoked fails the same way as a mis-scoped one.