Skip to main content
Agents is in private beta, so things may change. If you hit a problem, tell us via Support & feedback.
Analytics answers three questions about your Agent: is it running, is it working, and what is it costing? Go to Agents → open an Agent → Monitor → Analytics.
Agent analytics showing the Runs volume and latency charts over the last 24 hours

​
What do the charts show?

The page has six sections. Use the tabs at the top to move between them, and the controls beside the heading to change the dates and filter what you see. Runs you stopped yourself, and runs stopped by a limit, don’t count as failures, but they’re still part of the total the failure rate is measured against. Timings only count runs that finished.

​
Why is my spend higher than the runs chart suggests?

Because runs aren’t the only thing that costs credits. Spend by source, under the Cost charts, splits your spend into runs and everything else: Auto-improve, scoring real runs, and run summaries. The other charts only count runs, so this is where the rest shows up.

​
How do I bring costs down?

  • Cap a single run under Build → More → Run limits
  • Drop the model tier if the Agent’s job doesn’t need the top one
  • Remove tools the Agent doesn’t use
  • Grade fewer real runs, or turn that off completely
  • Put a credit cap on Auto-improve
See Costs and limits.

​
Additional FAQ

A run that finished and failed. Runs you stopped yourself, and runs stopped by a limit, aren’t counted as failures, though they’re still in the total the rate is measured against. Only runs that never reached a known ending are left out altogether.
On the AI Credits page. Analytics only covers one Agent.
Open a slow run in Run history and read back through its steps. You’ll see whether the time went on the model or on one of the tools, and the Tools section here shows which tool is slow across every run.
Nothing has graded a real run yet. Turn on grading for a scorer that doesn’t need an expected answer.