Switch

Switch to Uncoil.

Already tracing your agents somewhere else? Move in an afternoon. Run both tools side by side, then turn the old one off.

The plan

Four steps, any tool.

  1. 1Create an Uncoil project and copy its API key. It takes about a minute.
  2. 2Add the Uncoil SDK, or point your OpenTelemetry exporter at Uncoil. Leave your old tool on.
  3. 3Run your agent. Check that every run shows its model calls, tool calls, cost and errors.
  4. 4After a week of matching results, remove the old tool.

Coming from

Pick your current tool.

Langfuse

  1. Create an Uncoil project and copy its API key.
  2. Point your OpenTelemetry exporter at Uncoil's OTLP endpoint. Langfuse also takes OTLP over HTTP, so most setups only change the URL and the key.
  3. Run both for a week on the same traffic and compare cost and latency numbers.
  4. Export what you need from Langfuse before you turn it off, since history does not move across.
Uncoil vs Langfuse

LangSmith

  1. Create an Uncoil project and copy its API key.
  2. Replace the LangSmith tracing variables with an OpenTelemetry exporter that points at Uncoil's OTLP endpoint.
  3. Keep LangGraph and LangChain as they are. Only the destination of the traces changes.
  4. Run both side by side for a week, then turn LangSmith off.
Uncoil vs LangSmith

Helicone

  1. Create an Uncoil project and copy its API key.
  2. Add the Uncoil SDK or an OpenTelemetry exporter to your agent code.
  3. Keep Helicone as your gateway if you use its routing. Remove only the logging you no longer need.
  4. Check that tool calls now show inside each run.
Uncoil vs Helicone

Using something else, or plain OpenTelemetry? Uncoil takes standard OTLP spans over HTTP, so most setups only change the endpoint and the key. See the OpenTelemetry guide or the quickstart.

Questions

Before you move.

Do I have to rewrite my instrumentation?
Usually not. Uncoil accepts OpenTelemetry (OTLP) over HTTP, so instrumentation that already exports OpenTelemetry spans only needs a new endpoint and key. Otherwise add the TypeScript or Python SDK.
Can I run Uncoil next to my current tool?
Yes, and we suggest it. Send traces to both for a week, check that runs and tool calls look right, then switch the old one off.
Will my old traces move over?
No. Uncoil starts with new traces. Keep your old tool read-only for as long as you want the history.
What does it cost?
Free for 25k spans a month. Pro is a flat $19 and Team a flat $39. Use the bill calculator to compare your own traffic.
Does Uncoil sit in my request path?
No. Uncoil receives traces after the work is done, so it cannot slow or break a model call.

Try it next to your current tool.

Free to start. First trace in minutes.