Skip to main content
These pages are for teams that run agents and need to see what each run did, how well it did it, and what it cost. Use them to find a failing step, prove a change helped, and explain a spend increase. A trace is the step-by-step record of one run: model calls, tool calls, tokens, cost, and errors. A session ties a run, or a conversation’s runs, to the agent that ran it. An eval runs a set of cases and gives each case a score, and a scorer, your code or a hosted judge, decides what the score means. Cost is the recorded tokens of each model call, priced at your organization’s rates.

Core offerings

Record agent runs

Send traces and group runs into sessions.

Inspect one run

Follow model calls, tool calls, and errors step by step.

Test changes with evals

Score fixed cases before you release a change.

Score production sessions

Judge real sessions against your rubric.

Track spend and tokens

Compare cost across agents and check the rates behind it.

Choose where to start

Monitoring covers only the runs you send to Atlan Trident. Missing spans, scores, or costs do not show that a run succeeded or cost nothing. A trace error is an execution failure; an answer with no errors can still fail your rubric, so read traces and eval scores together. Run costs are calculated from traces and your rates; they are not your provider’s invoice.

See also