Types
The shape determines what the rater sees: SSE renders a single panel
per comparison, SxS renders A and B together.
Lifecycle
evaluation.status_changed webhook (see
events).
Creating an evaluation
The minimum viable SSE evaluation:dryRun: true first to validate and price the run without
committing. See Quickstart.
The response includes a links object with absolute URLs to the
preview, review, edit, results, and public share pages — surface these
in your UI rather than constructing URLs yourself.
Running the autousers
Creating an evaluation does not queue autousers — that’s a separate call so you can stage a draft without spend.Running (if it was Draft),
expands selectedAutousers by agentCount into individual
AutouserRun rows, and enqueues them on the GKE worker. Each run takes
1–6 minutes depending on the design complexity.
Subscribe to the autouser_run.completed webhook for completion. Or
poll GET /v1/evaluations/{id}/autouser-status for an aggregate
snapshot. Or open GET /v1/evaluations/{id}/autouser-stream for an SSE
event stream.
Reading results
/results for dashboards (it’s already aggregated). Use /ratings
for warehouse sync (full row-level data, paginate).
Sharing
Every evaluation has a public share token. Sharing modes:
See Teams & permissions for the share
ACL.
Deletion
See also
- Autousers — how the personas queue, run, calibrate.
- Templates — what gets rated.
- Ratings & agreement — the scoring shape.