Skip to main content

Overview

Venice provides visibility into your Claude Enterprise environment by reading organization activities through the Anthropic Compliance API. The connector is read-only. Venice does not change any settings in your Claude Enterprise account.

Prerequisites

  • A Claude Enterprise plan
  • The Primary Owner of the Anthropic tenant, to enable the Compliance API and create the API key
Enable the Compliance API before creating the API key. Key scopes are fixed at creation, so a key created before the Compliance API was enabled must be replaced.

Configuration Steps

1

Configure connector in Venice

  1. From the Venice portal Data Connectors page: https://app.venice.io/data-connectors
  2. Configure a new connector, “Claude Enterprise”
  3. Enter a Connector Name to identify the connector on the Venice platform, for example claude-enterprise. This name does not affect your Claude Enterprise account.
  4. Optionally, click + Add Description
2

Enable the Compliance API

In claude.ai, open the Enterprise parent organization, go to Organization settings → API (claude.ai/admin-settings/api-access), and enable the Compliance API.In Venice, select The Compliance API has been enabled to confirm.
3

Create an API key

In claude.ai, as the Primary Owner:
  1. Open Organization settings → API and create a new key
  2. Select the following scopes:
These scopes cover every read the connector makes.
  1. Paste the key into the Enterprise API key field in Venice
4

Choose a scan scope

Select which organizations under the parent Venice scans:Organizations – Scan only the organizations you list. Enter a comma-separated list of organization IDs in the Organization IDs field.All organizations – Scan every organization under the parent.
5

Validate and save

Click Test Connector, then click Save Configuration.
Test Connector checks that the configuration is complete and validates the API key with Anthropic. If the key is invalid or missing the read:org_audit scope, 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

Only the Primary Owner of the Anthropic tenant can enable the Compliance API and create the key. Verify that:
  • You are signed in to claude.ai as the Primary Owner
  • You opened the parent organization, not a child organization
If the key doesn’t offer the read:org_audit scope, it was likely created before the Compliance API was enabled. Enable the Compliance API, create a new key with read:org_audit, and replace the key in Venice.
Test Connector confirms the API key is valid. If no data appears after a successful test, verify that the organization IDs in the scan scope belong to the same parent organization.

Next Steps

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

Access Security Dashboard

View your Claude Enterprise activities in the Venice dashboard.