Skip to main content
Observe value-learning evidence
Submit observations to the Adapt-1 value learner with stable identities. Each request accepts at most 50 observations and 50 application outcomes. See value observations for supervision sources, comparison groups, partition requirements, and the observed atomic rejection and deduplication rules. The request tables below describe schema version 5. A default marked “Not declared” is absent from that schema; it does not mean null. Check /version at the API host root and confirm compatibility with your deployment.

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 in schema version 5. 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: ValueObserveRequest. Fields outside this object’s declared properties are rejected by the schema.

ValueApplicationOutcome

Schema: ValueApplicationOutcome. Fields outside this object’s declared properties are rejected by the schema.

ValueObservation

Schema: ValueObservation. Fields outside this object’s declared properties are rejected by the schema.

ValueContinuation

Schema: ValueContinuation. Fields outside this object’s declared properties are rejected by the schema.

ValueOutcome

Schema: ValueOutcome. Fields outside this object’s declared properties are rejected by the schema.

ValueSuccessor

Schema: ValueSuccessor. Fields outside this object’s declared properties are rejected by the schema.

ValueInput

Schema: ValueInput. Fields outside this object’s declared properties are rejected by the schema.

Responses

The validation error 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). Operational refusals can have their own error details. For observed admission, atomic batch rejection, record_id duplicates, and HTTP 409 conflicts, use value observations. An observations entry must have exactly one supervision source even though this cross-field rule is not represented in the property table.