AppsEvaluations

Autessa Evaluations · AI agent evaluation

Know how your AI agent really does.

Autessa Evaluations is an AI agent evaluation platform. Use it out of the box to test agents before launch with simulated users, score every conversation for groundedness, task completeness, argument faithfulness and efficiency, check each reply before customers see it, and grade transcripts from any agent. Then tailor the rubrics, personas and checks to how your company works.

Start free

LLM-as-a-judge · simulated users · online evaluation · response checks · grading API

Case viewer · Billing support agent · Double chargeSAMPLE
USER
Hi, I was charged twice for order 1042.
TOOL_CALL · billing_lookup
{ "orderId": "1042" }
TOOL_RESULT · billing_lookup
2 charges of $48.00 on card ending 4417
ASSISTANT
I can see the duplicate $48 charge on order 1042. I’ve refunded it, and you’ll see it in 3–5 business days.
PASSED
EXPECTED OUTCOME · MET

Judge’s notes

GroundednessGrounded

The $48 amount and order 1042 match the billing lookup result.

Task completenessComplete

Found the duplicate charge and refunded it, as asked.

Argument faithfulnessAll faithful

The order number passed to the refund tool came from the user.

EfficiencyEfficient

Two tool calls, both needed.

Status SUCCESSFUL

What it measures

How does Autessa evaluate an AI agent?

Every evaluated conversation, from a test run, live traffic or an uploaded transcript, is read in full by a model judge and scored on four dimensions. Add an expected outcome and a second judge decides pass or fail: only Met passes.

The result is one of four statuses: Successful, Successful (Not Efficient), Successful (Not All Steps) or Unsuccessful. A partly done task does not pass, and a fabricated tool argument makes the evaluation unsuccessful.

1

Groundedness

Is every claim backed by a tool result, a document or the conversation?

2

Task completeness

Did the agent do everything the user asked?

3

Argument faithfulness

Did every tool argument come from the conversation, not a guess?

4

Efficiency

Did it get there without extra or repeated tool calls?

About the four dimensions →

What makes it different

Evaluation that covers the whole conversation, before and after it happens

Product tour

From first test to live monitoring

Sandbox · Test sets

Write tests the way customers start conversations

Autessa Evaluations includes agent test sets: each case is an opening message, an optional expected outcome in plain English and template variables, kept in run order.
  • Default simulated user per test set
  • Cases without an outcome are graded on quality
  • Create from the CLI with `autessa sandbox test-sets-create`
Test sets and test cases →
Sandbox · Test set · Refund requests4 CASESSAMPLE
01
Double charge

Initial message: Hi, I was charged twice for order 1042.

Expected outcome: Refunds the duplicate charge and says when it arrives.

02
Refund outside window

Initial message: Can I get a refund on something from March?

Expected outcome: Explains the 30-day policy and offers a store credit.

03
Wants a person

Initial message: I need to talk to a real human about my bill.

Expected outcome: Hands off to a person without arguing.

04
Case 4

Initial message: Why is my invoice higher this month?

Expected outcome: none, graded on quality only

Default simulated user: Impatient customerRun test set

Sandbox · Simulated users

Test with impatient, confused and skeptical customers

Simulated users are personas a model plays to hold real multi-turn conversations: a persona, a goal, behavior instructions, stop conditions and up to 10 turns. Starter personas are one click away.
Simulated users →
Simulated users · Starter personasSAMPLE
Impatient customer

Short on time, terse, pushes for a fast answer.

max turns · 6

Confused first-timer

Unsure what they need; vague, needs guiding.

max turns · 10

Frustrated, wants a human

Upset after a bad experience; tests escalation.

max turns · 8

Detail-checker

Precise and skeptical; checks every number.

max turns · 8

Sandbox · Run results

A pass rate you can trust, and the reasons behind it

Runs report pass rate, failures, errors and sandbox faults, results by persona, stop reasons and turns used. Platform problems are counted apart, so they are never mistaken for agent failures.
Run results →
Run results · Refund requests · Version 4COMPLETEDSAMPLE
86%
Pass rate
258
Passed
36
Failed
2
Sandbox faults

By persona

PersonaPass rateAvg turns
Impatient customer91%3.2
Detail-checker81%5.7

Stop reasons

GOAL REACHED 241STOP CONDITION 31MAX TURNS 24AGENT ERROR 2TIMEOUT 2

Evaluation Details

Scores with justifications, beside the transcript

Every evaluated conversation shows each dimension’s badge and justification, the status, and the expected-outcome verdict when there is one.
Expected-outcome judge →
Evaluation Details · Automated evaluationSAMPLE
Groundedness
Claims backed by tools, documents or context?
Grounded
Task completeness
Did it do everything the user asked?
Not all steps
Argument faithfulness
Did every tool argument come from the conversation?
All faithful
Efficiency
Tools used without extra or repeated calls?
Not efficient
StatusSUCCESSFUL (NOT ALL STEPS)Does not pass

Agent History

Full logs of every conversation

The transcript, every tool request and response, response check results, version and evaluation status, for every agent and channel.
Conversation logs →
Agent History · Billing support agentSAMPLE
Nov 3 · v4 · 6 messages · 2 toolsSuccessful
Nov 3 · v4 · 4 messages · 3 toolsSuccessful*
Nov 3 · v4 · 9 messages · 1 toolsUnsuccessful
Nov 2 · v3 · 3 messages · 1 toolsNot evaluated
⚙ refund_charge (2 messages)
input  { "orderId": "1042", "amount": 48 }
result { "status": "refunded" }

Human evaluation

Your experts have the final word

Reviewers record a status and notes on any conversation, and a human verdict always takes precedence over the automated one in history and statistics.
Human evaluation →
Evaluation Details · Human evaluationSAMPLE
AutomatedSUCCESSFUL
Human evaluationSUCCESSFUL (NOT ALL STEPS)

“Refund was right, but it never confirmed the customer’s email for the receipt.”

Evaluated by reviewer · takes precedence

AutoEval

Online evaluation on real traffic

Score every live conversation automatically, or a random sample between 20% and 40%.
AutoEval →
Configure AutoEvalSAMPLE
Off
AutoEval is disabled. No automatic evaluations will be performed.
On (Evaluate All Conversations)
All conversations will be automatically evaluated.
Random Sample
A random sample of conversations will be automatically evaluated.
Sample rate30%
20%40%

Version performance

Catch a regression the day it ships

Results split by published version and draft, with a shortcut to open the version behind a dip.
Version performance →
Version Performance BreakdownSAMPLE
71%
78%
84%
74%
89%
v1v2v3v4Draft

Success rate by version. Version 4 dipped after publish; the draft fixes it.

Dashboards

Trends anyone can read

Eval pass rates by day, scores over time, conversations by channel, human vs automated, and what checks and the AI Firewall caught.
Quality dashboards →
How your agents are doing · Eval pass rates by daySAMPLE
1,284
Conversations
90%
Success rate
412
Evaluated
7
Active agents

Share of test cases and graded conversations that passed, by day. Show the numbers for a table.

Multi-Agent History

Find which agent got it wrong

Manager runs open to the reasoning before each delegation and every sub-agent’s nested transcript.
Multi-agent evaluation →
Multi-Agent History · Orchestration viewerSAMPLE
MANAGER · Support desk · v6 · Agents used 2 · Iterations 3

Reasoning: the customer has a double charge and wants a receipt; delegate billing first, then email.

Billing agentDONE

Task: Look up order 1042 and refund the duplicate charge.

▸ Agent Conversation Context

Email agentCHECK

Task: Send the refund receipt to the customer.

▸ Agent Conversation Context

Response checks

Stop a bad reply before it is sent

Response checks are LLM guardrails that run on every reply, in every channel: fact grounding, sensitive data detectors, pattern and script rules, and AI review. Each one flags, redacts, blocks or retries.
Fact grounding check →
Response checks · before the reply is sentSAMPLE
DRAFT REPLY
Your order A-88213 for $45.00 ships Friday.
↓ all checks run at the same time ↓
No made-up prices or order numbers
Facts must come from the conversation
$45.00 not found
Sensitive data
Sensitive data detectors
Passed
No competitors
Script rule
Passed
Policy review
AI review
Passed
Action: Retry, then blockRETRIED
SENT TO CUSTOMER
Your order A-88213 for $42.50 ships Friday.

Transcript Grading

Grade conversations from any agent

Paste or upload a conversation from an agent built anywhere, add its instructions and an optional expected outcome, and get the verdict in seconds.
Transcript Grading →
Transcript Grading · Grade a transcriptSAMPLE
Agent instructions
You are a billing support agent. Look up the customer’s order, refund duplicate charges, and tell them when the refund will arrive.
Conversation
User: Hi, I was charged twice for order 1042.
Agent: Sorry about that! Let me check order 1042 for you.
User: Thanks. It was $48 both times.
Agent: I’ve refunded the duplicate $48 charge. It arrives in 3–5 business days.
PassedDecided by the expected outcome: only Met passes.

Batch jobs

Grade whole batches in the background

Up to 500 transcripts per job, with progress, pass rate and a signed webhook when the whole job finishes.
Batch grading jobs →
Transcript Grading · Batch jobCOMPLETEDSAMPLE
500
Transcripts
431
Passed
3
Failed to grade
86%
Pass rate
WEBHOOK · POST when the job finishes
X-Autessa-Timestamp: 1762290000
X-Autessa-Signature: sha256=<hex HMAC-SHA256 of "<timestamp>.<body>">

Everything in Evaluations

Everything you need to evaluate agents

Agent testing, scoring, production monitoring, response checks, grading for any agent and developer tools, in one place.

See every feature →

How it works

Test, ship, score, guard

  1. 1

    Write the test set

    Cases as real opening messages, with plain-English expected outcomes.

  2. 2

    Run with simulated users

    Against the draft or a published version, once per persona.

  3. 3

    Publish when it passes

    Compare pass rates in eval history, then publish.

  4. 4

    Score live traffic

    AutoEval and human labels on real conversations, split by version.

  5. 5

    Guard every reply

    Response checks flag, redact, block or retry before send.

Testing the apps around your agents too? Capture any workflow automatically with Autessa Autodocs: do it once in the browser and get a step-by-step guide and a replayable workflow you can run again before every release.

For developers

An evaluation API for any agent

Grade a transcript in one call, run batches with signed webhooks, and start test runs from scripts.

POST /clients/evaluations/grade
curl -X POST https://api.autessa.com/clients/evaluations/grade \
  -H "authorization: $AUTESSA_API_KEY" \
  -H "content-type: application/json" \
  -d '{
    "agentInstructions": "You are a billing support agent. Refund duplicate charges.",
    "expectedOutcome": "The agent refunds the duplicate charge.",
    "turns": [
      { "role": "USER", "content": "I was charged twice for order 1042." },
      { "role": "ASSISTANT", "content": "I refunded the duplicate $48. It arrives in 3-5 days." }
    ]
  }'
autessa CLI
autessa evaluations grade        # grade one transcript now
autessa evaluations jobs-create  # up to 500 in the background
autessa evaluations jobs-get     # poll progress and pass rate
autessa evaluations jobs-items   # page through results
autessa evaluations items-get    # one result, by itemId or externalId
autessa evaluations jobs-list    # your company's jobs

autessa sandbox test-sets-create
autessa sandbox policies-create
autessa sandbox runs-start
autessa sandbox runs-get

Use cases

Who uses agent evaluation?

AI engineers

Run test sets on every draft and read failures down to the tool call.

Product and QA

Write expected outcomes, compare versions, decide when to ship.

Support leaders

Label conversations, track success by channel, see what checks caught.

Risk and compliance

Block made-up facts, personal data and leaked instructions before send.

Data teams

Sync conversations and evaluations into tables and pull statistics by version.

Teams with agents elsewhere

Grade transcripts from any system with the Grading API.

Use cases by role and industry →

Integrations

Works with your agents, wherever they run

Native with Autessa agents, managers, AutessaDB, AutessaScript and the AI Agent Firewall; any other agent connects through transcripts, the Grading API, the CLI and signed webhooks.

All integrations →

Security

Evaluation data treated like conversation data

Graded transcripts aren’t added to agent history, batch results are encrypted, check results stay with your team, checks fail closed, and permissions follow each agent’s sharing.

Compare

Evaluating other agent eval tools?

FAQ

Questions teams ask about agent evaluation

What is Autessa Evaluations?

Autessa Evaluations is an AI agent evaluation platform. It tests agents before launch with test sets and simulated users, scores live conversations for groundedness, task completeness, argument faithfulness and efficiency, checks each reply before the customer sees it, and grades transcripts from any agent through an API.

Does it work out of the box?

Yes. Turn on AutoEval, add the starter personas and run your first test set on day one. Then tailor it in Autessa: write evaluation notes so the judge grades against your own definition of done, add personas that sound like your customers, and set the response checks and actions that fit your policies.

How does Autessa evaluate an AI agent?

Each conversation is scored on four dimensions and given a status. Groundedness asks whether claims are backed by tools, documents or context; task completeness asks whether the job got done; argument faithfulness asks whether every tool argument came from the conversation; efficiency asks whether tools were used without waste. The status is Successful, Successful (Not Efficient), Successful (Not All Steps) or Unsuccessful, and each dimension carries a written justification.

Does Autessa use LLM-as-a-judge?

Yes. The quality evaluation and the expected-outcome verdict both come from model judges, and AI review checks use a model you pick. Judges never default to a pass: a missing or unreadable verdict is retried once and then marked as an error. Rule-based checks, like the fact grounding check and sensitive data detectors, use no model at all.

Can I test an agent before people use it?

Yes. Build a test set of cases, each with an opening message and an optional expected outcome, then run it against the draft or a published version. Add simulated users and every case becomes a real multi-turn conversation with a persona that pushes back, asks for a human or checks every number.

Can I grade conversations from an agent that is not built on Autessa?

Yes. Transcript Grading accepts a conversation from any agent, with user and assistant messages, tool calls and tool results, plus the instructions the agent was given. You can grade one in the browser, call the Grading API, or send up to 500 per batch job with a signed webhook when it finishes.

How do I stop an agent from sending a made-up fact or sensitive data?

Turn on response checks. The fact grounding check catches a number, date, link, ID or quote that did not come from the conversation, a tool or your instructions, and sensitive data detectors find SSNs, card numbers, credentials and leaked instructions. Each check can flag, remove the matched text, block the reply or ask the agent to try again.

Do people still review conversations?

Yes, and their verdict wins. Anyone with write access to an agent can record a human evaluation with a status and notes on any conversation, and a human evaluation always takes precedence over the automated one in history and statistics. Full logs of every conversation, including each tool request and response, make review and labeling quick.

How do I catch a regression after publishing a new version?

Two ways. Run the same test set against the new draft and the current published version and compare pass rates in eval history, and watch the version performance breakdown in Agent History, which splits live results by version so a drop after a publish is visible right away.

Does it work for voice agents and multi-agent systems?

Yes. Voice replies are graded on what the caller actually heard, response checks release each spoken sentence only after it passes, and manager (multi-agent) conversations are judged on the full history and every user request, with each sub-agent transcript open for review.

Is there an API and a CLI?

Yes. `autessa evaluations` grades transcripts and manages batch jobs, `autessa sandbox` manages test sets, simulated users and runs, and `autessa agents submit-evaluation` and `autessa agents statistics` record human verdicts and return success counts by version. The Grading API is available to scripts over an API key at /clients/evaluations.

Measure your agents. Then make them better.

Use it out of the box: start with one test set and the starter personas, turn on AutoEval for live traffic, and add response checks to every reply. Then shape rubrics, personas and checks to your company in Autessa.

Start free

Test sets · simulated users · four-dimension scoring · response checks · grading API

100% customizable, code and all

Make Autessa Evaluations fully your own.

Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.

Start free and make it yours