Skip to main content
Private beta. A telemetry event records what happened. A reward is the grader’s score.
Use log_event during the trajectory. Use client.telemetry.ingest_events for events that arrive later, with your organization API key.

During the trajectory

Write runtime events before complete. Reuse event_id when retrying the same event. Read them back, newest first, with client.trajectories.list_events(tid). Events are not reward components. The source-grader guide logs grader details as an event; the diagnostic-artifact guide attaches a file to a trajectory.

Later application events

Required fields are event_id, event_type, timestamp, session_id, and source. Set trajectory_id when you have session.tid.
result reports ingested, skipped, and failures.