Skip to main content
POST
A CI run is a standard evaluation run - this is the same endpoint as Create Run, shown here in its CI framing. Create the run at the start of the pipeline job, drive your agent through the dataset’s cases, submit and finalize, then compute the gate. Two fields matter most in CI:
  • evaluationSubject.version (or evaluationSubject.metadata.version): tag the run with the branch or commit under test, so version-to-version comparisons in the dashboard line up with your git history.
  • split: run only the dataset cases tagged with a named split (e.g. "smoke") for fast PR gates, keeping the full dataset for nightly runs.

Authentication

string
required
Project API key (use a CI secret, never source control).

Body

string
required
Dataset ID to evaluate against.
object
Metadata about the agent under test. In CI, include a version tag:
string
Grade with a standalone grading config instead of the dataset’s own criteria.
string
default:"\"sdk\""
How the run was triggered.
string
Named case subset to cover (cases tagged via main_question.splits). The caller filters which cases it executes; the split is recorded on the run’s subject.

Response

Returns 201 Created with { runId, datasetId, status: "in_progress", smokeTestVariants } - see Create Run for the full field reference. Read the cases to execute from the dataset itself (Get Test Cases).

Errors