What did my agents do, and did anyone check?
See every step, its time and cost, and which actions ran with no review. Test changes and version prompts before they ship.
refund-agent · this week
Reviewed firstLet throughRefusedAlerts
2 open- Wed 14:0212 billing actions ran with no reviewOpen
- Tue 09:40Wait above 10 minutes for 3 requestsOpen
- Mon 16:21New agent version: refund-agent 2.4Seen
Reviewed first, by agent
Last 48 hNoneAll
One run, step by step
run 8f31Time and cost on every step. The last one needed a person.
Rules in use
- Refunds over £500Two must agree
- PayoutsRefuse over £5,000
- Customer emailOne person
Observe
Agent tracing
Send traces from any agent. See each model call, tool call and action with its time and cost, next to the review it needed.
- Works with what you useSend OpenTelemetry data, or use the SDK. No new agent framework to learn.
- Time and cost per stepYou enter your own model prices, so the cost is yours. Steps with no price are shown as unpriced, never guessed.
- Loops caughtAn agent that repeats the same call again and again is flagged.
refund-agent run
3.2 s · £0.04- model.call plan1.1 s£0.02
- tool.call orders.get0.3 s£0
- model.call decide1.4 s£0.02
- action refund.issueNeeds 2 reviewersReview
Linked review
- Request
- r_01HX9
- Decided
- Approved
- Prompt
- refund-triage v14
Observe
Review coverage
Match every action in your traces to a review. See which ones a person approved, which a rule passed, and which had no check at all.
- Five clear statesApproved, auto-approved, rejected but ran anyway, ran before the answer, and unreviewed.
- Gaps become rulesPick an unguarded action and turn it into a rule in a click.
- Only Xevrion can show itOther tools see the run. We hold the review too, so we can join the two.
Unchecked, most common
- customer.email_send62 actionsAdd rule
- order.cancel31 actionsAdd rule
- file.export17 actionsAdd rule
Gap to rule
- Found in a trace
- Rule drafted
- What-if replay
Observe
Evals and release gate
Run test sets against your agent, compare runs with honest statistics, and block a release when it gets worse.
- Honest numbersEvery score has a range. A small test set says so, instead of showing a confident number.
- Judge, with a checkAn AI judge is only trusted once it agrees with your people often enough on enough cases.
- A gate for CIFail the build when a run is worse than the one you trust.
Pass rate
Baseline against this runGate
- Rule
- No drop over 3 points
- Drop
- −11 points
- Confidence
- 95% interval
- Result
- Release blocked
In CI
$ xevrion evals gate run_41FAILED. pass rate fell 90% → 79%exit 1Observe
Prompt registry
Keep prompts in one place with fixed versions and moving labels, so you know which prompt every trace used.
- Versions never changeEdit a prompt and you get a new version. Old ones stay exactly as they were.
- Labels you can movePoint production at version 7, or back to 6. Every move is logged.
- Linked to tracesSee which prompt version was behind any run, and how it scored.
Versions
Never edited- v15Tighten refund wordingstaging
- v14Add order lookupprod
- v13First review rule
Move a label
- Eval run 41 passes
- Move prod to v15
- Traces show v15
Used by
- Traces
- 1,820 on v14
- Agents
- refund-agent
Know what your agents did.
Start free. Guard your first agent in a few minutes, and keep a record anyone can check.
- Free plan, no card
- Signed, chained decisions
- Checked offline, without us
Signed decision
- Decision
- Approved, 2 of 2
- Action
- refund.issue, £540
- Rule
- Two reviewers must agree
- Sealed
- 14:09, key 7f2c
- Hash
- 5be2…7c44
Checked on your own machine
- Signature matches the public key
- Decision is in the log
- Every link before it adds up