Seven events ship in v1. Each fires exactly once per state transition; none fan out per-rater.Documentation Index
Fetch the complete documentation index at: https://docs.autousers.ai/llms.txt
Use this file to discover all available pages before exploring further.
| Event | Fires when | Object |
|---|---|---|
evaluation.created | POST /v1/evaluations succeeds (status Draft or Running). | Evaluation |
evaluation.status_changed | Evaluation.status transitions. | Evaluation |
evaluation.completed | All AutouserRuns + ratings finalize. | Evaluation + summary |
autouser_run.completed | AutouserRun.status flips to completed. | AutouserRun |
autouser_run.failed | AutouserRun.status flips to failed. | AutouserRun + error |
rating.created | A new Rating row inserts (human OR autouser). | Rating |
calibration.frozen | An autouser’s rubric is frozen. | Autouser + rubric |
enabled_events on the endpoint. Use
["*"] to receive everything — recommended only for warehouse-sync
integrations.
Envelope
All events share the same outer shape:request.id traces back to the API request that triggered the event,
useful for correlating customer-side and server-side logs.
Per-event payloads
evaluation.created
evaluation.created
Fires after
POST /v1/evaluations returns 201. Payload mirrors the
HTTP response.evaluation.status_changed
evaluation.status_changed
Fires on every
Evaluation.status transition. Reading the current
status alone is insufficient — listen for this event if you need to
react on Draft → Running distinct from Running → Ended.evaluation.completed
evaluation.completed
Fires once when all queued
AutouserRuns reach a terminal state
(completed or failed) AND any pending human rating windows close.
The single most useful event for “wake up when the eval is done”
integrations.autouser_run.completed
autouser_run.completed
Fires per
AutouserRun when it reaches status: completed. If you
queued 6 runs (agentCount: 3 × 2 comparisons), expect six events.autouser_run.failed
autouser_run.failed
Fires when an
AutouserRun errors out. A failed run does NOT consume
autouser-rating quota, but you may want to alert on it (the design
might be unreachable, or the worker might have crashed).rating.created
rating.created
Fires per Rating row insert — humans AND autousers. The single
firehose event for warehouse-sync use cases. High volume on busy
evals; budget your receiver accordingly.
calibration.frozen
calibration.frozen
Fires when an autouser’s rubric is locked via
POST /v1/autousers/{id}/calibration/freeze. Downstream pipelines
should listen for this before promoting an autouser to production.Adding new events
New event types are additive — new entries onAutousers-Event-Type,
new payload shapes — and ship without a version bump. Build your
receiver to ignore unknown event types: