# Agent scorecards that justify a release decision

Scorecards turn long agent runs into a reviewable verdict. AgentClash aggregates correctness, cost, latency, tool strategy, and validator evidence so baselines and candidates are easy to compare.

Source: https://www.agentclash.dev/features/agent-scorecards
Markdown export: https://www.agentclash.dev/md/features/agent-scorecards

## What scorecards include

A scorecard should be more than a single number — it should explain why a run passed or failed.

- OpenTelemetry-compatible trace import
- Pinned datasets and golden test cases
- Baseline versus candidate regression checks
- Replay trails for tool calls, outputs, and artifacts
- Scorecards for correctness, cost, latency, and evidence
- CI gates for prompt, model, RAG, and tool changes

## From run to scorecard

### 1. Import the evidence

Start from OpenTelemetry traces, curated datasets, support transcripts, or a real failure your team already saw.

### 2. Pin the baseline

Record the current accepted behavior so every prompt, model, RAG, or tool change has a fair comparison point.

### 3. Replay the evidence

Inspect tool calls, outputs, artifacts, latency, cost, and judge evidence when a candidate gets worse.

### 4. Gate the release

Compare candidate and baseline runs, then fail CI before a regression reaches users.

## Interpret results

Read the interpret-results guide, then wire scorecard thresholds into CI gates and release policy.

- [Agent evals](https://www.agentclash.dev/agent-evals): Real-task agent evals with replay evidence and CI gates.
- [LLM agent evaluation](https://www.agentclash.dev/llm-agent-evaluation): Evaluate LLM agents on full trajectories, not one-shot answers.
- [Compare tools](https://www.agentclash.dev/compare): See how AgentClash differs from prompt-eval platforms.
- [Interpret results](https://www.agentclash.dev/docs/guides/interpret-results): Learn how to read scorecards and replay evidence after a run.
- [Datasets overview](https://www.agentclash.dev/docs/guides/datasets-overview): Import examples, record baselines, sync regression suites, and gate CI.
- [Dataset CI gates](https://www.agentclash.dev/docs/guides/dataset-ci-gates): Fail builds when a candidate regresses against a pinned baseline.
- [CI/CD agent gates](https://www.agentclash.dev/docs/guides/ci-cd-agent-gates): Block pull requests when agent behavior gets worse.

## Agent scorecard FAQ

### What appears on an AgentClash scorecard?

Correctness signals, validator evidence, cost, latency, tool usage summaries, and dimension scores your challenge pack defines.

### Can scorecards compare two runs?

Yes. Baseline versus candidate comparisons are first-class for regression testing and CI gates.

### Can scorecards be exported or shared?

Yes. Runs keep scorecard views in the product and support shareable evidence for reviewers.