Value API
Train a value candidate
Start an asynchronous value fit with explicit initialization, observation selection, comparison options, validation settings, and installation controls.
Train a value candidate
Start a value fit with a required
session_id and request_id. HTTP 202 acknowledges the request; monitor training.status through value state. Set install: false for a candidate evaluated separately from the incumbent. Value training explains options, model guards, and report interpretation.
The tables below reproduce request fields from archived schema-version-5 build 0136121bd2cf9d4cdbcb114565c7e1ffb74c5a63. A default marked “Not declared” is absent from that schema; it does not mean null. See source and response notes for the evidence scope.
Path, headers, and query
Send the hosted API key asAuthorization: Bearer <ADAPT1_API_KEY>. The authenticated identity determines ownership; follow HTTP and contracts for the session placeholder.
X-Neuroadapt-Session-Id is a compatibility header present in the archived backend schema. It does not replace the hosted bearer identity.
JSON body contract
Content type:application/json. The HTTP request body is required. The following table describes its fields; linked schema names lead to the complete nested definitions on this page. When an array type also permits null, that alternative applies to the entire field, not to individual array items.
Request body
Schema:ValueTrainRequest.
Fields outside this object’s declared properties are rejected by the schema.
ValueApplicationCase
Schema:ValueApplicationCase.
Fields outside this object’s declared properties are rejected by the schema.
ValueTrainOptions
Schema:ValueTrainOptions.
Fields outside this object’s declared properties are rejected by the schema.
Responses
The archived validation shape has an optional
detail array. Each validation entry requires loc (an array of strings or integers), msg (string), and type (string); it can also include ctx (object) and input (any JSON value). Recorded operational refusals can have their own error details.
warm_start_source, install, observation_ids, and expected_initial_model_sha256 are request-level fields. warm_start and the other fitting controls belong inside options. The per-fit continuation workload limit is separate from per-row schema bounds; see training and reports.