> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/agentic-adoption-and-security/observability/evaluator.md).

# Evaluator

<figure><img src="/files/034HFYhao8fUNA1wWQZK" alt=""><figcaption></figcaption></figure>

The Evaluator View is similar to the batch interface, in that it allows running a CSV file of inputs on your agent, all at once. This view allows testing before a project goes live, and leverages a LLM to evaluate your agent's output.

There are two types of evaluation:

### 1. Grading outputs based on criteria&#x20;

On the right hand side, create an evaluator:

* Select the output to evaluate
* Add a system prompt - the evaluation logic
* Give it a name

Once the evaluator is created, a new column will appear in the table showing the evaluation results for each row.

<figure><img src="/files/PSJPjluvPESXbGozXlxy" alt=""><figcaption></figcaption></figure>

Add as many evaluators as outputs in your workflow. Each one will evaluate a different output. Give each evaluator's model a system prompt and select which of your agent's outputs should be evaluated.

<figure><img src="/files/sQLuzPbP7uh7j0Z1uy1p" alt=""><figcaption></figcaption></figure>

You can manually add rows to evaluate, or upload a CSV with all your scenarios to evaluate (click the 3 dots and then the upload CSV option).&#x20;

### 2. Comparing outputs to a gold standard answer&#x20;

<figure><img src="/files/kikPtRq0XfNCp9EmcwIN" alt=""><figcaption></figcaption></figure>

Click 'Requires Expected Answer' to add a ground truth to your execution. This is the response you would expect from the AI model. The evaluator will then take it into consideration for the analysis.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.stackai.com/agentic-adoption-and-security/observability/evaluator.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
