Jobs, found for you
Trodo groups your traces by what people asked the agent to do, with volume, satisfaction and failure rate for each.
Capabilities in the docsAgent analytics that answers one question: is your agent doing its job?
Trodo finds the jobs people use your agent for, scores how well it does each one, and shows the cost, tool success and satisfaction behind every number. Ask Lucid about any of it in plain English.
- The jobs your agent does, found for you
- Satisfaction and failure rate per job
- Tool success, latency and cost per trace
- Dashboards built by asking
What is agent analytics?
Agent analytics measures how an agent performs across all of its production traffic: which tasks people give it, how often it completes them, where it fails, how long it takes and what it costs. Where observability explains one trace, analytics explains the whole agent.
The useful unit is the job, not the call. A support agent handles refunds, order status and returns, and it is rarely equally good at all three. Knowing that refunds are its most common job and its weakest one tells a team exactly where to work.
Trodo discovers those jobs from your traces, scores every trace with its checks, and lets anyone on the team ask questions about the results without writing a query.
What Trodo measures. Per job, per trace, per user.
Every trace scored
Checks run on every production trace, so every metric is built on all your traffic, not a sample.
How checks workTool success and cost
Success rate, latency, retries and spend for every tool your agent calls. See which one drags the agent down.
Lucid, in plain English
Ask Lucid why a job’s satisfaction dropped or for a weekly dashboard, and get an answer with the traces behind it.
Lucid in the docsReports and alerts
Scheduled reports and alerts to Slack when a job’s failure rate or cost crosses the line you set.
Alerts in the docsTied to users
Every trace belongs to a user and a conversation, so you can see who a failure touched and whether they came back.
Identify usersAgent analytics compared
| Capability | Trodo | LLM tracing tools | Product analytics |
|---|---|---|---|
| Jobs discovered from traces | – | – | |
| Every trace scored | – | – | |
| Tool success and cost | – | ||
| Satisfaction per job | – | – | |
| Questions in plain English | Partial | Partial | |
| Users and retention | – |
Questions? Quick answers.
What is agent analytics?
Measuring how an agent performs across all its traffic: which jobs it is given, how often it completes them, where it fails, and what each costs. Trodo builds these numbers from checks on every trace.
How is agent analytics different from observability?
Observability explains a single trace. Analytics explains the agent as a whole: which jobs are growing, which are failing and which cost the most.
Which metrics matter most for an agent?
Task completion and satisfaction per job, failure rate, tool success rate, latency and cost per trace. Trodo tracks all of them per job and per user.
Do I need to write queries?
No. Ask Lucid a question in plain English and it answers with charts, tables and the traces behind them.
How much does it cost?
Developer is free forever with every feature: 10,000 units, 1,000 executions and $2 of Lucid credits a month. Pro is $249 a month with 250,000 units, 50,000 executions and $30 of Lucid credits.