.png)
Register an Agent
Register an agent before installing the Mavvrik SDK. Registration creates the SDK agent identity used to attribute captured activity and provides the tenant ID, agent ID, and API key required by the SDK.
This page applies to Python and JavaScript / TypeScript SDK integrations. Langfuse, LiteLLM Proxy, and n8n use their own connection flows.
Decide what one agent represents
Use one agent for a stable deployable service or agent application that should be reported as one unit. The Agent ID is the long-lived identity used for cost and execution attribution and cannot be changed after registration.
|
Register separate agents when |
Keep one agent when |
|---|---|
|
Services are owned or reported separately |
They deploy together and should be reported together |
|
They represent different agent applications or business processes |
The difference is a customer, user, environment, use case, or workflow stage |
Do not register one agent per customer or environment. Use Add Business Context for customer, user, session, and use-case attribution, and use tags for deployment dimensions such as environment.
1. Open the Agents page
Go to Admin → Accounts → Agents and click + Agent. The registration drawer contains Setup and Connect steps.
2. Configure the agent
|
Field |
Configuration |
|---|---|
|
Agent ID |
Accept the generated value or use a stable readable identifier such as |
|
Agent Name |
Display name. It can be changed later. |
|
Description |
Optional description of the service, repository, or owning team. |
3. Copy the connection values
Open Connect and copy:
|
Value |
Environment variable |
Purpose |
|---|---|---|
|
Tenant ID |
|
Identifies the Mavvrik tenant |
|
Agent ID |
|
Attributes captured activity to this agent |
|
API key |
|
Authenticates SDK telemetry to Mavvrik |
4. Store the credentials
export MVK_TENANT_ID="your-tenant-id"
export MVK_AGENT_ID="your-agent-id"
export MVK_API_KEY="your-api-key"
Store the API key in the deployment environment or secret manager. Do not commit it to source control.
5. Continue with the SDK
Registration alone does not produce telemetry. Data appears after the SDK is running and a supported operation executes.