Home / Compare

Run the head-to-head on your own calls.

A scorecard hands you the evidence and the command to regenerate every result yourself.

Two lanes, one you can re-run

Five dimensions, two lanes, each scored on its own.

Outcome, policy, conversation, speech, and reliability each pass or fail on their own evidence. The advisory model judge sits on a separate lane and never decides the verdict for you.

Every deterministic result re-derives from the same audio under one pinned policy. You recompute it yourself and get the same verdict.

See the five evidence tiers →

conversation-test.yamlscored per dimension
Outcometool / state evidence
deterministic
pass
Policyworkflow & rules
deterministic
pass
Conversationturn-taking timing
deterministic
fail
Speechtranscript · latency
deterministic
pass
Reliabilitypass^k across reps
deterministic
inconclusive
The advisory judge is a separate lane. It never gates unless you opt in.
Score your own recording
$ hotato test run conversation-test.yaml --agent <id>
Simulate the scenarios you must cover
$ hotato simulate scenario.yaml --out runs/
  • deterministic lane
  • advisory judge, opt-in
What ships in 1.3.1

Run it on your own recordings.

No account, no vendor number. Point it at a captured call or a simulated scenario: same scorecard either way.

Simulated artifacts are deterministic: seeds derive from the scenario, no model or network, every artifact stamped origin=simulated.

RoadmapA single-command open bake-off (one script running the five-part reproducible benchmark end to end) is on the roadmap: not shipped in 1.3.1.
Where it fits

Three questions about one call.

Different tools answer different questions. Match the question to the tool for it; the deterministic fixture layer owns the last one.

The same call, three jobs
The questionThe tool for itWhen
Did the whole call succeed? Task success, transcript rubric, compliance.Your broad QA suitebefore it ships
Should the agent yield right now? The live turn-taking decision, mid-call.Your runtime voice layerduring the call
Did the confirmed timing bug come back? Re-scored from the same audio, deterministically.Hotato, the deterministic fixtureafter a confirmed bug
Layers composeGate the fixture layer in CI, so a fixed timing bug stays fixed. It measures turn-taking timing: details on the timing page.