Monitor
Catch every agent failure in production
Moda reads every trace your agents run, flags the failures that never throw an error, and groups them into problems ranked by the users they affect.
Signals
Negative emotion rate
6.8%
−1.2 pts vs last 7 days
2,915 of 42,870 traces
Tool failure rate
3.1%
+0.9 pts vs last 7 days
4,102 of 132,330 tool calls
Lazy response rate
2.4%
−0.3 pts vs last 7 days
1,029 of 42,870 traces
Ungrounded claim rate
4.9%
+0.4 pts vs last 7 days
9,840 of 200,817 messages
What is changing
order_lookup times out
Tool failure+2.1 pts
Claims a refund that never ran
Grounding+0.8 pts
Asks for a human
User emotion+0.6 pts
Promised, not delivered
Laziness+0.3 pts
Where traces are concentrated
Orders and delivery38%
Refunds and returns24%
Account access17%
Product questions12%
How it works
From every trace to the problems that matter
Monitor every trace
Moda reads every production trace end to end and detects the failures that never throw an error: frustrated users, failing tools, lazy answers, and hallucinations. Add your own checks in plain language and get alerts in Slack, Linear, or email.
Trace
User
Where is my order? It was due on Monday.
Tool
order_lookup → error: timed out after 30s
Tool failureAgent
Good news, your order shipped and arrives tomorrow.
Contradicted claimUser
That's what you said yesterday. Get me a human.
FrustrationAgent
I can't transfer you from here.
Claimed inability4 signals · part of Order lookup times out under load
Find the mistakes they keep repeating
Failures are grouped into problems ranked by how many users they affect. Each problem shows the traces behind it, the turn where it went wrong, and related problems that share the cause.
Problem detected
Fabricated data after tool call
6735users affected
Fabricated data after tool call
When a lookup comes back empty, the agent fills in details from a look-alike record instead of saying it found nothing, so users get order numbers and dates that don't exist.
6735
Users affected
244
Linked traces
Linked tracesRelevancy
Quoted a tracking number the order lookup never returned
High
Gave a delivery date copied from another customer's order
High
Confirmed a refund total with no matching invoice
High
Listed opening hours for a store the search didn't find
Medium
See what users ask your agent to do
Moda splits every trace into user goals and groups them into use cases, kept current as your traffic shifts. Open a use case to see its volume, its trend, and the problems surfaced inside it.
Use cases
Orders and delivery
38%
16,290
Track a late order14%
Change a delivery address9%
Refunds and returns
24%
10,288
Account access
17%
7,288
Product questions
12%
5,144
Signals
Detections on every trace, out of the box
User emotion
16 emotions, from frustration and confusion to distrust and delight, read from the user’s own words, with what caused them and whether the agent recovered.
Tool failures
Every tool call is recorded as it arrives. Failed calls are grouped into named categories with a likely cause, per tool and over time.
Laziness
Stubbed code, skipped tool calls, promises with no action behind them, and work handed back to the user.
Hallucinations
Claims checked against what the trace recorded: success after an error, counts that contradict tool output, and tasks reported done that were not.
Tailored to your workflow
Custom signals
Judge
Agent gives time of day and attaches wrong time zone
3.2%
−0.8 pts vs last 7 days
Hit Rate
Hits out of every trace judged1.7K
Hits
Traces the judge matched54.5K
Traces Judged
Traces the judge gave a verdict onRecent hits
Told a customer in Berlin the store opens at 9:00 PT
Gave a Sydney customer the current time in UTC
Booked a 3pm EST callback for a customer in London
Said it was 6pm using the server's time zone
Monitors
Trigger
Agent gives time of day and attaches wrong time zone
Slack alert
Alert
Mention
When the hit rate is above
for an hour
Conditions
Right where you work
