What telemetry.dev does
Trace model calls, tool steps, and MCP requests. Get an alert when cost or errors break from normal, change prompts without a deploy, and trace each eval run.
Features
Tracing
Follow model calls, tool steps, and retrievals in one trace, with the duration of each step.
See tracing- track_shipment
- 2,418ms
- 49%
MCP analytics
Spans, failures, and p95 duration by method and tool, from the client and the server.
See MCP analytics| Tool | Spans | p95 | Failed |
|---|---|---|---|
| create_refund | 2,330 | 2.4s | 18.0% |
| get_invoice | 5,912 | 640ms | 1.1% |
| check_inventory | 4,208 | 310ms | 0.2% |
| cancel_order | 1,077 | 880ms | 0.6% |
- Tool errorsAlerting
- Monthly budgetAll clear
- Agent loopAll clear
- Missing pricesNeeds more data
Prompt management
Versions, labels, and rollouts without a deploy. Compare the versions on real calls.
See prompt management- Error
- TimeoutError
- The operation was aborted due to timeout
- Parent
- chat gpt-4.1 · case 2
- evaluate refund-policy
Connect your application
Use a telemetry.dev integration, or keep your OpenTelemetry setup and change where it exports.
- Integrations
A setup guide for each provider, framework, coding agent, and SDK
- OpenTelemetry
Keep your existing instrumentation and export standard OTLP/HTTP
- Connect an AI agent
Let an MCP client read the traces, logs, and usage of one workspace
- Alternatives
How telemetry.dev compares with LangSmith and Langfuse
Trace your next AI request
Choose an integration, add your project API key, and run an instrumented request.
Start free
30,000 ingestion units a month, one per span, log record, or metric data point. No credit card required.
npm install @telemetry-dev/sdkTalk to an engineer
Our team shows you tracing, cost tracking, and privacy controls for the frameworks and model providers that you use.