Setup Claude Cowork

Claude Cowork telemetry is enabled once, by an organization administrator, from the Claude for Work admin console. There is no per-developer install: once an admin points Cowork at Revenium's OTLP endpoint, Anthropic exports usage for every authenticated Cowork user in the organization automatically.

This differs from the per-user CLI onboarding used for Claude Code, Cursor, Gemini, GitHub Copilot, and Codex, and Cowork does not support historical backfill — telemetry is real-time only, captured as each Cowork request completes.

Requirements:

• Claude for Work (Teams or Enterprise) with Cowork enabled

• Administrator role with access to the Organization / Cowork settings in the Claude admin console

• A Revenium metering key (rev_mk_*) from your Revenium account

• Outbound connectivity from Anthropic's export to https://api.revenium.ai

Claude Cowork evolves quickly. Anthropic updates the admin console layout and monitoring fields frequently. If a screen does not match exactly, look for the Monitoring / OTLP / observability section under your organization's Cowork settings. The Revenium-specific values below — the endpoint URL, the x-api-key header, and the protocol — are the values to keep consistent.

Steps:

1. In Claude Desktop, open Organization → Co-work → Monitoring (admin access required).

2. Enable OTLP / telemetry export.

3. Set the OTLP endpoint and headers to the Revenium values:

Field	Value
OTLP endpoint	https://api.revenium.ai/meter/v2/otlp
Header	x-api-key: rev_mk_your_tenant_yourkey
Protocol	http/json

Use a Revenium metering key (rev_mk_*). Do not use an Anthropic/OpenAI provider key here — provider keys authenticate model calls, while the Revenium key authenticates telemetry ingest and identifies your Revenium tenant.

1. Save the configuration.

Telemetry begins flowing for all authenticated Cowork users on their next session. Your Revenium tenant is identified by the metering key.

Verifying Your Configuration

Ask a user to run a brief Cowork session. Usage should appear in Revenium under Intelligence → AI Assistants after the next telemetry flush.

If no usage appears, confirm your data is actually reaching Revenium with a one-line self-test from any terminal — substitute your metering key:

curl -sS -o /dev/null -w "%{http_code}\n" \
  -X POST "https://api.revenium.ai/meter/v2/otlp/v1/logs" \
  -H "x-api-key: rev_mk_your_tenant_yourkey" \
  -H "Content-Type: application/json" \
  -d '{"resourceLogs":[]}'

Interpret the response:

• 200 / 202 — your endpoint and key are reaching Revenium correctly. If usage still doesn't show, recheck the metering key is active and that Cowork users have run sessions since the config was saved.

• 401 / 403 with an auth message — the metering key is wrong, inactive, or not a rev_mk_* key. Generate/confirm the key in your Revenium account.

• 403 with no auth body, or a connection failure — the request is being stopped before it reaches Revenium (for example a corporate network or proxy). Contact Revenium support with your egress IP range so we can confirm connectivity.

Field reference

• OTLP endpoint — https://api.revenium.ai/meter/v2/otlp. Cowork appends the OTLP signal path (/v1/logs) automatically.

• x-api-key — your Revenium metering key (rev_mk_*). Note Cowork uses the x-api-key header, not an Authorization: Bearer header.

• Protocol — http/json.

Optional Internal Attribution

The configuration above is enough for correct metering and dashboard attribution. Cowork usage lands under your tenant's default attribution, which is right for most customers.

If you want to sub-segment Cowork usage within your Revenium tenant — for example to compare spend across business units — and your Cowork admin console exposes custom OTLP resource attributes, Revenium recognizes:

• organization.name — a business unit, department, or cost center

• product.name — the application or use case

Resource attribute formatting: no spaces in values (use underscores or camelCase), and values are case-sensitive — pick a canonical form and use it consistently.

Billing Classification

Claude Cowork is metered by usage (provider-metered) rather than seat-based. The AI Assistant pricing mode team setting controls whether Cowork telemetry counts as real API spend in Revenium-wide reporting or stays scoped to AI Assistant analytics.

Related

• AI Assistant Data Reference — the full Cowork data schema and OTLP transport details

• Setup Claude Code — the equivalent managed-settings flow for Claude Code