Oleksandr Kuzmenko, EditorPublished 6 min readAI-assisted · editor-reviewed
TL;DR
- Cursor removed dollar cost data for all individual and self-serve Teams plans, shifting to a token-only usage metric.
- CSV exports now default the Cost column to 0.0, and the internal API retroactively zeros out or omits historical cost fields.
- Enterprise plan users can still access detailed cost breakdowns, while self-serve plans must rely on high-level spend summaries.
Key facts
- Effective Date
- July 31, 2026
- Affected Tiers
- Individual & Teams (Self-Serve)
- API Fields Impacted
- chargedCents, usageBasedCosts, totalCents
What Changed in the Dashboard and API
Cursor removed all dollar indicators from the primary Dashboard > Usage interface for individual and self-serve Teams plans. Usage covered by standard plan quotas now shows Included with raw token counts. When exporting activity via CSV, the Cost column displays 0.0 across all rows.
Developers using the internal endpoint https://cursor.com/api/dashboard/get-filtered-usage-events found that JSON properties for cost were zeroed out or omitted retroactively as of 2026-07-31:
chargedCents:0usageBasedCosts:"$0.00"totalCents: omitted
Official Rationale and Alternative Tracking
Cursor support clarified that Enterprise plans retain full dollar metrics, whereas self-serve plans are now token-only. The team cited user confusion around calculated value vs. actual billed overages as the primary driver for the change.
To track spending going forward:
- Self-Serve Teams Admins: High-level per-user spend remains available under
Dashboard > Members > On-Demandor via the official Admin API. - Billing Cycle Totals: Billed overages are displayed aggregated under
Dashboard > Spending. - Per-Model Audits: Granular per-request or per-model dollar breakdowns are no longer supported natively on self-serve tiers, requiring teams to manually map token counts against public model pricing tables.
When to use
- When you want to check your aggregate spending for the billing cycle.
- When analyzing raw token counts rather than estimated dollar metrics.
When NOT to use
- When attempting to automatically pull per-request dollar costs from the self-serve API.
What to do today
- Check your billing totals on the Dashboard > Spending page.
- Update any custom cost-tracking scripts that rely on the internal usage API endpoint.
- Map token counts manually against model pricing tables if granular per-model audits are required.
Step names are taken from What to do today.
Step names are taken from What to do today. Check your billing totals on the Dashboard > Spending page.. Update any custom cost-tracking scripts that rely on the internal usage API endpoint.. Map token counts manually against model pricing tables if granular per-model audits are required.
- Check your billing totals on the Dashboard > Spending page.
- Update any custom cost-tracking scripts that rely on the internal usage API endpoint.
- Map token counts manually against model pricing tables if granular per-model audits are required.