Connect Cursor

Connecting Cursor brings your team's spend and usage into Helias, so your AI tooling costs sit next to your cloud spend.

The connection is one Cursor team. Helias reads it through Cursor's Admin API, using a team key you create.

This takes about two minutes.

Before you begin

A Cursor Teams or Enterprise plan. Individual plans have no team for Cursor to report spend on.
Team Admin access in Cursor, so you can create the key.

You also need a Helias account, which is granted by request and approved by a person. Start at Get access if you do not have one yet.

How the connection works

Cursor offers no keyless option, so an API key is the only way in. The key is what identifies the team, which is why a team key is required and a personal key will not work. It reads cost and usage and nothing else.

The key passes through the onboarding app only in memory during the connection. It is never written to our database, never appears in a log or an error message, and comes to rest only in the environment dedicated to your organization, which is a separate AWS account per customer. Rotate or revoke it in Cursor at any time.

Connect

Create a Team Admin API key
Open your Cursor dashboard and select API Keys. Select the Team tab, create a key with the Admin scope, and name it.
A personal key will not work. Cursor shows the key only once.
Paste the key and name the team
Cursor exposes no team name on its API, so the label you choose is how the connection appears in your list of connections.

Verify the connection

Helias checks the key before storing anything. The check authenticates against the Admin API and resolves your team id, which is what identifies the connection. If it fails, nothing is stored and no key is kept.

After you connect

Your first data appears in Helias within 24 hours of a successful connection, and you get an email when the first insights are ready.

Until then the connections page shows a collection status: Pending while collection has not started, In progress while it runs, and Completed once data is flowing.

Helias checks your access at connect time, not continuously

Every grant is verified when you connect, and a failure names the grant that is missing. Afterwards Helias does not re-check. If you revoke the access on your side later, collection stops but the connections page keeps showing the provider as connected until you disconnect there too.

Limits

Individual plans are not supported. Cursor reports spend per team, and an individual plan has no team.
One team per connection. Connect each team you want to track.

Troubleshooting

Cause	Resolution
`Invalid Team API Key`	The key is wrong, was revoked, or is a personal key. Create a new key under the Team tab with the Admin scope.
`You must be a member of an enterprise team to access this resource`	The key belongs to an account without a team Cursor will report on. Confirm your plan is Teams or Enterprise.
The key was created but is rejected	Confirm you selected the Team tab and the Admin scope. A key created under a different tab or scope authenticates as you rather than as the team.

Disconnecting

You can disconnect at any time from the connections page. Disconnecting releases collection, and the API key you provided is deleted.

What stays behind is nothing on our side, though the key still exists in Cursor. Revoke the key in your Cursor dashboard.