Traces Overview

Store and explore evaluation, training, and agent traces

Prime Traces stores the traces from evaluation, training, and agent workloads so you can view, search, download, and delete them. Open the Traces dashboard in your personal or team workspace.

• Trace: one rollout or request, with its messages, model calls, score, and metadata.
• Episode: a group of traces produced together, such as a multi-agent rollout.
• Run: traces that share a run_id, with totals such as trace count and average reward.

Prime Traces currently supports the verifiers v1 trace format. An arbitrary JSONL file, an OpenTelemetry export, or a legacy sample archive is not a substitute for that format. See Uploading traces for supported inputs.

Prime Traces is enabled by default for platform runs that upload traces. Uploads incur ingestion and storage charges. See Pricing and settings to review the rates or disable uploads for your workspace.

Legacy evaluation and training sample storage will be retired on November 6, 2026. Existing data is not migrated automatically. Request and download your legacy archive before that date.

Python SDK

Create an API key with the Prime Traces permissions you need. The SDK reads credentials from PRIME_API_KEY or your prime login configuration. Set PRIME_TEAM_ID for a team’s traces. See authentication and workspace selection.

uv add prime-traces

Upload a supported trace file using the upload guide, then query its run:

from prime_traces import TracesClient

with TracesClient() as client:
    page = client.list(run_id="your-run-id", reward_min=0.9)
    for summary in page.items:
        print(summary.trace_id, summary.score)

    if page.items:
        raw = client.get_raw(page.items[0].trace_id)

    matches = client.search("Traceback", run_id="your-run-id")

CLI

prime traces list --run-id your-run-id
prime traces get <trace_id> --raw
prime traces search "Traceback" --run-id your-run-id

Next steps

• Uploading traces: supported formats, authentication, SDK, and CLI.
• Pricing and settings: charges, workspace limits, and upload controls.
• Viewing and deleting traces: search, downloads, deletion, and troubleshooting.
• Legacy storage retirement: keep a copy of your existing evaluation and training data.