Skip to main content
Trace data can help correlate a conversation with work performed by its supporting services. Threetone currently exposes a representation for trace data already stored with a conversation.
The conversation read path does not generate spans or export telemetry. No first-party collector setup or end-to-end trace production workflow is released by this API.
You need an accessible conversation ID. A transcript alone does not imply that trace data exists.
1

Request the trace representation

Call Get conversation details with format=opentelemetry. The default format is json.
2

Inspect stored coverage

Check otlp_traces for an existing payload. If it is absent or null, record that trace evidence is unavailable. Repeating the request does not instrument an older conversation.
3

Keep correlation context

Retain the conversation, agent, branch, and version IDs with any trace investigation. Confirm timestamps and the producing service before attributing a delay to a model or tool.
Workspace webhook settings also accept webhooks.transcript_format=opentelemetry. Webhook delivery is unavailable, so this preference does not configure a functioning exporter. A future rollout needs verified producers, propagation, sampling, redaction, and a supported destination.
No. It exposes a stored field when present.
There is no verified public collector configuration or automatic export workflow to document yet.