Saved evaluators are pre-configured evaluation setups that you create on the LangWatch platform. Once saved, you can reuse them anywhere—in experiments, monitors, guardrails, or via the API—without reconfiguring settings each time.Documentation Index
Fetch the complete documentation index at: https://langwatch.ai/docs/llms.txt
Use this file to discover all available pages before exploring further.
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
- Built-in Evaluators - Use evaluators directly without platform setup
- Custom Scoring - Send scores from your own evaluation logic
Creating a Saved Evaluator
Via the Platform UI
- Go to Evaluations in your LangWatch project
- Click New Evaluator
- Select the evaluator type (e.g., LLM Boolean, PII Detection)
- Configure the settings (model, prompt, thresholds, etc.)
- Give it a descriptive name and save
Via the Evaluators Page
You can also manage saved evaluators from the dedicated Evaluators page at/{project}/evaluators.
Using Saved Evaluators
Saved evaluators are referenced using theevaluators/{slug} format, where {slug} is the unique identifier assigned when you create the evaluator.
Finding Your Evaluator Slug
- Go to your saved evaluator on the platform
- Click the ⋮ menu → Use via API
- Copy the slug from the code examples
In Experiments
In Online Evaluation
As Guardrails
Via cURL
Saved vs Built-in Evaluators
| Aspect | Built-in Evaluators | Saved Evaluators |
|---|---|---|
| Slug format | provider/evaluator (e.g., ragas/faithfulness) | evaluators/{slug} (e.g., evaluators/my-checker) |
| Configuration | In code via settings parameter | Pre-configured on platform |
| Reusability | Copy settings across code | Reference by slug anywhere |
| Management | In codebase | In LangWatch platform UI |
| Team access | Developers only | Anyone with platform access |
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