Agent Cost & UsageConnect eve

Connect eve

Use this integration for agents built with the eve framework.

eve provides native OpenTelemetry instrumentation through agent/instrumentation.ts. Configure that instrumentation to export agent telemetry directly to Mavvrik. The Mavvrik SDK is not required.

Eve automatically discovers agent/instrumentation.ts and runs it at server startup before the agent code. Existing model and tool logic does not need to be rewritten.

Requirements

You need:

• an eve agent application;

• access to the agent project;

• permission to install the OpenTelemetry packages shown in the Mavvrik Connect step;

• permission to register an agent in Mavvrik.

1. Register the eve agent

In Mavvrik, go to Admin → Accounts → Agents, click + Agent, and select eve.

Configure:

Continue to Connect.

2. Install the OpenTelemetry exporter

Install the packages shown in the Mavvrik Connect step.

For npm, the setup uses the eve/Vercel OpenTelemetry integration together with the OpenTelemetry trace SDK and OTLP HTTP exporter.

npm install @vercel/otel @opentelemetry/sdk-trace-base @opentelemetry/exporter-trace-otlp-http

The Mavvrik SDK is not required for this integration.

3. Configure agent/instrumentation.ts

Create or update:

agent/instrumentation.ts

Copy the instrumentation configuration from the Mavvrik Connect step.

The configuration:

• registers eve's OpenTelemetry provider;

• exports traces to the Mavvrik OTLP endpoint;

• authenticates the export with the Mavvrik tenant and API key;

• includes mvk.agent_id and mvk.agent_name so telemetry is attributed to the registered agent.

Keep both mvk.agent_id and mvk.agent_name in the instrumentation configuration. Without the agent attributes, cost can appear as Unattributed.

Eve discovers agent/instrumentation.ts automatically when the agent starts.

4. Configure the Mavvrik connection values

Set the values shown in the Mavvrik Connect step:

MVK_AGENT_ID=<agent-id>
MVK_API_KEY=<api-key>
MVK_TENANT_ID=<tenant-id>
MVK_ENDPOINT=<mavvrik-ingest-endpoint>

Store the API key in the deployment environment or secret manager. Do not commit it to source control.

Restart or redeploy the eve agent after changing the instrumentation or environment configuration.

5. Add user and business attribution

This step is optional.

Eve exposes the step.started instrumentation event for adding per-model-call values through runtimeContext. Use it for values already known by the application, such as user identity or business tags.

The Mavvrik Connect step shows an example using fields such as:

user.id
user.email
mvk.tags

Use stable business dimensions that are appropriate for telemetry export. mvk.tags can carry additional business tags as a JSON object when required.

What Mavvrik receives from eve

Eve exports an OpenTelemetry trace hierarchy for agent turns, model calls, and tool calls. Mavvrik uses the exported telemetry for agent cost and execution visibility, including fields available on the spans such as:

• agent identity;

• model and provider information;

• input/output and related token usage when emitted;

• duration and status;

• session, turn, and step relationships;

• model-call and tool activity;

• optional user and business attributes added through runtimeContext.

Mavvrik calculates cost from the model and usage data received from eve.

Data handling

Eve controls whether full model inputs and outputs are recorded on its OpenTelemetry spans through recordInputs and recordOutputs in defineInstrumentation.

Mavvrik does not require full prompt or response content for standard cost reporting. For sensitive, regulated, or production data, review these eve settings and the organization's data-handling requirements before exporting content.

For example:

export default defineInstrumentation({
  recordInputs: false,
  recordOutputs: false,
  // setup and optional events
});

See the eve instrumentation guide for the framework's current telemetry and runtime-context behavior: https://eve.dev/docs/guides/instrumentation

Verify the integration

After registration:

1. Start or redeploy the eve agent.

2. Run one known agent session.

3. Open Home → Agentic → Cost and locate the registered agent.

4. Confirm model usage and cost appear.

5. Open Home → Agentic → Sessions and inspect the captured execution.

6. If user or tag attribution was configured, confirm those values appear on the captured activity.

It may take up to 24 hours for new eve agent data to appear.

Troubleshoot eve data

Agent activity does not appear

Confirm:

• agent/instrumentation.ts exists in the eve agent project;

• the OpenTelemetry packages shown in the Connect step are installed;

• MVK_AGENT_ID, MVK_API_KEY, MVK_TENANT_ID, and MVK_ENDPOINT are configured;

• the agent was restarted or redeployed after configuration;

• the agent has completed at least one model request.

Activity appears as Unattributed

Confirm the instrumentation configuration includes mvk.agent_id and mvk.agent_name, and that MVK_AGENT_ID matches the agent registered in Mavvrik.

User or business attribution is missing

Confirm the step.started event returns the expected values through eve's runtimeContext.

Model activity appears but cost is missing

Confirm the exported model spans contain the model identity and usage fields required for pricing.

Verify the complete setup