Cursor usage, cost, and code attribution in Weave

What does Weave support for Cursor?

Token Intelligence names Cursor among its native integrations and per-user cost sources. It brings tool usage and spending together with engineering output so teams can examine adoption and cost alongside completed work.

The Connect Cursor flow offers an admin API connection and a Weave plugin installation. They supply different evidence. An API connection covers the workspace; plugin telemetry depends on the developer machines configured to send it.

Which data sources should you distinguish?

Cursor’s own dashboard, Analytics API, and Admin API are separate surfaces. Their access requirements and field definitions can differ. Access to an endpoint in Cursor does not, by itself, prove that a particular Weave report consumes it.

How do you connect the two sources?

In Connect Cursor, select the plans and setup types that apply. For the admin connection, choose Set up admin API key. A Cursor team administrator creates an admin key in the Cursor dashboard’s settings, then saves it in Weave. Keep the key out of screenshots and source control.

For richer telemetry, choose Install Weave Plugin and follow the generated instructions for each engineer. Workspace-wide API coverage does not mean every developer machine is sending plugin telemetry. If the admin API step is skipped, spend, seats, and output-per-dollar reporting remain unavailable from that source.

Which Cursor APIs and reporting windows apply?

Cursor’s Analytics API, team analytics, and Admin API describe separate reporting surfaces. Check the current plan, API access, and permission requirements for the surface your connection uses before planning an automated report.

Check the latest successful sync and the active plugin senders in your account. A connected workspace does not guarantee that every endpoint is available. AI code-tracking access can be unavailable while other usage and cost data continues to sync. Confirm the specific attribution field before interpreting a missing value as zero assistance.

How should Cursor cost be interpreted?

Weave separates the admin API key from plugin telemetry. The admin connection covers Teams and Enterprise workspaces and reports workspace usage, cost, seats, and historical activity. A workspace admin creates the key in the Cursor dashboard settings. The Weave Plugin supports any Cursor plan and provides session and file-edit detail, tool and MCP calls, and prompt activity from machines where it is installed.

Reconcile the period’s expense with your invoice. Cursor’s Admin API distinguishes spending fields and billing-cycle windows; usage-valued amounts can include usage already covered by a subscription. Adding that included usage to the invoice again can overstate cost.

Keep unattributed or organization-level amounts visible rather than dividing them across PRs without a stated allocation rule. See the AI ROI methodology for the difference between matched attributed spend and a full company budget.

Does Cursor attribution prove a change was AI-written?

Cursor documents AI contribution detection in Git commits, with limits around matching suggested code to later changes. A committed-code measure differs from accepted suggestions and from merged or deployed work. Code outside the detected category should not automatically be called verified human-only work.

Weave’s authorship guide explains direct, inferred, and estimated evidence. Keep that evidence label with the result and account for tools that overlap on the same PR.

What should a Cursor pilot produce?

Use one team, connected repository set, and consistent reporting period. Validate identity matching, cost-source labels, and representative contribution records. Inspect a real merged PR and its output reasoning, then review quality and rework alongside it.

The result should support a specific decision, such as renewing seats or expanding adoption. The Cursor analytics evaluation guide covers baseline design and ROI interpretation in more detail. This page identifies the integration coverage to verify first.