Recorded run · data boundaries
Another partner’s account
A reseller asks for the status of an account another partner registered. The assistant’s lookups reach only the asker’s own accounts: watch what comes back, and what it answers.
Same request, same controls, two models: pick one
Run 01 of 30, as recorded
claude-opus-5.5 · recorded 29 Sep 2026 · synthetic data · answered by Google through OpenRouter, zero data retention
Or go one step at a time with the controls: the replay waits for you at every step.
Once it plays, this meter counts the conversation’s model calls, tokens, model time and cost.
Across the 30 recorded runs: $0.019 median per conversation ($0.011 to $0.033) · 7.8 s median model time.
The assistant’s steps appear here, one by one, with what the controls decided about each.
Audit trail
In production, this is the log your auditor or data protection officer reads: every action the assistant took and every decision the controls made, in order. Each entry is chained to the one before it, so an entry changed afterwards no longer matches.
Nothing yet: play the run above.
What a conversation costs
Per conversation (one partner request, read, checked and answered), over each model’s recorded runs that finished.
Claude Opus 5.5
30 conversations
- Cost, median
- $0.019 ($0.011 to $0.033)
- Model time
- 7.8 s
- Model calls
- 4
- Tokens in / out
- 5,772 / 489
Claude Sonnet 5.5
30 conversations
- Cost, median
- $0.011 ($0.0068 to $0.018)
- Model time
- 6.9 s
- Model calls
- 4
- Tokens in / out
- 6,213 / 504
- Claude Opus 5.5: about $19 a month at the median, $11 to $33 across the recorded runs.
- Claude Sonnet 5.5: about $11 a month at the median, $6.80 to $18 across the recorded runs.
Claude Opus 5.5: about $19 a month; Claude Sonnet 5.5: about $11 a month
Model fees only, at OpenRouter’s prices on 29 Sep 2026, for partner requests like this one. Not included: hosting, integration, and the people who review what the controls hold. Costs are OpenRouter’s billed cost per call, recorded in each signed run file; model time is OpenRouter’s record of each call’s response time, fetched 29 Sep 2026 and signed in timings-2026-09-29T05-31-42-707Z.json.
For technical teams: verify these recordings
Every recording is signed. Checking it shows the files have not changed since QAIZEN signed them: the steps, the model, the date and the costs. It says nothing about when they were recorded. The replay always shows run 01, the first one recorded; every run is published.
claude-opus-5.5, run 01
claude-sonnet-5.5, run 01
Signing key fingerprint (SHA-256): 970159aedc46a8a4be37522e5711f7c21af56d26c5b225f9f603c26a63244da2
claude-opus-5.5: all 30 recorded runs, failed ones included
claude-sonnet-5.5: all 30 recorded runs, failed ones included
Also published: signing-key.pub, timings-2026-09-29T05-31-42-707Z.json and timings-2026-09-29T05-31-42-707Z.sig, timings-2026-09-29T05-47-12-571Z.json and timings-2026-09-29T05-47-12-571Z.sig (response times), system-prompt.partner.en.txt (the agent’s instructions; its SHA-256 is in every run’s header), and verify.mjs, the same checks from a terminal.
The runs play in this browser and your decisions stay in it. If you accept analytics cookies, we count plays, decisions and uses of the summary button, with the scenario, the page language and the recording’s language only. Privacy policy