Claude Onboarding

Why this matters: Claude usage across an organization is billed at the account level, but that total doesn't tell you which team or workflow is driving it. Connecting your Claude Enterprise account here brings that usage into Mavvrik's AI Assistant dashboards, the same way other AI spend is tracked.

Before onboarding your Claude Enterprise account, log in to Claude.ai as a Primary Owner and follow the steps below to capture the Organization ID & API key

Login to Claude.ai as Primary Owner
Navigate to Organization Settings, scroll to the bottom of the page and copy the Organization ID
Navigate to Analytics - API Keys page
1. Enable programmatic access
2. Create a key with read:analytics and read:spend_limits scope and copy the generated key

Steps to perform in Mavvrik

Go to the Menu
Click on Admin → Accounts →GenAI Accounts
Click on the '+ Account' button
Select Claude
Enter Organization ID & API Key
Click on 'Connect'

After onboarding is completed, allow up to 24 hours for data ingestion. Once ingestion is complete, cost will be visible under GenAI > Assistants > Cost.

Troubleshooting

If the account does not connect, verify the credentials and account details entered in Mavvrik.
If a permission error appears, confirm that the configured account has the access required by the onboarding steps.

FAQs

How long does it take for Claude usage to show up in Mavvrik?
Up to 24 hours after onboarding completes. Once ingestion finishes, cost is visible under GenAI > Assistants > Cost.

What permissions does the API key need?
The key must be created with read:analytics and read:spend_limits scope, and only a Primary Owner can generate it from the Analytics - API Keys page.

What does Mavvrik's Claude Cowork and Code feature do?

It attributes Claude Code and Claude Cowork spend across users, teams, sessions, models, token types, operations, LLM calls, tool calls, latency, errors, traces, and related activity signals.

Where does the cost data come from?

Cost and aggregate usage data come from Claude Analytics APIs.

Where does the activity data come from?

Session-level activity comes from Claude Code and Claude Cowork telemetry sent to Mavvrik through OpenTelemetry.

Why does Mavvrik need both APIs and OpenTelemetry?

The APIs provide the cost foundation. OpenTelemetry provides the session-level activity needed to understand what happened inside the workflow. Mavvrik combines both so teams can connect spend to behavior.

Does every user need to configure anything?

No. The integration is configured at the organization level. Individual users do not need separate Mavvrik setup.

Does Mavvrik replace Claude billing?

No. Claude remains the billing source. Mavvrik adds attribution, investigation, allocation, and governance on top of Claude spend.