Skip to main content
The Anthropic connector reads your organisation’s claude.ai chats straight from Anthropic’s Compliance API. Every chat, on any device, arrives in Velatir as a session of prompts and responses, whether or not Velatir runs on that device. You connect once, with one key from your Claude organisation’s settings. There is nothing to install and nothing for your users to do.
The Compliance API is only available on Claude Enterprise. Claude Team has no API to read chats from. For Team, use Claude Cowork monitoring and Velatir for Desktop instead.

​
What It Brings In

Claude chats

Each chat becomes a session. Each prompt and its response become traces with their text, attributed to the person who started the chat.

The last 30 days

Chats from the 30 days before you connected, imported in the background.
Velatir also records which tools Claude used in a turn, by name, which shows when a connector or MCP server was involved. Tool inputs and results, uploaded and generated files, artifacts, and projects are not read. Cowork and Claude Code sessions are not read through this connector. Cowork reaches Velatir through its own monitoring export, and Claude Code through Velatir for Desktop, so nothing is counted twice.

​
Before You Start

A Velatir Administrator

Only an organisation Administrator can connect, reconnect, or disconnect. See Roles & permissions.

A Claude owner who can create the key

The primary owner of your Claude organisation, or an organisation owner. The primary owner turns the Compliance API on first. A key the primary owner creates covers the parent organisation and every linked one. A key an organisation owner creates covers their own organisation only.

A Compliance Access Key

Created in claude.ai under Organization settings → API. Its key starts with sk-ant-api01-.

​
Create the Key

In claude.ai, open Organization settings → API and create a Compliance Access Key with these two scopes: Do not add delete:compliance_user_data. Velatir never deletes anything.
A key’s scopes cannot be changed after it is created. If you miss one, create a new key.
Other Anthropic keys do not work. A Claude Console Admin API key (sk-ant-admin01-) only reads the Activity Feed, and a Claude API key (sk-ant-api03-) cannot reach the Compliance API at all. Velatir tells you which one you pasted.

​
Connect Claude Enterprise

Find Anthropic in the Inventory

In Velatir, open Inventory from the sidebar. If there is no Anthropic card, select Declare service(s) and declare Claude. The card then shows Declared · not connected.

Start the connection

Select Connect on the Anthropic card. The dialog lists what Velatir will pull.

Name it and paste the key

Give the connection a name, for example Anthropic · Production, and paste the Compliance Access Key. Select Connect.

Velatir checks the key

Velatir asks Anthropic for one record with each scope. When both work, the key is saved and the card shows the connection. If the key is refused, the dialog says why, and nothing is saved.
The key is stored securely and never shown again, not even in part.

​
After You Connect

Chats are dated when each prompt was sent and each answer finished, not when Velatir read them, so imported chats fill in Sessions and Insights from the most recent day backwards. Running the import again adds nothing twice. The Anthropic card shows no seats or plans. This connector brings conversations, not figures.

​
Managing the Connection

Select Reconnect on the connection and paste a new Compliance Access Key. The old key keeps working until the new one is verified, and everything already imported is kept.
Select Disconnect on the Anthropic card and confirm. Velatir deletes the key and stops reading straight away. Everything already imported stays in Velatir. Delete the key in claude.ai as well if you do not plan to reconnect.
Deleting or deactivating the key in claude.ai stops Velatir’s access. Velatir checks its access every 15 minutes, so the connection shows Action needed within that time. Everything already imported stays.

​
Troubleshooting

The key was created without read:compliance_activities, read:compliance_user_data, or both. Scopes cannot be added to an existing key. Create a new Compliance Access Key with both, and paste that one.
The key is a Claude API key or a Console Admin API key. Create a Compliance Access Key in claude.ai under Organization settings → API.
The Compliance API is probably turned off for your Claude organisation. Ask the primary owner to turn it on, then connect again.
New chats appear within about 15 minutes. A chat deleted in claude.ai before Velatir read it has no content left, so it is skipped. Chats Velatir already imported stay when they are deleted in claude.ai.

Connectors

How connectors work in general.

Claude Cowork

Send Cowork activity to Velatir.