Claude Platform

Send OpenTelemetry traces of Messages API requests and Managed Agents sessions from the Claude Console to telemetry.dev.

The Claude Platform can send OpenTelemetry traces of your Messages API requests and Managed Agents sessions to telemetry.dev. You add telemetry.dev as a destination in the Claude Console. Each request then arrives as a trace, with a span for each model request, tool use, and agent turn. No code changes are needed. Anthropic offers this export as a beta.

What it captures

• One span for each Messages API request, with a span for each model request, server tool, MCP tool, and compaction inside it
• Managed Agents sessions: each turn, model request, tool use, and outcome evaluation
• Model, response ID, errors, and timing, with Anthropic’s stop reason as a span attribute
• Input, output, cache-read, and cache-write token usage, and thinking tokens when Anthropic reports them
• Prompts and responses, when the destination’s content mode is Full content

Get started

1. Create a telemetry.dev project API key. Keys use the td_live_... format.

2. In the Claude Console, open the organization’s OpenTelemetry settings and click Add destination. You need the admin role.

3. Fill in the destination:

   Field	Value
   Provider	Custom
   OTLP endpoint URL	https://ingest.telemetry.dev
   Request headers	authorization: Bearer td_live_...
   Content mode	Metadata only, or Full content to include prompts and responses
   Workspaces	The workspaces to trace

   Don’t add /v1/traces to the endpoint URL. The Console adds it.

4. Click Test in the destination’s More actions menu, then send a request. The destination shows Healthy within about a minute, and the trace appears in your project with the service name claude-platform.

Token usage

Anthropic reports a request’s usage on more than one span: on the API span for the request and again on each model request inside it. telemetry.dev counts each request once, following Anthropic’s counting rule. Model request spans inside a Messages API request show no usage of their own.

If you also export the Claude SDK’s own spans to telemetry.dev, the SDK span and the API span for a request carry the same usage. telemetry.dev counts the API span when it’s a child of the SDK span, and the SDK span still appears in the trace. That link needs the W3C trace context propagator registered in your application; see Anthropic’s trace context setup. Without the link, both spans count.

Good to know

• If your application already traces Anthropic calls with the telemetry.dev Anthropic integration, those calls arrive twice and their usage counts twice. Send the Console destination to a separate project, or use one of the two.
• Claude Platform on AWS doesn’t link SDK spans to API spans yet, so send them to separate projects or use one of the two.
• With Full content, prompts and responses go through your project’s capture and redaction settings like any other telemetry.
• With Full content, set Maximum content size in MB under Advanced settings to 0.75 or lower. telemetry.dev rejects requests larger than 4 MiB, and Anthropic doesn’t retry a rejected delivery.
• Anthropic delivers spans on a best-effort basis, so a span can occasionally be missing. telemetry.dev keeps one copy of a span that arrives more than once.