> For the complete documentation index, see [llms.txt](https://docs.revenium.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/setup-cursor.md).

# Setup Cursor

Revenium tracks Cursor IDE usage by syncing data from the Cursor Admin API. Setup is through the Revenium dashboard, where the backend handles syncing automatically.

## Requirements

* Cursor IDE with an active subscription (Pro, Business, or Enterprise)
* Cursor **team** API key (from your Cursor team settings — this is different from a personal user key)
* Revenium account with access to the Providers page

Connect your provider first: see [Connecting Providers](/get-started/quickstart/connecting-providers.md).

## 1. Add Cursor as a provider

1. In the Revenium dashboard, go to **Integrations > Providers**.
2. Select **Cursor** from the list of available providers.
3. Enter your **Cursor team API key**. This key is issued from your Cursor team settings and grants access to the team usage API.
4. Save the configuration.

Once saved, Revenium syncs Cursor usage data automatically every 5 minutes. No CLI installation or local configuration is required.

{% hint style="info" %}
**Team API key required.** Cursor has both personal user keys and team keys. Revenium uses the `/teams/filtered-usage-events` endpoint, which requires a **team** API key. A personal key will not work.
{% endhint %}

## 2. Verify data is flowing

After saving, allow up to 10 minutes for the first sync cycle to complete. Then check **Intelligence > AI Assistants > Cursor** in the dashboard to confirm usage data is appearing.

## On the dashboard

Open **Intelligence > AI Assistants > Cursor** to see the Cursor tab with usage and costs synced from the Cursor team API. The first sync may take up to 10 minutes.

## Troubleshooting

### No data appears after adding the provider

The backend syncs every 5 minutes. Allow up to 10 minutes for the first data to appear. If nothing shows after that:

1. Confirm you used a **team** API key, not a personal user key.
2. Verify the key in **Integrations > Providers > Cursor** is correct and has not been regenerated.
3. Confirm your Cursor subscription (Pro, Business, or Enterprise) is active.

### Cursor API key rejected

* The key must be a **Cursor team API key** from your Cursor team settings.
* Personal user API keys do not have access to the team usage endpoint.
* Regenerate the key in Cursor if in doubt and update it in **Integrations > Providers**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.revenium.io/track-and-control-costs/analyze-ai-tooling-spend/setup-cursor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.