How Intertrace works

Your application or gateway emits traces to Intertrace via HTTP (Bearer API key). Each trace contains spans representing steps, tool calls, and outcomes. Optional dual-write can mirror critical fields into legacy gateway event tables for backward compatibility.

Inline: SDK or thin wrapper around your HTTP client records spans synchronously around each call. Lowest latency for local debugging.

Async: Webhook or queue consumer posts batches to the ingestion API. Best for high throughput and decoupled pipelines.

If you already route model traffic through Bastion Gateway, gateway events may be correlated with traces. Direct integration sends traces without the gateway; both paths are supported for the MVP.