Today, Vantage is announcing support for Cursor costs in the Vantage console, allowing Vantage customers to track their usage and spend on Cursor alongside the rest of their cloud infrastructure. Customers can connect their Cursor accounts from the Integrations page, and Vantage will automatically ingest and categorize usage based on tokens used, model type, and user.

Teams use Cursor as an AI-powered coding assistant and IDE. Cursor usage is billed in tokens across several dimensions, including input tokens, output tokens, cache read tokens, and cache write tokens, as well as requests to their Cloud Agent. Prior to this launch, customers needed to manually collect this data from Cursor and upload using Custom Providers to analyze token usage and spend in order to view these costs within Vantage.

Now, with the launch of Cursor cost support in Vantage, customers can grant Vantage access to their Cursor organization by creating an Admin API key in the Cursor console, and Vantage will automatically ingest their costs to display alongside their other infrastructure costs. This key allows Vantage to retrieve detailed cost and usage data, including token and request counts by model (e.g., GPT 5.1 Codex, Claude 4.5 Opus High Thinking), type (e.g., request, token), and the user generating the costs. Customers can use these attributes to allocate costs to teams through Virtual Tags, detect anomalies in Cursor usage, and analyze Cursor consumption alongside other AI spend, such as OpenAI and Anthropic.

The Cursor integration is now available to all Vantage customers. To connect, go to the Integrations page in account settings and select Cursor. You can learn more via the new Cursor section in Vantage’s documentation.

Frequently Asked Questions

1. What is being launched today?

Vantage is launching native support for Cursor cost and usage data. Customers can now connect Cursor via an Admin API key, enabling automatic ingestion and visibility of Cursor usage and costs in Vantage.

2. Who has access to this integration?

The Cursor integration is available to all Vantage customers, across all subscription tiers.

3. How much does this integration cost?

There is no additional fee for using the integration. However, Cursor costs will be included in quota tier enforcement. In the event that your Cursor costs push you over your current tier limit, you may be prompted to upgrade. To see more details on pricing, please refer to the Pricing page.

4. How does the integration work?

Vantage uses the Admin API to ingest consumption through Admin API Keys. After authorizing Vantage access to your Cursor account, Vantage will begin ingesting data from the Admin API, which provides structured cost data broken down by model (e.g., GPT 5.1 Codex, Claude 4.5 Opus High Thinking), token type (e.g., input, output, cache), and user.

5. What permissions does Vantage have in my Cursor account?

Vantage does not have the ability to perform any actions that incur costs. However, Cursor does not have any scoping of Admin API Keys. This key 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 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.

6. What permissions are required on the Cursor side?

You need to be a Team Administrator to generate the 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.

7. What permissions are needed within Vantage?

You must have a Vantage Owner or Integration Owner role to add or remove the Cursor integration.

8. What dimensions can Cursor costs be filtered and grouped by?

Cursor reports can support aggregating and filtering on the following dimensions:

• Team (the name you assign to 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 ID (user email)
• Charge Type (Usage)
• Tag (includes Virtual Tags created in Vantage, as well as cursor:max_mode, which indicates whether the option to use maximum context windows for all models is enabled and cursor:user, which allows you to filter by Cursor user email within the tag dimension)

9. Can I view Usage data for Cursor?

Yes, usage data is available for models, measured in tokens or requests based on the usage type.

10. Are there Active Resources for Cursor?

No, there are no Active Resources to monitor for Cursor.

11. How often does Cursor data refresh in the Vantage console?

Cursor data refreshes daily in the Vantage console.

12. What happens if I remove a Cursor integration?

If you decide to remove your Cursor integration from Vantage, all associated costs will be removed from the Vantage console associated with that Cursor Admin key.

13. How far back will the data go?

The integration will fetch historical data up to your account’s configured retention period.

14. Does Vantage store prompt or response content?

No. Vantage only stores billing metadata (i.e., token consumption). No user content (prompts or responses) is ingested.