Sample readiness
The experiment finished and its verdict is available.
These checks apply to every experiment for ticket-summary, whatever the source model. Changes apply to new runs and start a fresh evidence pool, so earlier runs are not mixed with runs under different rules.
Added to the judge's instructions. A candidate that violates them is judged not equivalent.
Checked without the judge. A candidate that fails it counts as not equivalent and skips the judge call. If the original output fails it too, the schema is likely wrong, so the judge decides and the miss is only reported.
Test whether ticket-summary answers as well with a shorter prompt: less conversation history, or a shorter system prompt that the judge model proposes. TrAIce replays 30 captured requests on claude-sonnet-4-6 with the shorter prompt, and the judge compares each answer with the one your application got. Nothing changes in your traffic.
This demo is read-only. Create a workspace to run a trial.
Once a week, TrAIce groups up to 500 of this workload's sampled requests by what they ask for and shows what each group costs. The judge model on Google Vertex AI names each group from a few of its requests. Names are kept only as long as the samples they came from (at most 14 days); the counts and costs stay.
Analysed Nov 4, 2026 from 500 sampled requests, for $0.035 of replay budget. Next analysis around Nov 11, 2026.
| Topic | Requests | Cost | Per request | Input tokens | Output tokens | Errors | Retried |
|---|---|---|---|---|---|---|---|
| Escalated billing disputesLong ticket threads about a disputed charge, summarized for an agent. | 38%190 | 39% | $0.69852 | 230,292 | 9,399 | 2% | 6% |
| Integration and API issuesTickets about failing webhooks, API errors, or broken integrations. | 33% |
These complete, unexpired prompt and response pairs can be selected for an experiment. Opening sample content is audited.
| Case | Captured | Prompt tokens | Response tokens | Production latency | Expires | Availability | Sample details |
|---|---|---|---|---|---|---|---|
| 11 | Nov 8, 08:39 PM |
| 33% |
| $0.67786 |
| 222,707 |
| 9,246 |
| 1% |
| 6% |
| Feature requestsCustomers describing a capability they want added. | 29%145 | 28% | $0.66592 | 217,963 | 9,216 | <1% | 7% |
Shares are of the 500 sampled requests analysed. Per request, tokens, errors and retries are averages over each topic's requests.
| 44229 |
| 1742 |
| 1,268 ms |
| Nov 22, 08:58 PM |
| Used in latest experiment |
| View sample |
| 12 | Nov 8, 08:38 PM | 101196 | 5111 | 2,378 ms | Nov 22, 08:58 PM | Used in latest experiment | View sample |
| 13 | Nov 8, 08:37 PM | 216723 | 8935 | 3,885 ms | Nov 22, 08:58 PM | Used in latest experiment | View sample |
| 14 | Nov 8, 08:37 PM | 39806 | 1608 | 636 ms | Nov 22, 08:58 PM | Used in latest experiment | View sample |
| 15 | Nov 8, 08:36 PM | 60859 | 2573 | 1,546 ms | Nov 22, 08:58 PM | Used in latest experiment | View sample |
| 16 | Nov 8, 08:36 PM | 114996 | 4762 | 1,115 ms | Nov 22, 08:58 PM | Used in latest experiment | View sample |
| 17 | Nov 8, 08:35 PM | 25476 | 1099 | 635 ms | Nov 22, 08:58 PM | Used in latest experiment | Close |
Sample case 17 evidenceCaptured prompt and source response available for the next experiment. used Captured promptNorthstar support case 17: resolve the ticket-summary request with the account policy and cited help-center context. Original responseclaude-sonnet-4-6 Resolved ticket-summary case 17 with the correct policy, next step, and customer-safe explanation. | |||||||
| 18 | Nov 8, 08:35 PM | 194608 | 8265 | 1,674 ms | Nov 22, 08:58 PM | Used in latest experiment | View sample |
| 19 | Nov 8, 08:34 PM | 69351 | 3002 | 599 ms | Nov 22, 08:58 PM | Used in latest experiment | View sample |
| 20 | Nov 8, 08:33 PM | 22822 | 1019 | 213 ms | Nov 22, 08:58 PM | Used in latest experiment | View sample |