Traces and model prices

What a trace is

A run is one job your agent did, end to end, such as “summarize this ticket”. It is made of steps: each model call and each tool call. ClickClacks stores token counts, not prompts. An output preview is optional, and you decide per step whether to send one.

Send your runs

Runs arrive as two special events, sent from your server with the server API and a server source’s key:

• one $agent_step for each completed step
• one $agent_run at the end, summing up the run

Use the real user ID (and session ID, if you have it) so each run joins the person’s other activity.

{
  "items": [
    {
      "event": "$agent_run",
      "distinct_id": "user_8412",
      "properties": {
        "trace_id": "trc_7f3a91c2d4",
        "run_name": "Summarize ticket",
        "agent_name": "support-bot",
        "source": "helpdesk",
        "outcome": "succeeded",
        "failure_reason": null,
        "started_at": "2026-09-25T14:03:11.402Z",
        "duration_ms": 8120,
        "step_count": 3,
        "tokens_in": 5210,
        "tokens_out": 830
      }
    }
  ]
}

$agent_run properties

$agent_step properties

Only the properties listed here are accepted on these two events. Until a run arrives, the Traces page shows No agent runs yet with a sample request and a Check for runs button.

Reading Traces

Open Traces under Data. Pick a date range. The page then shows:

• Runs, Finished cleanly, Typical run duration (with the 95th percentile, in wall-clock time) and Cost.
• Runs by outcome over time.
• A table of runs with their steps, duration and cost.

Narrow the table by searching run or agent names, by trace source, by person, or by outcome (Succeeded, Failed, Cancelled). These narrow the table only: the date range drives the cards and chart too. Export downloads the filtered runs as a CSV, with tokens.

One run

Click a run to see its Steps as a timeline, the output preview if you sent one, what the person did around the run, and who they are.

Model prices

ClickClacks doesn’t guess what a model costs. Runs without a price show a dash, and the page links to Set model prices.

1. Open Settings › Model prices. Any member can edit it.
2. Enter the Model name exactly as your steps send it, such as openai/gpt-5-mini.
3. Enter Input $ per 1M and Output $ per 1M tokens, as your provider lists them.
4. Click Save model price.

Run costs use these prices from then on.

Tips and gotchas

• Model names must match exactly. gpt-5-mini and openai/gpt-5-mini are different models to the price list.
• Send the run event last. It carries the outcome and totals.
• Previews are capped at 400 characters, and a run’s page shows the first 180.

Recipes