Skip to content

Start from the framework you use

Connect agents built with LangChain, LangGraph, CrewAI, the OpenAI Agents SDK, the Claude Agent SDK or the Vercel AI SDK, and see exactly what each path reports.

Frameworks

Choosing a path

There are three ways in. They differ in what they can see and what they can do.

PathSeesCan decideRecommended for
OpenTelemetryRuns, model calls with token counts, tools and steps, from the framework's own instrumentationNothing: it only reportsLangChain and LangGraph, CrewAI, Vercel AI SDK
Python or Node SDKWhat you wrap: runs, spans and outcomes, and model calls through an instrumented OpenAI or Anthropic clientPause, resume and cancel at checkpoints, and approval of exact actionsOpenAI Agents SDK, Claude Agent SDK
Toolcaise ConnectEvery model call made through OpenAI- or Anthropic-compatible APIs, measured by the connectorStops the run at time, token, cost or call limits; pause, resume or stop from the dashboardAny agent you start from a command line

They combine. An OpenTelemetry trace and an SDK run are separate runs in Toolcaise, so use the SDK where a person has to decide and OpenTelemetry for the full picture.

Any OpenTelemetry exporter

Any agent that exports OpenTelemetry traces over OTLP/HTTP can report to Toolcaise with environment variables alone:

Environment
OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=https://toolcaise.com/api/v1/otlp/v1/traces
OTEL_EXPORTER_OTLP_HEADERS=Authorization=Bearer%20<agent credential>
OTEL_EXPORTER_OTLP_COMPRESSION=gzip
OTEL_METRICS_EXPORTER=none
OTEL_LOGS_EXPORTER=none

The %20 is required: header values in these variables are URL-encoded. Toolcaise reads the OpenTelemetry GenAI conventions, OpenInference, OpenLLMetry and the Vercel AI SDK's attributes; a trace with none of them is accepted and not stored.