Connect Anthropic

Connecting Anthropic brings what your people use across Claude into Helias, so your AI spend sits next to your cloud spend instead of in a separate invoice.

The connection is your Claude organization, with its workspaces beneath it. Helias reads it through the Claude Enterprise Analytics API, using a key you create.

This takes about two minutes.

Before you begin

A Claude Enterprise plan with analytics enabled. Anthropic turns analytics on for your organization. If the Analytics API keys page is unavailable, contact Anthropic support.
Primary owner access in claude.ai. No other role can create an Analytics API 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

Anthropic offers no keyless option, so an API key is the only way in. The key you create is scoped to read:analytics and reads usage and cost. It cannot call a model, change settings, or read message content.

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 claude.ai at any time.

Connect

Create an Analytics API key
Open your Analytics API keys page in claude.ai. Under Analytics API, turn on the Access toggle. Create a key, keep the read:analytics scope, and name it.
Use a key dedicated to Helias so you can rotate it on its own. Claude.ai shows the key only once.
Paste the key into the app
An Analytics API key starts with sk-ant-api01-. If yours starts with sk-ant-admin01- it is a Claude Console Admin key, which the Analytics API does not accept, and sk-ant-api03- is a standard key that can only call the model.
Name the organization
The Analytics API exposes no organization name, 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 Analytics API and resolves your organization, 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

Data starts on 1 January 2026. Nothing before that date is available from Anthropic.
Claude bought through Amazon Bedrock is part of your AWS bill and appears in your AWS connection.
Claude bought through Google Vertex AI is part of your Google Cloud bill and appears in your Google Cloud connection.
Workspaces are a snapshot. They ride on the organization connection rather than connecting or collecting on their own.

Troubleshooting

Cause	Resolution
The key is rejected	Check the key is still active in claude.ai, that it keeps the `read:analytics` scope, and that analytics is enabled for your organization.
The key starts with `sk-ant-admin01-`	That is a Claude Console Admin key. Create an Analytics key in your claude.ai organization settings instead.
The key starts with `sk-ant-api03-`	That is a standard API key, which can only call the model. Create an Analytics key instead.
The Analytics API keys page will not open	Anthropic enables analytics per organization, and the page refuses for anyone without it. Contact Anthropic support.
Creating a key is not offered	Only the primary owner of the organization can create an Analytics API key.

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 claude.ai. Revoke the key in your claude.ai organization settings.