# Cursor

Import your team's Cursor AI usage into Pump View. See which models were used, token counts, per-user costs, and fast vs. slow request breakdowns so you can attribute IDE AI spend to individuals alongside your cloud costs.

**Setup time:** \~3 minutes

**Access level:** Read-only

***

### Prerequisites

* **A Cursor Enterprise plan.** The Admin API is only available on Enterprise plans. Business and Pro plans do not support API key generation.
* **An Admin API Key.** This key starts with `key_...` and must be generated by a Team Admin.
* **Team Admin role.** Only Team Admins can access Team Settings and generate API keys.

***

### Setup Instructions

#### 1. Open API Key Settings

1. Log in to [cursor.com](https://cursor.com/) as a Team Admin on an Enterprise plan.
2. Navigate to **Team Settings → API Keys**.

#### 2. Create and Copy an API Key

1. Click **Create** to generate a new Admin API key.
2. Copy the key immediately. It starts with `key_...`. This key grants read access to team member lists and usage events.

#### 3. Connect in Pump

1. In Pump, go to **Settings → Integrations**.
2. Find **Cursor** and click **Connect**.
3. Paste your Admin API key.
4. Optionally, enter your **Team Name** for display purposes in Pump.
5. Click **Connect**.

#### 4. Verify

Pump authenticates via Basic Auth and backfills up to **365 days** of usage events. Your per-user, per-model AI costs should appear within a few minutes.

***

### What Data Does Pump Pull?

| Data                   | Description                                                            |
| ---------------------- | ---------------------------------------------------------------------- |
| **Model usage**        | Which AI models your team is using (e.g., GPT-4, Claude) and how often |
| **Token fees**         | Token-level costs per model                                            |
| **Per-user costs**     | Spend attributed to individual team members                            |
| **Fast/slow requests** | Breakdown of premium (fast) vs. standard (slow) request usage per user |

### Frequently Asked Questions

#### I don't see an "API Keys" section in Team Settings.

The Admin API is only available on Cursor **Enterprise** plans. If you're on a Business or Pro plan, you won't have access to this feature. Contact Cursor sales to learn about upgrading.

#### Who can generate the API key?

Only Team Admins can access Team Settings and generate API keys. If you're not a Team Admin, ask one to create the key for you.

#### What does the Team Name field do?

It's optional and only used for display purposes in Pump (e.g., labeling the integration in your dashboard). If you leave it blank, Pump will still work.

#### How far back does Pump pull data?

Pump backfills up to 365 days of historical usage events from the date you connect.

#### Can I see which team members are using the most AI?

Yes. Pump breaks down usage by individual team member, so you can see per-user costs, model preferences, and fast vs. slow request ratios.

#### Can I revoke the key later?

Yes. You can delete the API key from Cursor at **Team Settings → API Keys** at any time. This will stop data syncing in Pump.

#### My data isn't showing up after connecting.

* Confirm the key starts with `key_...`.
* Verify you're on a Cursor Enterprise plan.
* Ensure the key was generated by a Team Admin.
* Wait a few minutes for the initial backfill.
* If the issue persists, reach out to <support@pump.co>.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.pump.co/integrations/cursor.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.