Skip to main content

​
Overview

nOps uses your Cursor Team Admin API key to connect your Cursor team account and validate access before storing credentials securely. The key powers AI seat tracking in Budgets (per-user spend and limits) when you opt in on a budget. The key is never shown again in the nOps UI after you save it.
One Team Admin API key covers everything nOps reads from the Cursor Admin API — team members, daily usage, per-event usage, and spend. It authenticates with HTTP Basic auth (the key as the username, no password), so no separate secret is needed. Personal or user-level API keys will not work — it must be a Team Admin key.

​
Prerequisites

  • A Cursor Teams or Enterprise plan with admin access
  • Permission to create Team Admin API keys in Cursor
  • nOps organization administrator access to connect or manage the integration
Members can view integration status on Account Settings and Integrations, but only admins (and owners) can connect, re-validate, or disconnect. Non-admins see an Admin Only indicator on the Cursor card.

​
Create a Team Admin API key

  1. Sign in to Cursor with an account that has team admin privileges.
  2. Open your team settings and navigate to Admin API or API keys (see Cursor Admin API documentation).
  3. Create a new Team Admin API key.
  4. Copy the key immediately — Cursor may only display it once.
Treat the Admin API key like a password. Do not share it in chat, email, or source control.

​
Connect in nOps

Only nOps administrators can complete these steps.

​
Where to open Cursor

  • To connect for the first time — go to Settings → Integrations (the main Account Settings page shows a preview of available apps; use View all to open the full catalog if Cursor is not in the preview) and click the Cursor card.
  • To manage an existing connection — go to Account Settings → Account Status → Connected apps and click the Cursor chip to re-validate or disconnect.

​
Connect steps

  1. Click the Cursor integration card or chip.
  2. Paste your Admin API key and click Connect.
  3. nOps validates the key with Cursor (GET /teams/members) before saving it.
If validation succeeds, the status shows Integrated on the integrations catalog card, or Connected in Account Status and in the connection modal.

​
Use in Budgets

After Cursor is connected org-wide, enable it per budget:
  1. Open Operate → Budgets and select a budget.
  2. In AI seat tracking, select Cursor and Save.
  3. Matched users show period-to-date spend and seat limits in the user table (matched by email).
Cursor seat limits are read-only in nOps today. To turn off tracking for one budget, deselect Cursor (and any other providers) and save—this does not disconnect the org integration. See Budgets — AI seat tracking for the full workflow.

​
Manage your connection

After Cursor is connected, administrators can open the same card or chip to:
  • Re-validate — nOps checks the stored key against Cursor again without asking you to re-enter it.
  • Disconnect — removes the stored key and marks the integration as disconnected in nOps.
If validation fails (for example, the key was revoked in Cursor), the status changes to Action required. An administrator should open the integration and connect again with a new key, or use Re-validate after fixing the key in Cursor.

​
What nOps stores

nOps saves integration status and configuration details (such as when Cursor was connected and last validated) so your team can see whether the integration is active. Your Admin API key is stored securely and is never shown again in the nOps UI after you connect.

​
Troubleshooting

​
Invalid API key

  • Confirm you copied the full key with no leading or trailing spaces.
  • Ensure the key is a Team Admin API key, not a personal or user key.
  • Verify your Cursor team still has API access enabled.

​
Action required

  • The stored key may have been revoked or expired in Cursor. Create a new Team Admin API key and connect again, or use Re-validate after updating the key in Cursor.
  • Only nOps administrators can resolve this status.

​
Admin Only on the card

  • You are signed in as a member, not an administrator. Ask an org admin to connect or manage Cursor, or request the administrator role in nOps.

​
No account found in Budgets

  • nOps matches nOps users to Cursor members by email. Confirm emails match, or switch to All in the seat table to see unmatched users.

​
Rate limited

Cursor limits Admin API requests per team. If you see a rate-limit error, wait a minute and try again.

​
Still stuck?

Contact your nOps administrator or nOps support with the time of the error (not the API key itself).

​
Reference