Scaffold a prompt
Wrap a single prompt in the effective subject’s cognitive scaffold: a short header naming the focal knowledge-graph nodes and the prior context that bear on the prompt.
X-Exo-Subject header.
Authorization
This route requires theread scope.
A missing or invalid credential returns 401 authentication_error. A valid credential without the scope returns 403 permission_denied, and the problem body names the exact scope required.
Headers
These are request conventions the contract does not declare as parameters, so they do not appear in the schema tables below.Success responses
Errors
application/problem+json body carrying a stable code, a requestId, and a suggestedAction where Exo has one. See Errors.Authorizations
An Exo API key (exo_...) sent as the X-Exo-API-Key header.
Body
Response
The scaffolded prompt and the focal node ids that shaped it.
ConditionScaffoldResponse + additive usage (existing keys unchanged).
Usage block on condition responses (spec D13), camelCase on the wire.
The compose builders are pure SQL reads (no LLM call today), so the token
fields are null; readUnits meters one unit per compose call. If a
future builder version starts spending LLM tokens, it reports them here.