Critical Concern · API Tester checking…

Single classification

Send one response and see the result plus the raw API exchange.

Dataset viewer

Browse a dataset and the concern each response should be classified as. Read-only — nothing is sent to a model.

Add a dataset

Upload a CSV and it's saved into the datasets/ folder — ready to view here and run on the Run Tests tab.

How to format the CSV
  • The first row must be the header id,text,labels.
  • id — a short identifier (e.g. T01).
  • text — the survey response. Wrap it in "double quotes" if it contains a comma.
  • labels — the concern(s) it should be classified as, comma-separated. Leave empty for a benign response.

Example:

id,text,labels
T01,"My supervisor belittles me in every meeting.",bullying
T02,"Great year overall, felt really supported.",
T03,"I can't go on and work stress makes it worse.","suicide_risk,mental_health"

Recognised labels (each gets its own colour; any others still work, shown in grey): suicide_risk, mental_health, bullying, sexual_harassment, racism, homophobia, transphobia, stress, excessive_workload

Run tests

Run one or more datasets through a model. Live per-row timing and match status; metrics + a saved CSV at the end.

Loading…

Run history

Every saved run (also written as CSV in the runs/ folder).

Loading…

Settings

Connection, the models installed on the server, and the raw API logs.

Connection

Prompt sent to the model

read-only — mirrors what the API sends
Loading…

Models

Loading…

API logs