Visionality for Cursor · AI IDE
Govern the Cursor prompt the same way you govern the Copilot prompt.
Cursor is the modern AI IDE; high-growth adoption at startup and mid-market software teams. The CFO question — what is each developer doing, and which sprint paid for it — applies the same way it does for GitHub Copilot, with the added complexity that Cursor's per-user pricing makes the seat-rate question explicit.
Visionality's Cursor connector ingests per-user usage telemetry; the gateway sits between Cursor's API and the underlying LLM with the binding-key envelope wrapping every call. The per-developer chargeback CSV with Jira + Bitbucket repo attribution is the structural answer.
What Visionality does for Cursor
Tagged, governed, audited — at the call, not after the bill.
Cursor usage telemetry — per developer, per workspace.
Pulls per-user usage from Cursor's admin surface; cost rows tagged with workspace + developer identity land on request_logs.
Repo + Jira project mapping.
The Bitbucket + Jira connectors wire repo identity to project_id; every Cursor prompt from that repo carries the right attribution without metadata your developers have to remember.
Per-developer chargeback CSV for time-and-materials shops.
Software-services shops billing T&M (ArcTrade-shape buyers) drop the per-Cursor-prompt cost row into client invoices as an evidence appendix.
Compatible with Cursor's BYO-key model.
Cursor lets developers BYO LLM keys. Visionality's gateway sits between Cursor and the LLM provider; the BYO keys land in our envelope discipline with no developer behavior change.
Govern your Cursor AI spend in 30 minutes.
30-minute deploy. Bring your own LLM keys. Your existing SDK code works unchanged. The Cursor connector is shipped — operator wires credentials and you have a working audit trail before the coffee is gone.