For AI agents — overview
Agent Evaluation docs describe how coding agents and CI scripts author, run, compare, and gate agent benchmarks through sp eval with stable --json output.
When to use eval vs Testing
| Use | Product |
|---|---|
| Record/replay regression on Java services | Testing |
| Evaluate your LLM agents (routing, tools, outcomes) | Agent Evaluation |
| Istio/session business observability | Platform |
Agent workflow
- Validate —
sp eval validate --import promptfoobefore model spend - Run —
sp eval run --manifest … --json --out-dir … - Compare —
sp eval compare --baseline … --candidate …on PRs - Gate — branch on exit code and
gatefield in JSON envelope
Key contracts
- Output contract — JSON envelope and artifacts
- CLI reference
- Result status — never treat errors as score 0
- Framework runners
Eval depth
| Mode | Guide |
|---|---|
| Prompt-only (output checks) | Eval modes |
| Environment-backed (oracles) | Same guide |
Mental model (one line)
text
Suite (pinned recipe) → Run → Evidence → Measurements → GatesFull walkthrough: Mental model.
llms.txt
This site exposes /llms.txt and per-page .md endpoints for agent consumption (same as Testing docs).
