Skip to main content
A trace is one complete agent run: its input, LLM calls, tool calls and output. Evaluations, regression checks and datasets all read traces. The SDK sends them for you: give your agent its framework’s agent_config(). To read one, see Read a run. Scores and verdicts are on Evaluations.

Endpoints

Search traces

Search is GET /api/v1/traces with query parameters: there’s no separate search route. Every filter is optional. ?agent_name= with an empty value answers 400 rather than matching everything, so leave out a filter you don’t want. An unknown status, source_type, child_status, prompt_source, experiment_arm or sort answers 422.
It returns traces, total, limit, offset and target_manifest_id.

Core filters

There’s no filter on a numeric score. Filter on eval_verdict, then read each trace’s eval_score.

Prompts and experiments

Manifests and training verdicts

Multi-agent, tools and skills

Paging and order

Structure

A trace has two kinds of children: