Runtype
Changelog
FeatureAugust 16, 20261 min read

Send traces from any agent, wherever it runs

A standard OTLP/HTTP endpoint ingests traces from any GenAI-instrumented agent. Runs show up in Logs with a full trace tree, and can be captured as eval cases and replayed.

observabilitytelemetryevalsintegrations

Agents you did not build on Runtype can still be observed and evaluated on Runtype. Point a standard OpenTelemetry exporter at us and stop writing integration code.

OTEL_EXPORTER_OTLP_ENDPOINT=https://api.runtype.com/v1/otel
  • POST /v1/otel/v1/traces accepts OTLP/HTTP in both protobuf and JSON, gzip or deflate, authenticated with an API key carrying the new TELEMETRY:WRITE scope. Any agent emitting GenAI semantic-convention spans works with no Runtype-specific code.
  • Ingested runs appear in Logs and the trace tree next to runs Runtype executed, with model, token, and cost attribution projected from the spans.
  • Those runs are capturable as eval cases and replayable against the external agent, so you can measure whether a change helped even when the agent runs somewhere else entirely.
  • Agents built with the Vercel AI SDK can push runs through @runtypelabs/ai-sdk-adapter, and Flue agents get first-class instrumentation.

Guides: Reporting telemetry from an external agent and Instrumenting a Flue agent.