Skip to main content
POST
Train the ExoBrain
Enqueue a full ExoBrain re-train for the caller’s org and return immediately with the job id. Requires the admin scope. Only one train may be in flight per org: a second request while one is queued or running returns 409. Poll GET /v1/brain/info for progress. The new artifact is published only after it passes its numerical parity gate, so a failed train leaves the previous brain serving.

Authorization

This route requires the admin 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

Every error is an RFC 9457 application/problem+json body carrying a stable code, a requestId, and a suggestedAction where Exo has one. See Errors.

Notes

  • One train per organization at a time. A second request while one is queued or running returns 409.
  • A failed train changes nothing. The new artifact is published only after it passes a numerical parity gate, so the previous brain keeps serving.

Authorizations

X-Exo-API-Key
string
header
required

An Exo API key (exo_...) sent as the X-Exo-API-Key header.

Body

application/json

Options for an ExoBrain re-train. Both fields are optional.

epochsScale
number
default:1
reason
string
default:manual

Response

The accepted training job.

The accepted training job.

jobId
string
required
orgId
string
required
status
string
required