Queues a durable eval job and returns immediately with its polling ID.

For prompt evals, provide explicit targets to override the configured prompt targets, or omit targets to use the organization's configured scheduled prompt targets. For API Performance evals, explicit targets or models override the stored configuration; when omitted, Lightsage uses configured scheduled targets or legacy configured models. For eval runs with source_type set to custom_evals, custom_eval_ids identify the evals to run, while targets specify the text models or coding-agent harness and model combinations used for the run. Omit custom_eval_ids to use the configured eval set.

For API Performance source types backed by a source (rest_api, sdk, or cli), provide source_id from api-performance sources list, or omit it when operation_ids, eval_ids, or the requested source_type identify a single source. operation_ids are Lightsage API Performance operation IDs, not OpenAPI operationId strings.

Every run is queued through the durable job queue. The response id is the eval_run_id to pass to GET /v1/eval-runs/{eval_run_id}. When Lightsage can determine the runnable work, the response also includes dispatch_id and initial queued progress for the child jobs. If neither the request nor the saved configuration identifies runnable work, the request fails with 400. If the organization lacks the estimated credits, it fails with 402 before dispatching work. An environment containing an empty or placeholder credential also fails with 400 before any evaluation is dispatched.