# Share an LLM Eval Report — Make the Score Reviewable

Canonical: https://commareports.com/agents/share-llm-eval-report
Published: 2026-08-24

> promptfoo, DeepEval and Ragas all produce an HTML view somebody has to run a server to see. Publish the eval to Comma for a link where a reviewer can disagree with a specific grade, on the row it's on.

# Share an LLM eval report

Eval tooling has converged on a good shape: a table of test cases, one column
per model or prompt variant, a grade per cell, and a rollup at the top. What
none of it has solved is that the table lives behind a local command —
`promptfoo view`, a notebook cell, a Streamlit process on port 8501 — so the
only thing that escapes into a team conversation is the rollup.

And the rollup is the least useful part of an eval. **84% pass** is a number
everyone nods at. The 16% is where the actual disagreement lives, and it is
per-row: this grader was too strict, that test case is wrong, this refusal was
correct behaviour scored as a failure.

## Publish the run

```bash
npx promptfoo eval
npx promptfoo export latest --output eval.html
```

```python
import os, requests

r = requests.post(
    "https://commareports.com/api/v1/reports",
    headers={"Authorization": f"Bearer {os.environ['COMMA_API_TOKEN']}"},
    json={
        "title": "Support agent eval — system prompt v7",
        "description": "84% pass. 12 regressions vs v6, all in the refund flow.",
        "html": open("eval.html").read(),
    },
)
print(r.json()["url"])
```

Same shape for anything else that emits HTML — DeepEval, a Ragas notebook
converted with `nbconvert`, or a table you render yourself from the results
JSON, which is often the better report because you control what a reviewer
sees first.

Write a real description. "84% pass, 12 regressions, all in the refund flow"
is the sentence that makes someone open the link.

## The review is the deliverable

An eval only improves a system if somebody disagrees with it out loud.
Anchored comment threads put that disagreement on the row it belongs to:

- **"The judge scored this a hallucination — it's quoting the doc correctly."**
- **"This test case has been wrong since we wrote it. Remove it."**
- **"Correct refusal, graded as a failure. Rubric bug, not a model regression."**

Each thread stays attached across reruns, which is what turns a rubric from
folklore into something maintained. See
[commenting on HTML](/comment-on-html) and
[giving an agent feedback](/agents/give-an-agent-feedback).

## One URL per suite, a revision per run

```bash
curl -fsS -X PATCH "https://commareports.com/api/v1/reports/$REPORT_ID" \
  -H "Authorization: Bearer $COMMA_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d "$(jq -n --rawfile html eval.html '{html: $html}')"
```

Model versions change under you, prompts change weekly, and the only honest
way to read an eval is against the last one. PATCHing a single report id makes
the comparison structural: the link in your team channel is always current,
and every previous run is a diff away.

Two ways to make that automatic:

- **From CI**, on every prompt change — see [publishing from CI](/docs/ci).
- **On a schedule**, with a
  [routine](/features/routines/daily-claude-eval-refresh) that reruns the eval
  and republishes to the same report.

## Let the agent publish it

The REST surface is also exposed [over MCP](/docs/mcp), so an agent that just
ran an eval can publish the report itself and return the link — one tool call,
[scoped token](/agents/scoped-tokens-for-ai-agents), no human moving files
between machines. That matters more as evals get run by the thing being
evaluated. See [where should my agent post](/agents/where-should-my-agent-post).

## Limits

- **HTML body: 5 MB.** A large eval matrix with full model outputs will exceed
  it — publish the summary table plus the failing cases, and attach the raw
  results JSON as an asset (25 MB per file).
- **Scripts run, sandboxed:** `allow-scripts`, no `allow-same-origin`.
- **60 requests/minute per token.**

## Try it

Comma is free — unlimited reports, unlimited commenters, unlimited revision
history.

**[Publish an eval →](https://commareports.com/)**

### Related

- [Daily Claude eval refresh](/features/routines/daily-claude-eval-refresh)
- [Let an agent respond to comments](/agents/let-an-agent-respond-to-comments)
- [Context budgeting for AI reports](/agents/context-budgeting-ai-reports) · [MCP setup](/docs/mcp)