Skip to main content
Vantage uses an Admin API key to ingest cost and usage data through the Cursor Admin API. This API provides structured cost data broken down by model (e.g., GPT 5.1 Codex, Claude 4.5 Opus High Thinking) and token type (e.g., input tokens, output tokens, cache read tokens, cache write tokens), as well as requests to the Cloud Agent. Usage data is available for Cursor, measured in tokens or requests based on the usage type.

​
Cursor Permissions

Vantage cannot perform cost-incurring actions. Cursor requires an Admin API key to access the Admin API, which includes additional permissions beyond what Vantage uses (see the full list of permissions here). Vantage only reads data from the Admin API endpoint related to cost and usage and will never perform any other actions. Unfortunately, Cursor does not currently support more fine-grained permissions for Admin API keys. We recommend customers submit a feature request to Cursor for improved permission scoping, and Vantage will adopt fine-grained permissions if this becomes available. Vantage stores only usage metadata (e.g., token consumption). No user content (prompts or responses) is ingested.

​
Connect Your Cursor Account

​
Prerequisites

  • You need to be a Team Administrator to generate an Admin API key in the Cursor console. It’s best practice to use a dedicated key for Vantage and rotate it per your security policy.
  • Create a free Vantage account, then follow the steps below to integrate Cursor costs.

​
Create the Connection

1
Navigate to your Cursor dashboard.
2
On the left, click Settings.
3
Scroll down to the Advanced section and click New API Key.
4
Enter a key name. The Scope is automatically set to Admin. Then, click Save.
Enter a key name in the Cursor console
5
Copy the generated Admin API key that’s displayed.
6
From the top navigation in Vantage, click Settings.
7
On the left navigation, select Integrations > Cursor.
8
The Cursor integrations page is displayed. Ensure you are on the Connect tab.
9
At the bottom of the page, click Add API Key and paste your previously generated Admin API key.
10
For Account Name, enter a name that will be used to differentiate this Cursor account from others you may add. This name will be displayed in Cost Report filters.
11
Click Connect Account.
After clicking Connect Account, you will see the status of your integration change to Importing within the Vantage console. This status indicates that Vantage is actively importing your Cursor cost data. The integration will fetch historical data up to your account’s configured retention period. It usually takes less than 15 minutes to ingest Cursor costs. See the Integration Status documentation for details on integration statuses.
As soon as costs are processed, they will be available on your All Resources Cost Report. If you decide to remove your Cursor integration from Vantage, all costs associated with your Cursor Admin API key will be removed from the Vantage console.

​
Next Steps - Manage Workspace Access

Once the import is complete and the integration status changes to Stable, you can select which workspaces this integration is associated with. See the Workspaces documentation for information.

​
Use Case: Track Token Usage and Allocate Cursor Costs by Team

If your organization uses Cursor across multiple teams, you can use Virtual Tags in Vantage to allocate Cursor token usage and costs by team, user, or project. You can start by analyzing Cursor costs at the user level by grouping by Resource (which represents user emails) to see individual usage patterns. This allows you to identify which users are consuming the most tokens and understand their usage across different models.
Cursor Cost Report grouped by user
Once you’ve identified user-level patterns, you can take your analysis further by creating Virtual Tags to group users by team, department, or project. For example, you may want to track token consumption for the Engineering team to understand their usage patterns across different models. By creating a Virtual Tag with the key Team and the value Engineering, you can apply a filter to group together Cursor costs filtered by user emails (Resource) associated with engineering team members. You can then analyze token usage by model type (e.g., GPT 5.1 Codex vs. Claude 4.5 Opus High Thinking) and token category (input, output, cache read, cache write) to identify optimization opportunities.

​
Data Refresh

See the provider data refresh documentation for information on when data for each provider refreshes in Vantage.

​
Cursor Reporting Dimensions

On Cursor Cost Reports, you can filter and group across several dimensions:
  • Team (the name you assign to the integration when created in Vantage; use Account for Group By)
  • Service (e.g., GPT 5.1 Codex, Claude 4.5 Opus High Thinking)
  • Category (e.g., requests, tokens)
  • Subcategory (e.g., Usage-based, Included in Business)
  • Resource (user email)
  • Charge Type (Usage)
  • Tags: Includes Virtual Tags created in Vantage for this provider. The following provider tags are automatically created by Vantage from Cursor data and are available for filtering and grouping:
    • cursor:max_mode: Indicates whether the option to use maximum context windows for all models is enabled, allowing you to filter and group costs by max mode usage.
    • cursor:user: The Cursor user email when present in the source data, allowing you to filter and group costs by user email.