Skip to main content
Saved evaluators are pre-configured evaluation setups that you create on the LangWatch platform. Once saved, you can reuse them in experiments, monitors, guardrails, or through the API without reconfiguring settings each time.
When to use Saved Evaluators:
  • You want to reuse the same evaluation configuration across multiple places
  • You prefer configuring evaluators via UI rather than code
  • You want non-technical team members to create and manage evaluations
  • You need consistent evaluation settings across your team
See also:

Creating a Saved Evaluator

Via the Platform UI

  1. Go to Evaluators in your LangWatch project
  2. Click New Evaluator
  3. Select the evaluator type (e.g., LLM Boolean, PII Detection)
  4. Configure the settings (model, prompt, thresholds, etc.)
  5. Give it a descriptive name and save

Via the Evaluators Page

The Evaluators page with three saved evaluators and the New Evaluator button
You can also manage saved evaluators from the dedicated Evaluators page at /{project}/evaluators.

Custom (Code) evaluators

A code evaluator is a saved evaluator whose logic is your own Python. Create one on the Evaluators page with New Evaluator → Custom (Code): declare its inputs (for example output and expected_output) and write a Code class whose __call__ takes those inputs and returns a dictionary with any of passed, score, label and details.
From code you can:
  • Run it like any saved evaluator: POST /api/evaluations/evaluators/{slug}/evaluate, with data holding one value per declared input.
  • Find it: GET /api/evaluators lists it with type: "code", and GET /api/evaluators/{idOrSlug} returns its code and inputs in config.
  • Monitor with it: run it on incoming traces with POST /api/monitors, sending the evaluator’s id as evaluatorId and code/<evaluatorId> as checkType, plus mappings from trace fields to its inputs.
Creating a code evaluator and editing its code are done on the Evaluators page: POST /api/evaluators only creates built-in evaluator types.

Using Saved Evaluators

Saved evaluators are referenced using the evaluators/{slug} format, where {slug} is the unique identifier assigned when you create the evaluator.

Finding Your Evaluator Slug

  1. Go to your saved evaluator on the platform
  2. Click the ⋮ menu → Use via API
  3. Copy the slug from the code examples

In Experiments

In Online Evaluation

As Guardrails

Via cURL

Saved vs Built-in Evaluators

Best Practices

Naming Conventions

Use descriptive, consistent names for your saved evaluators:
  • ✅ tone-checker-formal
  • ✅ pii-detection-strict
  • ✅ answer-quality-v2
  • ❌ test1
  • ❌ my-evaluator

When to Save an Evaluator

Save an evaluator when you:
  • Use the same configuration in multiple places
  • Want to manage settings from the UI
  • Need non-developers to configure evaluations
  • Want to version control evaluation criteria separately from code

Overriding Settings

You can override saved evaluator settings at runtime:

Next Steps

Built-in Evaluators

Custom Scoring

Evaluators List

Experiments

Last modified on October 12, 2026