Cursor

Pull Cursor usage and spend into Flowstate so it sits alongside Copilot, Claude and the rest. See who is actually using Cursor, who is idle, and which teams are getting their money's worth.

What syncs

Cursor reports at the member level, so this is one of the few connectors where money and people arrive on the same row:

Data	Grain
Daily usage	Per team member, per day
Amount charged	Per team member, per day, in the currency Cursor bills you

What you'll see in Flowstate

• Spend by person — who is using Cursor and what it costs, including people not yet imported as employees (they auto-link when you import your team).
• Spend reconciliation — Cursor's charged amounts next to Agent telemetry. See Spend.
• Per-project attribution — with the Flowstate Agent, Cursor usage is attributed to projects and people. See Attribution.
• Cost per team — Cursor spend rolled up by engineering team.

Getting started

You need access to your Cursor team's dashboard settings.

1. Open the Cursor dashboard → Settings → Cursor Admin API Keys and generate a key
2. Copy it straight away — it starts with key_ and is shown once
3. In Flowstate, open Settings → Integrations → Cursor, paste the key and click Verify and connect — Flowstate makes one read-only call to check it works before saving anything

How syncing works

Usage syncs hourly, and the first connect backfills history automatically.

Cursor accepts at most 30 days per request, so the first backfill walks your history in chunks and takes a little longer than a single-call provider. Cursor asks that its usage endpoints are polled no more than once an hour, which is exactly the cadence Flowstate uses.

If a key is rotated or revoked, the connection shows Cursor's real error on its provider page. Use Replace key on that connection to paste a new one — the history stays.