Data sources · Sources checked
AI coding tool integrations: data and coverage
Check whether each connected account covers the providers, costs, client activity, and repositories you need.
On this page
Connecting a provider's usage API does not necessarily give you billing data. GitHub Copilot is one example: usage reporting and enterprise billing require different permissions. Neither record tells you which code reached a merged pull request. That requires source control and a way to match the tool user to the contributor.
What each source reports
Weave collects data through provider APIs, configured coding clients, and source-control connections. Coverage depends on the provider plan, account, and permissions. Client telemetry also depends on which engineers and machines are configured to send it.
Scroll horizontally if needed →
| Source | Usage or activity | Cost data | Access and coverage to check |
|---|---|---|---|
| Cursor | Workspace API activity; separate plugin session and edit telemetry | Admin API spend; account for subscription and included usage | Workspace admin access for Teams or Enterprise. Plugin activity is per configured engineer. |
| GitHub Copilot | GitHub organization activity; separate compatible client telemetry for Copilot Chat | Provider billing, seats, and premium requests where accessible | Connect the organization or enterprise that pays. Usage access alone does not provide billing data. |
| Claude Code | Provider reports and configured telemetry or plugin sources | Enterprise analytics may provide billed per-user costs; Console reports and telemetry can provide estimates | Check the plan, key type, paying account, identity mapping, and machines sending telemetry. Cloud-provider billing is separate. |
| Codex | Configured client telemetry or plugin activity | Credits at a configured rate, or token-based estimates | Check which client and account are connected. Reference-priced activity is not a ChatGPT subscription invoice. |
| OpenAI direct API | Provider usage at the available user or project scope | Token-based estimates | Verify the connected account and project. Negotiated adjustments may not be included. |
| Devin and Windsurf | Provider usage available for the connected plan | Usage units at a configured rate; Windsurf can also use seat allocation | Check the plan, units, and configured rate. Units do not verify an invoice. |
| Gemini CLI | Configured token and activity telemetry | No native CLI dollar cost; a configured subscription can be allocated | Check telemetry senders and subscription assignment. Token activity is not billed cost. |
| Modal | Organization-level compute billing | Metered cost at organization scope | Check workspace and billing account. The amount is not automatically assigned to engineers. |
Why reported cost may differ from the invoice
A token-based estimate uses observed activity and a reference price. It can help explain usage without including a subscription allowance, negotiated discount, credit, or tax. A configured seat allocation spreads a subscription cost across assigned users. Neither calculation should be presented as an invoice amount.
Weave distinguishes billed, estimated, modeled, client-reported, and allocated costs. The label matters when comparing tools. A billed per-user amount from Claude Code enterprise analytics and a Console usage estimate can have different account scopes and cost bases, even when both are expressed in dollars.
An apparently low total can also come from an unconnected second workspace, an enterprise account that pays for several organizations, or a reimbursed personal subscription. Compare the connected accounts with the invoices. The AI coding budget guide works through seats, allowances, and overages.
Matching tool activity to merged code
A suggestion can be accepted and then deleted before commit. A commit can contain AI-assisted code even when the author has no connected tool telemetry. An open PR may never merge. These are different stages, so an activity count cannot stand in for an authorship percentage or a merged-output total.
Scroll horizontally if needed →
| Question | Evidence to check | What it leaves open |
|---|---|---|
| Was the tool used? | Provider activity or configured client telemetry | Other clients and unconfigured machines may be missing |
| What did it cost? | Invoice, estimate, configured rate, or seat allocation | Billing and activity may cover different accounts |
| Which changes had AI evidence? | Native attribution, Git metadata, or activity-based estimates | Keep direct, inferred, and estimated signals distinct |
| Which work merged? | Connected repositories, contributor identities, and merged pull requests | Repositories outside the connection are not included |
| What happened after merge? | Review, quality, rework, and later delivery signals | Activity and output alone do not show business value |
The AI code authorship guide distinguishes direct tool evidence, Git co-authorship, and activity-based estimates. Preserve those distinctions when reporting attribution. A change without detected AI evidence may still have been AI-assisted.
Test the connection with a known user
Pick a user whose tool activity and merged work you can inspect for a known period:
- Check the latest sync for the connected provider account.
- Find the user's activity and confirm that their tool identity maps to the correct person.
- Compare the reported cost with the invoice for the same account and billing period. Record whether it is billed, estimated, modeled, client-reported, or allocated.
- Find a merged PR in a connected repository. Check its author mapping and the source of any AI attribution.
If the activity appears but the PR does not, check repository scope and contributor mapping. If usage appears without cost, check billing access and the cost source. A successful connection confirms that an account is reachable; it does not confirm that every expected record is present.
Router setup is separate from analytics
Weave Router setup configures where a coding client sends model requests. Analytics connections supply the activity, cost, and source-control records used in reports. Routing a client through Weave does not confirm that billing or repository data is connected. Connecting analytics does not change the client's routing configuration.
Check access before connecting accounts
The connection flow lists the permissions requested for each source. Check them against the provider account, billing owner, and repositories you intend to include. An organization usage connection and an enterprise billing connection may need different owners to approve access.
For account-access and retention requirements, see Weave security and involve your security owner in the setup. If you need help debugging a connection, remove API keys, prompts, source code, and account exports from screenshots or public examples.
Sources
Connecting your team's tools
Review your provider accounts, billing access, and repositories with the Weave team.
Book a demo