> ## Documentation Index
> Fetch the complete documentation index at: https://docs.venice.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Claude Platform Connector

> Connect Venice to the Claude Platform for visibility into users, API keys, workspaces, agents, and activities across your Anthropic organization

## Overview

Venice provides visibility into your Claude Platform organization by reading users, API keys, workspaces, agents, sessions, and the activity feed through the Anthropic Admin and Compliance APIs.

The connector is read-only. Venice does not change any settings in your Claude Platform account.

## Prerequisites

* A **Claude Platform** organization
* The **admin** role in the Claude Platform, to enable the Compliance API and create the Admin API key
* The **developer** role in the Claude Platform, to create the service account used to create the Platform API key

> [!WARNING]
>
> Enable the Compliance API **before** creating the Admin API key. A key created earlier can't read the activity feed, and agents created before enablement are never attributed to an owner.

## Configuration Steps

**1. Configure connector in Venice**

1. From the Venice portal Data Connectors page: [https://app.venice.io/data-connectors](https://app.venice.io/data-connectors)
2. Configure a new connector, **"Claude Platform"**
3. Enter a **Connector Name** to identify the connector on the Venice platform, for example `claude-platform-prod`. This name does not affect your Claude Platform account.
4. Optionally, click **+ Add Description**

**2. Enable the Compliance API**

In the Claude Platform, open **Settings** → **Security** and turn on **Compliance API**.

In Venice, select **The Compliance API has been enabled** to confirm.

**3. Create the Admin API key**

As an admin:

1. In the Claude Platform, open **Settings** → **Admin keys** and create an Admin key
2. Paste the key into the **Admin API key** field in Venice

The Admin API key reads users, API keys, workspaces, and the activity feed.

**4. Create the Platform API key**

As a developer:

1. In the Claude Platform, open **Settings** → **Service accounts** and create a service account with the **Developer** role
2. Scope the service account to the workspaces Venice should read. You can select all workspaces or only some of them.
3. Create a Platform API key for the service account
4. Paste the key into the **Platform API key** field in Venice

The Platform API key reads agents and sessions.

**5. Choose a scan scope**

Select which workspaces Venice scans:

**Workspaces** – Scan only the workspaces you list. Enter a comma-separated list of workspace IDs in the **Workspace IDs** field, for example `wrkspc_01JwQvzr7rXLA5AGx3HKfFUJ`.

**Organization-wide** – Scan every workspace in the organization.

**6. Validate and save**

Click **Test Connector**, then click **Save Configuration**.

> [!NOTE]
>
> **Test Connector** checks that the configuration is complete and validates the API keys with Anthropic. If the keys are invalid, the test fails.

## Security & Trust

Venice leverages multiple layers of defense to protect key information and handles all critical facets of network and application security, including authentication, authorization and assurance.

As a security provider focusing on security architecture, our internal architecture from the ground-up has been designed for minimal manual intervention in the deployment & maintenance process, with a fully-automated production update process, greatly reducing the risks to the service and to customers' data.

The security program systematically evaluates our information security risks, considering the impact of company threats and vulnerabilities. The company is certified for **SOC2 type 2** standard, with an annual schedule of regular third-party audits and is **GDPR certified**.

Attention to customer input and industry trends help ensure that our security programs keep pace with a changing security landscape and meet evolving customer requirements.

## Troubleshooting

> [accordion] Can't create the Admin API key
>
> Only a user with the **admin** role can create Admin keys. Verify that you are signed in to the Claude Platform as an admin.

> [accordion] Activity feed is missing
>
> If Venice doesn't show activities, the Admin API key was likely created before the Compliance API was enabled. Verify that the Compliance API is on under **Settings** → **Security**, then create a new Admin key and replace it in Venice.

> [accordion] Agents show no owner
>
> Agents created before the Compliance API was enabled are never attributed to an owner. Only agents created after enablement show an owner in Venice.

> [accordion] Test Connector passes but no data appears
>
> **Test Connector** confirms the API keys are valid. If no data appears after a successful test, verify that:
>
> * The Platform API key belongs to a service account with the **Developer** role
> * The service account is scoped to the workspaces you want Venice to scan
> * The workspace IDs in the scan scope belong to the same organization

## Next Steps

Once your Claude Platform connector is set up, you can:

* Review Claude Platform users, API keys, workspaces, agents, and activities in Venice
* [Connect your AI clients to the Venice Identity Gateway](https://docs.venice.io/guides/identity-gateway-connecting-ai-tools.md)

> [card] [Access Security Dashboard](https://app.venice.io)
>
> View your Claude Platform activities in the Venice dashboard.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.