Skip to main content
Native graph planning API
Submit a finite state graph to Adapt-1 native planning. GraphPlanningRequest requires session_id, relation, policy, and root. Each node has an ID and maximizing/minimizing perspective; each edge supplies an action and target node ID. See planning integration for graph construction and planning options for limits and evaluator selection. 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: GraphPlanningRequest. Fields outside this object’s declared properties are rejected by the schema.

GraphNode

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

PlanningOptions

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

PlanningState

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

GraphEdge

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

PlanningObservation

Schema: PlanningObservation. 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. HTTP graph edges refer to successor node IDs through target. Streaming expansion returns child state descriptors instead. Keep evaluator selection and terminal values consistent with the intended perspective; planning integration and planning options explain the observed behavior and remaining semantic limits.