Skip to main content
Reset value learner state
Use the Adapt-1 value reset route for an intentional value-state boundary. It accepts the compatibility session_id within the authenticated Domain scope and is distinct from Domain /clear and /policy/reset. Changing the body placeholder does not create a separate owner. The captured request schema does not specify which observations, configuration, or model state survive; verify the deployment’s postconditions before using reset in a workflow. 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 as Authorization: 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: ValueRequest. 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. The request shape establishes the authenticated Domain operation, not a complete deletion matrix. Verify the post-reset state returned by your deployment; see reset and clear.