High Volume of Zero-Token Records in Normal Requests Across Auto and Advanced Models

In the model usage log data fetched from the Cursor usage events API, there are a large number of records with zero token usage even for normal requests. This is not limited to Auto models; many advanced models show the same pattern.

We need to confirm whether this is expected behavior and help investigate the cause.

This is a known bug with how token counts are recorded in usage data. Your team’s billing and usage limits are working correctly behind the scenes, but the token fields in the usage events show 0 for some requests.

A few things contribute to the zero-token records:

  • Errored or cancelled requests correctly show 0 tokens and $0 cost

  • Some successful requests have token counts that aren’t populated properly in the usage data, even though billing tracks them correctly through a separate path

We have an open bug report for this and are working on a fix. In the meantime, your spending dashboard graph at cursor.com/dashboard/spending is the most reliable view of actual usage.